The following information applies to DBS release 12.0 and above.
Whenever database DBC is restored, run the post_dbc_restore migration script before continuing with the restore of the Teradata system. If the post_dbc_restore migration script fails or is interrupted, reinitialize the system and restart the migration from the beginning.
Whenever table data is restored to a system as part of a full system restore, to a system with a different release, or to a different platform, run the post_data_restore migration script after the data restore is completed. If the'post_data_restore migration script fails or is interrupted, run the data restore and the 'post_data_restore' migration script again.
In most cases, Teradata ARC prints a message that specifies that a specific migration script needs to be run, and then automatically exits to allow the user to run the script. After the script runs, the restore can be continued.
For detailed information regarding the post_dbc_restore and post_data_restore migration scripts, refer to the appropriate Data Migration document for the DBS release on the target system. To find the related Data Migration documents, see the Data Migration documents section in Supported Releases. The Data Migration documents that discuss the post_dbc_restore and post_data_restore migration scripts have the general title, Teradata Database Node Software Migration Guide. Please view the specific version of this document that matches the database version to that which you are restoring.