Running the post_dbc_restore Script - Teradata Database

Teradata Database Node Software Migration Guide

Product
Teradata Database
Release Number
16.10
Published
November 30, 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
bkn1504122461303.ditamap
dita:ditavalPath
5942_Migrating_1610.ditaval
dita:id
B035-5942
lifecycle
previous
Product Category
Software
The post_dbc_restore script updates any table IDs for access rights and compiles system UDTs. If you do not run the script before restoring user databases, the upgradestats.pl script does not run automatically and must instead be run manually. This is also the case if you restore user databases using the COPY command (which should not be used when performing a full-system migration).
  1. Log on to the Control Node as user root.
  2. Run the post_dbc_restore script.
    /opt/teradata/PUTTools/tdxx.xx.xx.xx/IUMB_scripts/post_dbc_restore host_name/dbc,dbcpassword
    The script outputs logs in /var/opt/teradata/PUTTools/<script>_<td_release>.
  3. 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.timestamp
    Upon script completion, a list of errors appears.
    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.

  4. 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.