Before migrating data to the destination system and while no users are logged on, initialize the system as follows.
-
On the destination system, do the following:
- Use the Vproc Manager to verify that all virtual processors (VPROCS) on are online.
- Install the correct Teradata Database release and Teradata Tools and Utilities release according to the procedures in the corresponding installation guides.
- On client platforms, install the correct Teradata Tools and Utilities release according to the procedures in the corresponding installation guide.
-
On the destination system, do the following:
-
Execute the sysinit command.
Execution of this command is a critical step in the migration process. It is the only time when row format and hash function can be changed, and is also the only time when Japanese language support can be enabled. Consult with Teradata Customer Services for assistance as necessary.
-
Run the DIPMIG script (which runs the DIPERRS, DIPDB, DIPVIEWS, DIPVIEWSV, and DIPBAR scripts in the required order).
Do not run the DIPALL script after executing the sysinit command. Run only the DIPMIG script. If this script is not run, or the DIPALL script is run, DBC database restoration will fail and the sysinit process must be repeated on the destination system.
-
Execute the sysinit command.
- If you are using DSA to migrate data, see Teradata Data Stream Architecture User Guide, B035-3150 for instructions on adding the required system configuration, restarting DS Main, and activating the added system configuration.
-
On the destination system, enable only DBC logons from the Supervisor window in the DBW console.
Enabling only DBC logons on the destination system before restoring database DBC reduces outside logon attempts during restoration.