Usage Notes - 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

ROLLBACK erases all changes made to a database or selected tables of a database. Use ROLLBACK to roll back data tables on all or a subset of the processors. A rollback uses a single journal table as input. All objects in the object list must share the same journal table.

A rollback is not allowed over a data definition statement that changed a table’s structure. If Teradata ARC encounters such a change to a table during a rollback, the rollback for that table stops and the program prints a message in the output listing.

If an AMP is offline and a nonfallback table is being recovered with unique secondary indexes, Teradata ARC invalidates unique secondary indexes on the table. After the AMP returns online, drop and recreate the unique secondary indexes for that table.

RELEASE LOCK can be used instead of the RELEASE LOCK keywords. Use the RELEASE LOCK statement to release all HUT locks and the RELEASE LOCK keyword to release specific HUT locks.

To roll forward using a current single image journal, first roll back to the checkpoint. After the rollback has completed, use ROLLFORWARD to restore the data.

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.