Restoring the Database DBC - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

To restore Database DBC, the recommended procedure for Teradata ARC 16.10 and Teradata Database 16.10 is shown below. For the recommended procedure for prior releases, please see the Database Migration document for your specific release. For instructions on how to access the Data Migration documents, see the Data Migration documents section in Supported Releases.

The following table provides a summary and description of each step in the Database DBC restore process.

Database DBC Restore Steps 
Step Summary Description
1 sysinit Reinitialize the system by running sysinit .
2 If needed, reconfigure the system If needed, reconfigure the system to the desired configuration.
3 run DIPERR and DIPVIEWS Run the DBS Database Initialization Program (DIP) and execute the DIPERR (initialize the error message tables) and DIPVIEWS (initialize the system views) scripts. Do not run any of the other DIP scripts at this time, including DIPALL. See the Teradata Database Node Software IUMB document for information on running DIP. Please view the specific version of this document that matches the database version that you are restoring to. For instructions on how to access the Data Migration documents, see Supported Releases.
4 Enable DBC logons Only user DBC is allowed to restore database DBC. In addition, to avoid possible restart loops that could result in a sysinit, logons should be disabled for all other users except for user DBC. To do this, enter the following in the DBS supervisor console window.
DISABLE LOGONS;
ENABLE DBC LOGONS;

After database DBC is restored, logons for all user can be re-enabled by entering the following in the DBS supervisor console window.

ENABLE LOGONS;
5 Drop all user objects 
(ARC script option) If user objects are defined in the Teradata Database, drop them before restoring database DBC. (For a complete list of objects supported by Teradata ARC, see Database Objects.) Use the following statement to drop all such objects, except for permanent journal tables:
DELETE DATABASE (DBC) ALL, EXCLUDE (DBC);

DELETE DATABASE also deletes all UDTs from the SYSUDTLIB database.

To drop permanent journal tables, use the MODIFY USER or MODIFY DATABASE statement. (See the MODIFY DATABASE/USER descriptions in SQL Data Definition Language [B035-1144].)

6 Restore database dbc
(ARC script) Restore database DBC by itself running a script similar to the following:
LOGON DBC,DBC;
DELETE DATABASE (DBC) ALL, EXCLUDE (DBC);
RESTORE DATA TABLES (DBC),
  RELEASE LOCK,
  FILE=ARCHIVE;
LOGOFF;

Run DBC restores as single-stream jobs unless the archive is multi-stream. If multi-stream, use the same number of streams that were used during the archive. Using fewer streams during the restore can cause the job to fail. For more information, see Restoring with Multi-Stream.

7 Run post_dbc_restore After restoring database DBC, run the post DBC restore script (post_dbc_restore). The post_dbc_restore script will also run additional DIP scripts, as needed. For more information on the post_dbc_restore script, see Migration Scripts.
8 Restore user data
(ARC script) If restoring user data, follow the post_dbc_restore script by running a script similar to the following:
LOGON DBC,DBC;
      RESTORE DATA TABLES (DBC) ALL,
        EXCLUDE (DBC), (TD_SYSFNLIB),
        RELEASE LOCK,
        FILE=ARCHIVE;
      LOGOFF;

If using multi-stream, use the same number of streams that were used during the archive. For more information, see Restoring with Multi-Stream.

9 Run post_data_restore After restoring the user data, run the post data restore script (post_data_restore). The post_data_restore script also runs additional DIP scripts as needed. For more information on the post_data_restore script, see Migration Scripts.