Each Teradata Database release has a unique subdirectory in the PUTTools directory for the post-upgrade and post-migration scripts applicable to that release. The folder is /opt/teradata/PUTTools/tdnn.xx.xx.xx, where nn is the major release number (15, 16, 17, and so forth), and xx.xx.xx is either the literal string xx.xx.xx (for initial releases, like 15.00, 16.00, 17.00, and so forth) or the minor release number (like 10, for 15.10 or 16.10) followed by xx.xx.
- Log on to the Control Node as user root.
Run the post_dbc_restore script.
/opt/teradata/PUTTools/tdnn.xx.xx.xx/IUMB_scripts/post_dbc_restore host_name/dbc,dbcpasswordThe script outputs logs in /var/opt/teradata/PUTTools/post_dbc_restore_xx.xx.xx.xx .
Use the tail command to monitor the output of the post_dbc_restore script:
tail -f /var/opt/teradata/migfiles/post_dbc_restore_xx.xx.xx.xx/post_dbc_restore.timestampWhen the script completes, any errors that occurred are listed at the end of the log in the Error Summary.
Running the post_dbc_restore script on SLES11 after DBC restore of an archive originated from SLES10 or earlier results in script failure and a message that PSF conversion is necessary. Using the Migrate PSF Setting option of the Workload Management Pre-Migration Tool prior to migration allows you to convert existing SLES 10 priority definition sets to SLES11 workloads allocated the appropriate level of resources.
If the source system is no longer available (for example, due to a system re-staging with backup, re-staging, sysinit, or restore), the required PSF configuration can no longer be acquired using the psfmigration.pl script, so this information is lost.
Correct any reported errors, and then run the script again. Repeat this process until no errors result.
Do not continue with the migration until the script runs without any errors.