Restoring with a Specific-AMP Archive - Teradata Tools and Utilities

Teradata® Archive/Recovery Utility Reference

Product
Teradata Tools and Utilities
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-06-05
dita:mapPath
fac1527114221922.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
Product Category
Teradata Tools and Utilities

Before restoring database DBC do the following:

  1. Reconfigure the system from a single AMP to the desired configuration.
  2. Run the DBS Database Initialization Program (DIP) and execute the DIPERR and DIPVIEWS scripts. Do not run any of the other DIP scripts at this time, including DIPALL.

Example

This example demonstrates how to restore all databases from an all-AMPs archive and a specific-AMP archive. All AMPs are online for the restore, although AMPs may have been added to or deleted from the configuration since the archive was taken.

The next example assumes that none of the databases have journal table definitions. Journal tables must be dropped before running this job.

LOGON DBC,DBC;
DELETE DATABASE (DBC) ALL, EXCLUDE (DBC);
RESTORE DATA TABLES (DBC),
  FILE=ARCHIVE;
LOGOFF;

Run the post DBC restore script (post_dbc_restore).

LOGON DBC,DBC;
      RESTORE DATA TABLES (DBC) ALL,
        EXCLUDE (DBC), (TD_SYSFNLIB),
        NO BUILD,
        FILE=ARCHIVE;
      RESTORE DATA TABLES (DBC) ALL,
        EXCLUDE (DBC), (TD_SYSFNLIB),
        NO BUILD,
        FILE=ARCHIVEX;
      BUILD DATA TABLES (DBC) ALL,
        EXCLUDE (DBC),
        RELEASE LOCK;
      LOGOFF;

Run the post data restore script (post_data_restore).

In this example, file ARCHIVE is an all-AMPs archive; ARCHIVEX is a single AMP archive.

When the restore is complete, check the print file to verify that all AMPs remained online throughout the process. If one or more AMPs went offline, see Restoring With AMPs Offline for more information.

To decrease the total time required to complete the restore process, specify the NO BUILD option for the restore operation, then submit a BUILD statement after the specific-AMP restore. In addition, unique secondary indexes remain valid on nonfallback tables.