17.10 - LockLogger [Deprecated] - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Utilities

Product
Advanced SQL Engine
Teradata Database
Release Number
17.10
Release Date
July 2021
Content Type
Configuration
Publication ID
B035-1102-171K
Language
English (United States)

Determines whether the Lock Logger feature is enabled or disabled. The Lock Logger logs delays caused by blocked database locks, and can help identify lock conflicts.

The command-line Lock Logger utility (dumplocklog) and related DBS Control settings are deprecated, but remain available for compatibility with prior releases. Database locks should be logged using the Database Query Log (DBQL). This lock information can be accessed by means of the Teradata Viewpoint Lock Viewer portlet, or by querying the DBC.QrylockLogXMLV view.
  • For more information on DBQL, see Teradata Vantage™ - Database Administration, B035-1093 and the BEGIN QUERY LOGGING statement in Teradata Vantage™ - SQL Data Definition Language Syntax and Examples, B035-1144.
  • For more information on the Lock Viewer portlet, see Teradata® Viewpoint User Guide, B035-2206.

Field Group

General

Valid Settings

Setting Description
TRUE Enable the Lock Logger.
FALSE Disable the Lock Logger.
If LockLogger is set to FALSE, the LockLogger Delay Filter, LockLogger Delay Filter Time, and LockLogSegmentSize DBS Control fields are ignored.

Default

FALSE

Changes Take Effect

After the next database restart.

Usage Notes

Lock Logger runs as a background task, recording lock information in a table. Use the Lock Logger (dumplocklog) utility to create or designate a table to be used for storing lock log entries.

LockLogger is useful for troubleshooting problems such as determining whether locking conflicts are causing high overhead.

Some values in the lock log table represent internal IDs for the object on which the lock was requested. The lock log table defines the lock holder and the lock requester as transaction session numbers. The lock log table can be joined with the DBC.DBase, DBC.TVM, and DBC.EventLog tables to gain additional information about the object IDs and transaction session numbers.