Usage Notes - 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 rollforward operation uses a single journal table as its input. Define all tables specified for recovery with the same journal table. ROLLFORWARD can recover all data tables or a subset of the tables that are protected by the same journal table.

Use ROLLFORWARD to rollforward data tables on all or a subset of the AMPs.

Do not execute a rollforward over a data definition statement that changed a table’s structure. If Teradata ARC encounters such a change to a table during a rollforward, the rollforward for that table stops and an error message is placed in the output listing.

When recovering a nonfallback table with unique secondary indexes and an AMP is offline, Teradata ARC invalidates unique secondary indexes on the table. After the AMP returns online, drop and then recreate the unique secondary indexes for that table or use BUILD DATA TABLES on the table.

Using BUILD DATA TABLES is much faster than dropping and recreating the unique secondary indexes.

If the table being recovered has a single after image journal and the recovery operation uses the current journal, do not roll forward data rows on the AMP that are backed up by an AMP that is offline. If the table being recovered has a local single after image journal, it may be recovered only to the last archived data.

If the tables to be rolled forward have a dual after-image journal, then the rollforward operation (by default) uses the journal tables that exist on each AMP to roll forward those AMPs.

When performing a restore and rollforward, bring the affected data tables on the AMPs to their state after a modification. Specific AMP rollforwards are typically performed to do one of the following:

  • Complete a previous all-AMPs rollforward that happened while some AMPs were offline.
  • Recover a single AMP from a disk failure.
When a PPI table or a Column Partition (CP) table is restored, Teradata ARC automatically executes the Revalidate step during the BUILD phase. The Revalidate process increases the Util version of the table. This is considered to be a structural change to the table. Because of this change, a PPI table or a CP table cannot be recovered using either the RollBack or RollForward operation after it is restored.