DB2 Version 9.7 for Linux, UNIX, and Windows

table_name - Table name monitor element

The name of the table.

Table 1. Table Function Monitoring Information
Table Function	Monitor Element Collection Level
MON_GET_TABLE table function - Get table metrics	Always collected
MON_GET_INDEX table function - Get index metrics	Always collected

Table 2. Snapshot Monitoring Information
Snapshot Level	Logical Data Grouping	Monitor Switch
Table	table	Basic
Application	appl	Lock
Lock	appl_lock_list	Lock
Lock	lock	Lock
Lock	lock_wait	Lock

Table 3. Event Monitoring Information
Event Type	Logical Data Grouping	Monitor Switch
Locking	-	-
Tables	event_table	-
Deadlocks¹	lock	-
Deadlocks¹	event_dlconn	-
Deadlocks with Details¹	event_detailed_dlconn	-

1: This option has been deprecated. Its use is no longer recommended and might be removed in a future release. Use the CREATE EVENT MONITOR FOR LOCKING statement to monitor lock-related events, such as lock timeouts, lock waits, and deadlocks.

Usage

Along with table_schema, this element can help you determine the source of 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 only valid when the "lock" monitor group information is set to ON, and when lock_object_type indicates that the application is waiting to obtain a table lock.

For snapshot monitoring at the object-lock level, this item is returned for table-level and row-level locks. The table reported at this level is the table against which this application holds these locks.

For snapshot and event monitoring at the table level, this is the table for which information has been collected. For temporary tables, the format for table_name is "TEMP (n, m)", where:

n is the table space ID
m is the table_file_id element