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

Usage Notes

During an archive or recovery operation, Teradata ARC places HUT locks on the objects affected by the operation. These locks remain active during a Teradata Database or client restart, and must be explicitly released by the RELEASE LOCK statement or by the RELEASE LOCK keywords available on the ARCHIVE, REVALIDATE REFERENCES FOR, ROLLBACK, ROLLFORWARD, RESTORE and BUILD statements. Teradata ARC issues a message to report that the release operation is complete. It releases HUT locks when the AMPs return to online operation.

If the user name is specified in the logon statement, RELEASE LOCK or the equivalent option in a utility statement releases all HUT locks placed on the specified database or table. If the OVERRIDE keyword is specified in RELEASE LOCK, Teradata ARC releases all HUT locks on the specified database or table.

If HUT locks were placed at the database-level, they must be released at the database-level.

A table‑level release lock against a database-level lock has no effect. Conversely, a database-level release lock releases all locks on the database, including any database-level lock and all table level locks.

Do not specify ALL with the AMP keyword.

SYSUDTLIB can now be specified as an individual database name in the RELEASE LOCK statement.

BACKUP NOT DOWN Keywords

With Teradata Database, BACKUP NOT DOWN allows HUT locks to remain on non-fallback tables with remote single after image journaling when the backup AMP is offline.