16.10 - LockLogger - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
zll1480972831047.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval

Purpose

Determines whether the Lock Logger feature of Teradata Database 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 Database Administration and the BEGIN QUERY LOGGING statement in SQL Data Definition Language - Syntax and Examples.
  • For more information on the Lock Viewer portlet, see Teradata Viewpoint User Guide.

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 Teradata 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.