16.20 - Restoring Database DBC - Teradata Vantage NewSQL Engine

Teradata Vantageā„¢ NewSQL Engine Node Software Migration Guide

prodname
Teradata Database
Teradata Vantage NewSQL Engine
vrm_release
16.20
created_date
March 2019
category
Administration
Configuration
Installation
featnum
B035-5942-162K
Restoring database DBC is the first step in copying the complete archived source system to the destination system. Restore database DBC only once. Run the post_dbc_restore script after you have restored DBC.
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 script 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 you have not already initialized the destination system, do that before continuing. See Initializing the Destination System.
  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.