16.20 - Migration Sequence - Teradata Vantage NewSQL Engine

Teradata Vantageā„¢ NewSQL Engine Node Software Migration Guide

Teradata Database
Teradata Vantage NewSQL Engine
March 2019

The destination system must be empty before beginning the restoration process. Prepare the destination system by first running sysinit to initialize the system, then running the DIP utility to run the DIPMIG script.

Before performing the data restore, check the destination system for a Time Zone String. See Checking Time Zone Setting Status. If it has one set, temporarily remove it, as described in Removing the Time Zone String.

Perform the restoration on the destination system by completing the following steps in the order indicated below.
  1. Restore database DBC from the source system archive.
    If this step fails, database DBC cannot be recovered. You must start the migration again by running sysinit and DIPMIG to prepare the destination system again.
  2. Restore journal tables from the source system archive.
  3. Run the post_dbc_restore script.
  4. Restore database SYSLIB from the source system archive.
  5. 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.
  6. If you excluded TD_SERVER_DB when restoring user data, restore TD_SERVER_DB from the source system archive individually.
  7. 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.
  8. If you removed the Time Zone String, restore it. See Restoring the Time Zone String.

If the RESTORE database DBC step fails, it cannot be recovered and the migration must start over by running sysinit and DIPMIG to prepare the destination system. If DBC database restoration fails, you must re-start the restoration process, beginning with running sysinit and the DIP utility to run the DIPMIG script on the destination system.

If restoration of user databases fails, you do not need to re-start the entire restoration process. However, you must manually run the upgradestats.pl script for restored databases, because statistics for those database are otherwise lost.