New activity event monitor elements for joining and pruning activity event monitor tables
To make it easier to join and prune activity event monitor target tables, three columns have been
added to the ACTIVITY, ACTIVITYSTMT, ACTIVITYVALS and ACTIVITYMETRICS tables of the activity
event monitor:
- The COORD_TIME_CREATED timestamp column displays the time when an activity was created on the
coordinator member. It has been added to all activity event monitor tables. For any activity the
COORD_TIME_CREATED value is the same for all tables and across all members. When combined with the
APPLICATION_HANDLE value, the COORD_TIME_CREATED value ensures uniqueness when joining tables. The
values in this column can be used to prune all activity data across all members, based on a specific
timestamp.Note: On the coordinator member the COORD_TIME_CREATED and TIME_CREATED columns have the same value.
- The EVENT_TIMESTAMP timestamp column displays the time when an activity event monitor record was generated on a member. It has been added to all activity event monitor tables. In an environment configured for the Db2 database partitioning feature (DPF), each member generates their own value when the event monitor records are generated. An activity that is recorded on multiple members has different event_timestamp values on each member. Like the COORD_TIME_CREATED value, when combined with the APPLICATION_HANDLE value, the EVENT_TIMESTAMP value ensures uniqueness when joining tables. The values in this column can be used to prune all activity data across all members, based on a specific timestamp
- The APPLICATION_HANDLE column displays the time when the activity event monitor record was
generated by a member. It has been added to all event monitor tables. Note: While the application handle value is currently stored in the AGENT_ID column of the ACTIVITY table, this value does not exist in other tables and uses an old snapshot element name rather than the new name. This is one of the reasons for the deprecation of the AGENT_ID column in Db2 V11.5.2.