Migration Rules - Teradata Database

Teradata Database Node Software Migration Guide

Product
Teradata Database
Release Number
15.10
Published
November 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
heq1467819788761.ditamap
dita:ditavalPath
5942_Migrating_1510.ditaval.ditaval
dita:id
B035-5942
lifecycle
previous
Product Category
Software
The following rules apply when restoring data as part of migrating a full-system:
  • The destination system must be empty before beginning the restoration process. Prepare the destination system by executing only the sysinit command and the DIPMIG script, in that order.
  • Perform the restoration on the destination system by completing the following steps in the order indicated:
    1. Check the Time Zone setting status, and disable the setting if it is enabled.
    2. Restore database DBC from the source system archive.
    3. Restore journal tables from the source system archive.
    4. Run the post_dbc_restore script.
    5. Restore database SYSLIB from the source system archive.
    6. Restore user data from the source system archive(s).
      When restoring user data, exclude DBC database and TD_SYSFNLIB. It is also recommended that you exclude CRASHDUMPS, SYSLIB, and SYSSPATIAL. If migrating from Teradata Database release 15.0 or later, also exclude TD_SERVER_DB.
    7. If you excluded TD_SERVER_DB when restoring user data, restore TD_SERVER_DB from the source system archive individually.
    8. Run the post_data_restore script.
      The post_data_restore script executes DIP scripts as appropriate. Some of these DIP scripts may require a different logon. If the current password security restrictions would prevent logon with the hard coded password, the post_data_restore script temporarily modifies the password security restrictions to enable the logon. After the DIP script completes, the post_data_restore script issues a tpareset to reset the password security restrictions to the original user settings.
    9. If you disabled the Time Zone setting, enable it.
  • The RESTORE command is expected to be run only once for DBC database and once for all user databases. If DBC database restoration fails, you must re-start the restoration process, beginning with running the sysinit command and the DIPMIG script on the destination system. If restoration of user databases fails, you do not need to re-start the restoration process. However, you must manually run the upgradestats.pl script for restored databases, because statistics for those database are otherwise lost. You must also manually run the upgradestats.pl if you restore user databases using the COPY command, which should not be used when performing a full-system migration. (For more information, see Restore Compared To Copy.)