Certain Statements Force the Restoration of the Entire Database - 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

A Teradata SQL DROP or RENAME statement cause the definition of an entity to be removed from the dictionary. This same definition cannot be recreated using a Teradata SQL CREATE statement because a create operation is a new logical definition.

As a result, do not restore a dropped:

  • Table unless you restore the entire database
  • Database unless you restore database DBC first

A Database DBC archive must also contain a definition of the dropped database.

Archive individual tables with care, and periodically archive the dictionary.

If restoring all of a user database or database DBC (that is, all of the Teradata Database) is required because of a catastrophic event, restore the dictionary information for the database at the database level before restoring the individual tables. Restoring the dictionary first restores the table definitions, so that the tables can be successfully restored.