Restoring a GROUP READ LOCK Archive - 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

To restore tables that are archived under a group read HUT lock, define them with an after-image journal. Always follow the restore of an archived data set taken under a group read HUT lock by performing a rollforward operation, using the after-image journal that was created during the archive. Rollforward ensures that the data in the tables is consistent. To learn more about the rollforward operation, see ROLLFORWARD.

An archive taken under a group read HUT lock does not archive secondary indexes defined for the tables being archived. Therefore, rebuilding the indexes after restoring the archive is required. If the NO BUILD option is not specified for the restore, Teradata ARC builds nonunique secondary indexes as part of the restore process. Teradata ARC does not rebuild unique secondary indexes. To learn more about the NO BUILD option, see NO BUILD Option.

The Teradata ARC restore process marks all existing unique secondary indexes as invalid for the table being restored. Rebuild or drop all secondary indexes by doing one of the following:

  • Issue a BUILD DATA TABLES statement.
  • Drop and recreate the index.

Rebuild unique secondary indexes only after the rollforward of the data tables is complete.