System Merge - Parallel Upgrade Tool (PUT)

Parallel Upgrade Tool (PUT) Reference

Product
Parallel Upgrade Tool (PUT)
Release Number
3.09
Published
February 2020
Language
English (United States)
Last Update
2020-02-24
dita:mapPath
ows1493317469465.ditamap
dita:ditavalPath
ows1493317469465.ditaval
dita:id
B035-5716
Product Category
Software
Teradata Tools and Utilities

The System Merge step takes a previous configuration found by the GDO Info step (from an earlier run of the Configure Teradata Vantage operation) and maps it to the current configuration discovered by PUT. It also determines how nodes are mapped into cliques by examining shared storage between nodes. If an error is encountered when trying to merge the old configuration data with the current configuration data, operational messages appear.

This step requires no user interaction unless an error is encountered when trying to merge the old configuration data with the current configuration.

System Merge Operational Messages

Message Description
Clique cabling error detected Indicates that SysMerge encountered a clique cabling error, meaning the shared external disk arrays are cabled incorrectly between nodes. For a clique to be valid, all nodes in the clique must share the same external storage.

This message also indicates that at least one node shares only some of the storage devices in the clique. The display shows the two nodes that are in conflict. Under each node is a list of shared disk controller serial numbers that are accessible from that node. For both nodes to be in the same clique, both lists must be identical.

This is a fatal error and must be corrected before the Configure Teradata Vantage sequence can run successfully. You must locate the disk array that is in conflict and correct the cabling so that it is accessible from all nodes in the clique, or remove it from all but one node so that it is not included as available clique storage.

SysMerge determined this is a re-config, but no previous GDO information can be found Indicates that the GDO Info step found previous configuration information, but the SysMerge step cannot access the internal tables that contain the previous configuration data. This is a fatal error and causes the step to abort to prevent any possibility of overwriting an existing configuration with a new one.
Configure Teradata Vantage cannot match previously-defined pdisks with current storage. These pdisks are owned by active AMP vprocs. Configure Teradata Vantage cannot continue Indicates that SysMerge cannot find previously defined pdisks within the current system storage devices. Since the AMPs that own these pdisks were still active the last time Teradata was running, this is a fatal error. SysMerge does not continue because to do so would risk losing existing data.
Configure Teradata Vantage cannot match previously-defined pdisks with current storage. However, the AMP vprocs that own these pdisks are no longer active Indicates that SysMerge cannot find previously defined pdisks within the current system storage devices. However, the owning AMPs in this case are inactive. Since the AMPs are inactive, you can continue the operation. However, if you continue, these AMPs and pdisks are deleted from the configuration.
One or more ACTIVE AMP vprocs were found to have pdisks spread across multiple cliques. All pdisks assigned to an AMP must be in the same clique Indicates that the pdisks for an AMP are currently on devices that are in different cliques. This is an invalid system configuration. All storage for a single AMP must physically reside in the same clique as the AMP. Because the AMP is currently active, this is a fatal error and must be corrected before Configure Teradata Vantage can run successfully.
One or more inactive AMP vprocs were found to have pdisks spread across multiple cliques. Click NEXT to have Configure Teradata Vantage delete those pdisks from the configuration or click CANCEL to abort this operation Indicates that the pdisks for an AMP are currently on devices that are in different cliques. However, because the AMP is inactive, you can delete it from the configuration and continue.
SysMerge has detected an empty storage table. This means that no available storage space was found and no existing Teradata pdisks were found Indicates that there is no available disk storage on the system and there is no existing database. You cannot create a valid Teradata configuration without at least one piece of disk storage. This is a fatal error.