RELEASE LOCK - 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

RELEASE LOCK

Purpose  

RELEASE LOCK removes a utility (HUT) lock from the identified databases or tables.

Syntax  

where

 

Syntax Element

Description

(dbname)

Name of the database on which the HUT lock is to be released

ALL

Indicates the operation affects the named database and its descendants

(dbname.tablename)

Name of the table on which the HUT lock is to be released

EXCLUDE

Prevents HUT locks on the named databases from being released

(dbname)

Name of database to exclude from release

ALL

Excludes the named database and its descendants

(dbname1) TO (dbname2)

Alphabetical list of databases to exclude from release

The delimiting database names need not identify actual databases.

Database DBC is not included as part of a range.

CLUSTERS = nnn or CLUSTER = nnn

Specifies AMP cluster for which locks are released

nnn is the number of the cluster on which locks are released.

Specify up to 4096 cluster numbers.

Locks are not released on any offline AMPs in the specified clusters unless the ALL option is specified.

ALL

Releases locks on AMPs that are offline when RELEASE LOCK is used

Teradata ARC releases HUT locks when the AMPs return to online operation.

Note: Do not use the ALL keyword with the AMP option.

OVERRIDE

Allows HUT locks to be released by someone other than the user who set them

BACKUP NOT DOWN

Allows HUT locks to remain on non-fallback tables (with single after image journaling) for those AMPs where the permanent journal backup AMP is down

Teradata ARC releases all other HUT locks requested.