Upgrade Validation - Parallel Upgrade Tool (PUT)

Parallel Upgrade Tool (PUT) Reference

Parallel Upgrade Tool (PUT)
Release Number
February 2020
English (United States)
Last Update
Product Category
Teradata Tools and Utilities

The Upgrade Validation step verifies the Database Initialization Program (DIP) script output following minor, maintenance, and efix upgrades of the Teradata TDBMS component. Upgrade Validation is skipped during major upgrades and upgrades that do not include the TDBMS component. When errors are found in one or more DIP output files, a failure screen appears. Click the button on the failure screen to open a new window where you can view a detailed failure summary. The failure summary identifies each file that was checked and lists any errors that were found. You have the option to skip Upgrade Validation if an error occurs. When no errors are detected, the plug-in succeeds and moves immediately to the next step in the operation.

Important: If you skipped the Run DIP step and did not complete the appropriate DIP scripts, you must run them manually to complete the upgrade.

Supported DIP Options

The DIP utility creates an output file for each DIP option that runs. These files are stored in the /var/opt/teradata/tdtemp directory. Since DIPALL and DIPPATCH are mutually exclusive, you will always see output from one or the other, but never both, in the same run. The TDWM DIP script generates two output files when it runs. Both TDWM files include a timestamp that is always the same for both files. TDWM DIP was introduced in Teradata Database Release 13.10.

The DIP output file names use the following naming conventions:
DIP Option Output File Name
DIPALL dipall.txt
DIPPATCH dippatch.txt
TDWM DIP tdwmigrationlog timestamp.txt

tdwmscriptlog timestamp.txt

The CNS control node is where the DIP scripts are run and is the node where the output files are located. Upgrade Validation always validates all DIP output files located in /var/opt/teradata/support/DIPlogs/Last on the CNS control node.

PUTTools and the validate.pl Script

The PUTTools package contains the validation script used by PUT to verify the DIP output. The latest version of PUTTools is required to support all Teradata Database releases, and to support DIP output file formats for Teradata Database Release 13.0 or later.
Always make sure you have the current PUTTools version, which is available from https://access.teradata.com.

The validation script for each Teradata Database release is located in a corresponding directory in /opt/teradata/PUTTools. Within each of these directories is an IUMB_scripts directory that contains a number of version-specific scripts, including the validate.pl script used by Upgrade Validation. If the validate.pl script is not found, Upgrade Validation cannot run and will fail with an error indicating the script was not found.

Supported Teradata Releases

Upgrade Validation supports DIP output verification for Teradata Database Release 13.0 and later. The latest PUTTools package version is required to correctly parse all the DIP output files. Upgrades to versions earlier than Teradata Database Release 13.0 do not support DIP automation or Upgrade Validation.
Always make sure you have the current PUTTools version, which is available from https://access.teradata.com.

Handling Upgrade Validation Failures

When a failure occurs during Upgrade Validation, the Upgrade Validation Failed screen appears. Click the Display Upgrade Validation Failure Summary button to display the error summary in a new window. During an Upgrade Validation, DIP errors and setup errors can occur. You can skip Upgrade Validation and continue the operation no matter which type of error occurs. Upgrade validations cannot be retried, but the validation can be restarted using the table of contents if necessary.

Upgrade Validation Failed screen

DIP errors occur when the validate.pl script finds one or more errors in one or more DIP output logs. You must review these errors, correct them, and rerun DIP successfully to complete the upgrade. An example of a DIP error in the error summary is shown below.

DIP error example in error summary

Setup errors that occur when Upgrade Validation does not run as expected are logged in the error summary. If DIP scripts were run, you must verify the output manually to complete the upgrade. An example of a setup error is shown below.

Setup error example (upgrade validation issue)

The following table lists the different types of setup errors that can occur.
Setup Failure Error Description
No DIP logs DIP logs not found in /var/opt/teradata/support/DIPlogs/Last
No DIPlogs/Last directory /var/opt/teradata/support/DIPlogs does not exist
No validate.pl No validate.pl script, cannot run without this script
Process Manager Exception The PUT process manager could not run the validate.pl script
PUT can be used to rerun the DIP scripts and Upgrade Validation but all errors must be fixed before PUT attempts to run DIP again. Rerun the DIP scripts by restarting the Run DIP step using the table of contents on the PUT screen. Note that restarting the Run DIP step in PUT reruns all required DIP scripts, including the scripts that did not produce errors. A new set of output files is copied to the Last directory after each retry.
If you skip Upgrade Validation after DIP errors were detected, you must fix the DIP problems manually outside of PUT to complete the upgrade.