Information written to tables for a locking event monitor
Information written by the locking
event monitor when the WRITE TO TABLE option is specified.
When you choose WRITE TO TABLE as the output type for the
locking event monitor, by default, five tables are produced, each
containing monitor elements from one or more logical data groups:
| Default table name | Logical data groups reported |
|---|---|
| LOCK_evmon-name | Refer to lock in Event monitor logical data groups and monitor elements |
| LOCK_PARTICIPANTS_evmon-name | Refer to lock_participants in Event monitor logical data groups and monitor elements |
| LOCK_PARTICIPANT_ACTIVITIES_evmon-name | Refer to lock_participant_activities
Event monitor logical data groups and monitor elements |
| LOCK_ACTIVITY_VALUES_evmon-name | Refer to lock_activity_values in
Event monitor logical data groups and monitor elements |
| CONTROL_evmon-name | The CONTROL logical group consists of selected elements from one or more of the event_dbheader, event_start and event_overflow logical data groups. |
Important: Even though all five tables are produced
by default, you must still ensure that data collection is enabled
for the kind of lock information that you want to gather. Otherwise,
some of the columns contain null values.
To restrict the output
of the event monitor to specific tables, specify the names of the
logical groups for which you want tables produced for the CREATE EVENT
MONITOR or ALTER EVENT MONITOR statement. Refer to the reference topics
for those statements for details.Control table
| Column name | Data type | Description |
|---|---|---|
| PARTITION_KEY | INTEGER | partition_key - Partitioning key |
| EVENT_MONITOR_NAME | VARCHAR(128) | event_monitor_name - Event monitor name |
| MESSAGE | VARCHAR(128) | message - Control table message |
| MESSAGE_TIME | TIMESTAMP | message_time - Timestamp control table message |
| PARTITION_NUMBER | SMALLINT | partition_number - Partition number |