IBM Support

DSM Monitor - Alerts - Locking

Question & Answer


Question

What are descriptions of locking alerts reference various time spent metrics?

Answer

You can read more about time spent metrics here in the Knowledge Center:

http://www-01.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.mon.doc/doc/c0055434.html?lang=en


Lock Waits over Request Time

This alert fires if it detects a connection where the ratio of time spent waiting on locks / total request time is greater than the specified limit.  The evaluation is done based on the cumulative times spent during the life of each connection.  So long lived connections that suddenly begin experiencing excessive lock wait time will not be detected as quickly as newer connections.

The names of the time spent metrics involved are:

  • lock_wait_time
  • total_rqst_time

Usage

This alert can detect users or applications that are consistently experiencing excessive lock wait times.

Default Settings

Off

Warning threshold: 5%

Critical threshold: 10%

Configuration

Edit monitoring profile > Alerts Monitoring  > Applications with excessive lock waits over request time


Time Waited on Locks

This alert fires if it detects a statement that has spent more than X seconds waiting on locks.

Usage

Find out about statements that are victims of lock contention.

Default Settings

Off

Warning threshold: 60 seconds

Critical threshold: 150 seconds

Configuration

Edit monitoring profile > Alerts Monitoring  > Time Waited on Locks


Rate of Table Lock Events

This alert fires if the number of lockwait a table is involved in increases, or there is deadlock.

Usage

This alert can report dead lock or abnormal lock wait.  This alert relies on Event monitor to collect data.

Default Settings

Off

Criteria of alert: Critical alert if lock wait happens 5 times of historical rate, warning alert if lock wait happens 3 time of historical rate.  Critical alert if there is dead lock.
This alert requires Enterprise license, and also requires repository database.
To make this alert work, you need to turn on the following:
Edit monitoring profile > repository persistence: ON Edit monitoring profile > Persistence -> monitoring data: ON and Locking event monitoring data: ON Edit monitoring profile > Alerts Monitoring  > Rate of table lock events increases: ON

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS5Q8A","label":"IBM Data Server Manager"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
30 December 2019

UID

ibm11165702