How to use db2 deadlock monitor

This article mainly introduces "db2 deadlock monitor use method", in daily operation, I believe many people in db2 deadlock monitor use method problems have doubts, small make up consult all kinds of information, sort out simple and easy to use operation method, hope to answer "db2 deadlock monitor use method" doubts helpful! Next, please follow the small series to learn together!

DB2DETAILDEADLOCK event monitor disable and rebuild

I. Impact of open monitors on database performance:

DB2 commonly uses two tools to collect monitoring information: snapshot monitors and event monitors. The former is used to obtain monitoring data for a specific point in time, and the latter is used to obtain monitoring data for a specific event. No matter which monitoring tool users use to collect data related to database system monitors, it will cause certain system overhead, including memory, CPU, and extra call processing for obtaining monitoring data. In order to control the collection of necessary monitoring information and reduce unnecessary system overhead, DB2 introduces a monitor switch mechanism. Each switch has two states: "ON" and "OFF." When the switch is in "OFF", the information of the relevant monitoring element under its control will not be collected. Monitor status at the DB2 instance level (database manager) can be obtained with "db2 get dbm monitor switches." When a monitor opens a switch under an instance, the switch corresponding to the instance level will also be opened.

For example:

Collected DBM System Monitor Information

db List of switches for partition number 0

BUFFERPOOL = OFF

Lock = OFF

Sort Information (SORT) = OFF

SQL statement info (STATEMENT) = OFF

Table activity information (TABLE) = OFF

Get Timestamp Information (Timestamp)= ON 2005-06-26 10:36:47.019334