Chat now with support
Chat with Support

Spotlight on DB2 6.9.3 - Release Notes

Agents Waiting for Locks alarm

The Agents Waiting for Locks alarm becomes active when the number of registered database agents currently waiting on locks within the database reaches a threshold percentage. Lock waits occur for a number of reasons, including internal database contention.

This alarm has been predefined with a Low severity level. The underlying metric for this alarm can be adjusted to suit your environment by using the Metric Editor.

What you can do

The application agents could be experiencing concurrency problems. Try to identify the applications that are holding locks for long periods of time and determine the cause. One possible solution is to use small units of work (for example, frequent COMMITs) to reduce concurrency issues.

Access the Client Application Analysis drilldown to identify the applications holding locks and review statistics about those locks.


Related topics


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating