Specifies a threshold time delay value (in seconds). Lock requests that are blocked for less than this amount of time are not logged. This prevents the log table from being filled with data for insignificantly blocked locks.
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 Range
0 through 1,000,000 seconds
| IF you set LockLogger Delay Filter Time to… | THEN blocked lock requests with a delay of… |
|---|---|
| 0 seconds | 0 seconds would not be logged. |
| 10 seconds | 10 seconds or less would not be logged. |
| 1,000,000 seconds | 1,000,000 seconds or less would not be logged. |
Default
0 seconds
Changes Take Effect
After the DBS Control Record has been written.
Usage Notes
The LockLogger Delay Filter Time field has a dependency on the Lock Logger Delay field and the LockLogger field.
| IF the LockLogger field is… | THEN LockLogger Delay Filter Time field is… |
|---|---|
| FALSE, and the LockLogger Delay Filter field is TRUE | ineffective. |
| TRUE, and the LockLogger Delay Filter field is FALSE | ineffective. |
| TRUE, and the LockLogger Delay Filter field is TRUE | effective. |