Restoring Database DBC - 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
Restoring database DBC is the first step in making a copy of the complete archived source system on the destination system. Restore database DBC only once, and run the post_dbc_restore after doing so.
Prior to archiving and restoring database DBC, user DBC must have full access rights for database DBC. If the source system is not available, such as when restoring from tape, then full access rights must be explicitly granted for each object, view, and macro in DBC after database DBC restoration in order for the post_dbc_restore and post-restoration DIP scripts to run cleanly.

If you have permanent journals, restoring database DBC converts the permanent journal dictionary to the new format, but does not convert data in the permanent journal.

The following procedure and ARC-based scripts are common to many sites. If your site has different restoration procedures or job scripts, use those instead to complete the process.

  1. If not previously done as part of initializing the destination system, complete the following steps:
    1. 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.
    2. Open a Supervisor window, and then enter the following command:
      start dip
      
    3. 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.
    4. In the Supervisor window of the DBC console, enable only DBC logons by entering the following code:
      enable dbc logons
      Enabling only DBC logons on the destination system before restoring database DBC reduces outside logon attempts during restoration.
  2. Restore database DBC. The following example illustrates code for restoring database DBC:
    LOGON tdp/dbc,dbc_password;
    DELETE DATABASE (DBC) ALL, EXCLUDE (DBC);
    RESTORE DATA TABLES (DBC), RELEASE LOCK, FILE=ARCHIVE;
  3. If you have permanent journals, restore the journal tables using the following commands:
    RESTORE DICTIONARY TABLES ALL FROM ARCHIVE,
    RELEASE LOCK,
    FILE=JNLARCH;
    Journal data is not restored.
  4. Complete the steps to run the post_dbc_restore script.