Teradata ARC Locks During a Restore Operation - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
15.00
Language
English (United States)
Last Update
2018-09-25
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

Teradata ARC Locks During a Restore Operation

A restore operation uses an exclusive HUT lock when data tables are restored.

  • To restore an entire database, Teradata ARC places the exclusive lock at the database level.
  • To restore selected tables, Teradata ARC places the exclusive lock on each table before it starts to restore the table.
  • To restore (or copy) selected partitions of PPI tables, Teradata ARC uses a write lock.
  • To restore selected partitions of PPI tables with GROUP READ LOCK, the entire table locks rather than a part of the table.
  • Restoring Tables

    If the RELEASE LOCK keyword in the RESTORE statement is specified and that statement specifies that selected tables are to be restored, Teradata ARC releases the exclusive HUT lock on each table as soon as it finishes restoring it.

    Restoring a Journal Table

    When a journal table is restored, Teradata ARC places a write HUT lock on the table. The restored journal table and the journal table that is recording changed rows are different physical tables. Consequently, the write HUT lock exerted by a journal table restore does not prevent change images from recording to the journal table. The write HUT lock only prevents concurrent restore operations to the same journal.