Restoring After a Disk Failure - 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

To recover from a disk failure, run the Disk Copy and Table Rebuild utilities to restore database DBC and all user data tables defined with the fallback option, then perform a specific AMP restore.

To specify the non-fallback tables that were not restored while the AMP was inoperative, specify database names or names of individual tables with the EXCLUDE keyword.

When restoring part of a non-fallback table during an all-AMPs restore is not possible because an AMP is offline, the system invalidates unique secondary indexes for the table. After the AMP is back online and the table has been restored, either drop and then recreate the unique secondary indexes for the table, or use BUILD to recreate secondary indexes.

To restore from a catastrophic condition (for example, to restore database DBC) on a system that has permanent journaling, restore the system using an archive created from an ARCHIVE JOURNAL TABLES statement in the following order:

  1. RESTORE DATA TABLES (DBC) ...;
  2. RESTORE DICTIONARY TABLES (DBC) ALL, EXCLUDE (DBC), (TD_SYSFNLIB)..., FILE=ARCHIVE;
    For this example, ARCHIVE is a journal archive.
  3. ;RESTORE DATA TABLES (DBC) ALL, EXCLUDE (DBC), (TD_SYSFNLIB)...;
  4. RESTORE JOURNAL TABLES (DBC) ALL, EXCLUDE (DBC), (TD_SYSFNLIB);
    Follow Step 4 only if rolling the journal images forward or backward.

RESTORE builds the fallback copy of primary and non-unique secondary index subtables within a cluster. If the system fails during this process, RESTORE rebuilds fallback copies automatically.