Removing HUT Locks After a Restart - 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

Teradata ARC places HUT locks on tables and databases to prevent modifications to the tables and databases before the job is restarted. Consequently, when a Teradata ARC operation does not finish, HUT locks might remain on tables and databases.

Occasionally, you might decide that you cannot restart a job for some reason. In this case, specifically remove HUT locks to allow the database or table to be accessed again.

To remove HUT locks:

  1. Run a utility statement that specifies the RELEASE LOCK statement for the currently locked database.
  2. Specify a new restart log. The restart log used when the failure occurred indicates that a restart is necessary, which prevents the removal of Teradata ARC HUT locks.

Example

The following example shows the statements needed to release the locks on a database named Database_Name.

LOGON TDPI/DBC,DBC;
RELEASE LOCK ( Database_Name ),  OVERRIDE;
LOGOFF;

For additional information on the RELEASE LOCK statement and the options available on this statement, refer to RELEASE LOCK.