Return
-
Title
There is no Lock History available for a DB2 instance although Deadlocks and Timeouts are occurring -
Description
When going to the "Locks (History)" dashboard, the following message is displayed:
"There is no data to display".
However, the Real Time dashboard shows that there are lots of Deadlocks and Lock Timeouts occurring on the DB2 instance. -
Cause
Lock history is only available for locks that exceed the duration of 90 seconds.
This can be configured in the Agent properties.
Because DB2 monitors deadlocks every 10 seconds by default (check database parameter DLCHKTIME), chances are that Foglight will not have a record of those locks. -
Resolution
Lower the threshold for the lock history - this is recommended for a short period of time.
- Go to "Administration | Agents | Status".
- Select the DB2 agent and click the "Edit Properties" button.
- Click the "Modify the private properties for this agent" link.
- Scroll down to section "History Locks Wait Details".
- Set the "Minimal lock duration (seconds)" option to a value lower than 90 seconds to match the DB2 monitor deadlock (it is set to 10 seconds by default - check database parameter DLCHKTIME).
- Click the "Save" button.