Initialize the Destination System | Teradata Vantage - 17.00 - 17.05 - Initializing the Destination System - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Advanced SQL Engine Node Software Migration Guide

Advanced SQL Engine
Teradata Database
Release Number
Release Date
June 2020
Content Type
Publication ID
English (United States)
Before migrating data to the destination system, and while no users are logged on, initialize the system as described below.
  1. Use the Vproc Manager to verify that all virtual processors (VPROCS) on are online.
  2. Install the correct Advanced SQL Engine release and Teradata Tools and Utilities release according to the procedures in the corresponding installation guides.
  3. On client platforms, install the correct Teradata Tools and Utilities release according to the procedures in the corresponding installation guide.
  4. On the destination system, do the following:
    1. Run (or have your Teradata Services representative run) the sysinit utility to initialize the system.
      Sysinit will remove any existing data on the destination system.
      The only time you can change the database row format and hash function is during system initialization. This is also the only time you can enable Japanese language support. If you require assistance, consult with Teradata Customer Services.
    2. Run the DIPMIG script (which runs the DIPERRS, DIPDB, DIPVIEWS, DIPVIEWSV, and DIPBAR scripts).
      Do not run the DIPALL script after running sysinit. 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.
  5. See Teradata® DSA User Guide, B035-3150 for instructions on adding the required system configuration, restarting DSMain, and activating the added system configuration.
  6. Enable DBC logons and prevent user logons on the database by using the Database Window utility or an equivalent console utility, such as cnsterm or cnstool, to enter the following console command:
    enable dbc logons