This topic provides additional information about the Lock Info data collector that may be helpful.
|Number of sessions||1|
|Character set||* (default character set)|
|Table name to write lock log entries||lockLoggerTableyyyyMMddHHmmss|
|Utility to create table||Yes|
|Time constraint at or later than||One hour before previous collection time|
|Time constraint at or prior to||* (current time)|
|Object constraint||* (all objects)|
The DCS uses the following process to collect lock information against Teradata Database 14.0 and earlier. First, the DCS executes the dumplocklogb utility and specifies that the lock information is inserted into a new table. The next time the Lock Info collector executes, it runs the dumplocklogb utility again, specifying that the lock information is inserted into a second table. Lock data from an hour prior to the previous collection through the current time is inserted into this second table. The Lock Info collector then compares the two tables, finds any rows that are present in the second table but not in the table from the previous collection, and then drops the table from the previous collection. This process is repeated for each execution of the collector.
When the Lock Info collector is not executing, there should be only one lock table in the database of the Teradata Database user being used for data collection. The table name starts with "lockLoggerTable" and ends with a unique timestamp. If there is more than one lock table, older tables can be safely dropped as they are not being used by the DCS.