Foglight for DB2 (Cartridge) 5.9.5.10


Metric	Description
DATABASE_NAME	The name of the monitored database
MEMBER	The database partition or member number.
METRIC_NAME	The event name to which the TOTAL_TIME metric value refers.
PARENT_METRIC_NAME	The identifier of the parent for the TOTAL_TIME metric, whose value contains the TOTAL_TIME value as a subset.
TOTAL_TIME	The total time value (in seconds), which corresponds to METRIC_NAME.
COUNT	The number of occurrences of this type of event.
COUNT_RATE	The rate of the number of occurrences of this type of event.
TOTAL_TIME_RATE	The rate (per second) of the total time spent.
CATEGORY	The category of the event. Values: I/O wait - The amount of time spent waiting for IO. Subcategories provide additional information. Other wait - The aggregate of several events that do not typically have a high impact on performance. Subcategories provide additional information. WLM wait - The amount of time spent waiting for the WLM queue. pureScale wait - The amount of time spent waiting for various functions within the cluster. Subcategories provide additional information. Idle - The amount of time the client waited that was not spent within DB2 database server. Network wait - The amount of time spent waiting for network protocols. Subcategories provide additional information. Lock wait - The amount of time spent waiting for locks. Log wait - The amount of time spent waiting for the log. Subcategories provide additional information. Transaction - The amount of time spent on the commit or rollback of the transaction. Compile - The amount of time spent doing explicit or implicit compiles. Memory wait - The amount of time spent waiting for an internal latch. Administration - The amount of time spent processing administration tasks. Subcategories provide additional information. Execute - The amount of time spent executing the request. Subcategories provide additional information. FCM wait - The amount of time spent waiting for the FCM communications layer. This is only applicable on the partition level. Subcategories provide additional information. IPC - The amount of time spent waiting for IPC channels.

History Locks Wait Collection

The following table provides a list of the History Locks Wait metrics that are collected, and a description for each.

Metric

Description

DB_NAME

The name of the monitored database.

DBPARTITIONNUM

The database partition from which the data was retrieved for this row.

LOCK_NAME

The ID of the lock.

AGENT_ID

A system-wide unique ID for the locked wait application. On a single-partitioned database, this ID consists of a 16-bit counter. On a multi-partitioned database, this ID consists of the coordinating partition number concatenated with a 16-bit counter. In addition, this ID will be the same on every partition where the application may make a secondary connection.

The application handle (synonymous with agent ID) can be used to uniquely identify an active application. It can also be used as input to the FORCE APPLICATION command or API. On multi-node systems, this command can be issued from any node where the application has a connection. Its effect is global.

STMT_TEXT

The full statement text of the locked agent.

LOCK_MODE

The type of lock being held.

This mode can assist in determining the source of the contention for resources.

One of the following is indicated, depending on the type of monitoring information being examined:

•

The type of lock another application holds on the object that this application is waiting to lock (for application-monitoring and deadlock-monitoring levels).

•

The type of lock held on the object by this application (for object-lock levels).

Mode Types:

NON - No Lock

IS - Intention Share Lock

IX - Intention Exclusive Lock

S - Share Lock

SIX - Share with Intention Exclusive Lock

X - Exclusive Lock

IN - Intent None

Z - Super Exclusive Lock

U - Update Lock

NS - Next Key Share Lock

NX - Next Key Exclusive Lock

W - Weak Exclusive Lock

NW - Next Key Weak Exclusive Lock

LOCK_OBJECT_TYPE

The type of object against which the application holds a lock (for object-lock-level information) or the type of object for which the application is waiting to obtain a lock (for application-level and deadlock-level information).

This element can assist in determining the source of the contention for resources.

The object type IDs are defined in sqlmon.h. The object may be one of the following types:

Internal (another type of lock held internally by the database manager)

INPLACE_REORG_LOCK INTERNAL_LOCK

The agent ID of the blocker that holds the object or the application handle of the agent that holds a lock for which this application is waiting.

The lock monitor group must be turned on to obtain this information.

This element can assist in determining which applications are in contention for resources.

If the value is 0 (zero) and the application is waiting for a lock, the lock is being held by an in-doubt transaction.

APPL_ID_HOLDING_LK

The application ID of the application that is holding a lock on the object this application is waiting to obtain.

LOCK_WAIT_START_TIME

The date and time that this application started waiting to obtain a lock on the locked object.

This element can assist in determining the severity of resource contention.

LOCK_MODE_REQUESTED

The lock mode being requested by the application.

Mode Types:

•

NON - No Lock

•

IS - Intention Share Lock

•

IX - Intention Exclusive Lock

•

S - Share Lock

•

SIX - Share with Intention Exclusive Lock

•

X - Exclusive Lock

•

IN - Intent None

•

Z - Super Exclusive Lock

•

U - Update Lock

•

NS - Next Key Share Lock

•

NX - Next Key Exclusive Lock

•

W - Weak Exclusive Lock

•

NW - Next Key Weak Exclusive Lock

LOCK_ESCALATION

Indicates whether a lock request was made as part of a lock escalation.

Use this element to help you understand the cause of deadlocks. If you experience a deadlock that involves applications performing lock escalation, you might want to increase the amount of lock memory or change the percentage of locks that any one application can request.

DATA_PARTITION_ID

The ID of the data partition for which a lock occurred.

This element is only applicable to partitioned tables.

A value of -1 represents a lock of the whole table and not a specific partition.

TABNAME

The name of the table.

Along with TABSCHEMA, this element can assist in determining the source of the contention for resources.

At the application level, application-lock level, and deadlock-monitoring level, this is the table that the application is waiting to lock, because it is currently locked by another application. For snapshot monitoring, this item is valid only when the “lock” monitor group information is turned on, and when LOCK_OBJECT_TYPE indicates that the application is waiting to obtain a table lock.

TABSCHEMA

The schema of the table.

Along with TABNAME, this element can assist in determining the source of the contention for resources.

TBSP_NAME

The name of a tablespace.

This element can assist in determining the source of the contention for resources.

It is equivalent to the TBSPACE column in the SYSCAT.TABLESPACES database catalog table. At the application level, application-lock level, and deadlock-monitoring level, this is the name of the tablespace that the application is waiting to lock. Another application currently holds a lock on this tablespace.

At the lock level, this is the name of the tablespace against which the application currently holds a lock.

At the tablespace level (when the buffer pool monitor group is on), this is the name of the tablespace for which information is returned.

This is not returned for a table lock held on a partitioned table.

LOCK_ATTRIBUTES

The lock attributes of the lock wait. If there are no locks, the text identifier is NONE. Otherwise, it is any combination of the following, separated by a '+':

•

•

•

•

•

•

•

•

During a lock conversion operation, the type of lock held before the conversion is completed. For example, during an update or delete operation, it is possible to wait for an X lock on the target row. If the transaction is holding an S or V lock on the row, that would require a conversion. LOCK_CURRENT_MODE is assigned a value of S or V while the lock waits to be converted to an X lock.

LOCK_RELEASE_FLAGS

Each release flag is based on a bit flag value defined in sqlmon.h. The following are possible release flag settings (API constant description):

SQLM_LOCKRELFLAGS_SQLCOMPILER - Locks by SQL compiler

SQLM_LOCKRELFLAGS_UNTRACKED - Non-unique, untracked locks

SUBSECTION_NUMBER

Identifies the subsection associated with the returned information.

This number relates to the subsection number in the access plan that can be obtained with db2expln.

LOCK_DURATION

The duration of the lock wait.

History Locks Summary Collection

The following table provides a list of the History Locks Summary metrics that are collected, and a description for each.


Metric	Description
DB_NAME	The name of the monitored database.
DBPARTITIONNUM	The database partition from which the data was retrieved.
LONGEST_DURATION	A metric for internal use.
NUM_OF_EXCEEDING_LOCKS	A metric for internal use.