E
edu_ID - Engine dispatchable unit ID monitor element
ID of engine dispatchable unit with which this memory pool is associated.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_MEMORY_POOL table function - Get memory pool information | Always collected |
PD_GET_DIAG_HIST table function - Return records from a given facility | Always collected |
Usage
When returned by the table function MON_GET_MEMORY_POOL, this monitor element is NULL except when the memory pool being described is PRIVATE.
eff_stmt_text - Effective statement text monitor element
The effective text of the SQL statement, if the statement was modified as a result of the statement concentrator.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details | ACTIVITY METRICS BASE |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activity | event_activitystmt | Always collected |
Usage
If the statement concentrator is enabled and if the statement text has been modified as a result of the statement concentrator, then this monitor element contains the effective statement text. Otherwise, this monitor element contains a text string which is 0 bytes long.
effective_isolation - Effective isolation monitor element
The effective isolation level for this statement.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
MON_GET_PKG_CACHE_STMT table function - Get SQL statement activity metrics in the package cache | Always collected |
MON_GET_PKG_CACHE_STMT_DETAILS table function - get detailed metrics for package cache entries | Always collected |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Locking | - | - |
Package cache | - | COLLECT BASE DATA |
Usage
Use this element to understand the isolation level that was used during the execution of the statement.
effective_lock_timeout - Effective lock timeout monitor element
The effective lock timeout value for this activity. This value is reported in seconds.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
Usage
effective_query_degree - Effective query degree monitor element
The effective query degree of parallelism for this activity.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Locking | - | - |
elapsed_exec_time - Statement Execution Elapsed Time monitor element
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Statement, Timestamp |
Application | appl | Statement, Timestamp |
DCS Database | dcs_dbase | Statement, Timestamp |
DCS Application | dcs_appl | Statement, Timestamp |
DCS Statement | dcs_stmt | Statement, Timestamp |
Data Transmission | stmt_transmissions | Statement, Timestamp |
- Usage
- Use this element, along with other elapsed time monitor elements,
to evaluate the database server's processing of SQL requests and to
help isolate performance issues. Subtract this element from the host_response_time element to calculate the network elapsed time between DB2 Connect and the host database server.Note: For the dcs_dbase, dcs_appl, dcs_stmt and stmt_transmissions levels, the elapsed_exec_time element applies only to z/OS® databases. If the DB2 Connect gateway is connecting to a Windows, Linux®, AIX®, or other UNIX database, the elapsed_exec_time is reported as zero.
empty_pages_deleted - Empty pages deleted monitor element
The number of pseudo empty pages that have been deleted. Pseudo empty pages are pages where all the keys have been pseudo deleted.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_INDEX table function - Get index metrics | Always collected |
empty_pages_reused - Empty pages reused monitor element
The number of pseudo empty pages that have been reused. Pseudo empty pages are pages where all the keys have been pseudo deleted.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_INDEX table function - Get index metrics | Always collected |
entry_time - Entry time monitor element
The time at which this activity entered the system.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
WLM_GET_WORKLOAD_OCCURRENCE _ACTIVITIES table function - Return a list of activities | Always collected |
Usage
estimated_cpu_entitlement - Estimated CPU entitlement monitor element
Table Function | Monitor Element Collection Level |
---|---|
MON_SAMPLE_SERVICE_CLASS_METRICS - Get sample service class metrics | Always collected |
estimatedsqlcost_threshold_id - Estimated SQL cost threshold ID monitor element
The ID of the ESTIMATEDSQLCOST threshold that was applied to the activity.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
Usage
Use this element to understand which ESTIMATEDSQLCOST threshold, if any, was applied to the activity.
estimatedsqlcost_threshold_value - Estimated SQL cost threshold value monitor element
The upper bound of the ESTIMATEDSQLCOST threshold that was applied to the activity.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
Usage
Use this element to understand the value of the ESTIMATEDSQLCOST threshold applied to the activity, if any.
estimatedsqlcost_threshold_violated - Estimated SQL cost threshold violated monitor element
This monitor element returns 'Yes' to indicate that the activity violated the ESTIMATEDSQLCOST threshold. 'No' indicates that the activity has not yet violated the threshold.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
Usage
Use this element to determine if the activity violated the ESTIMATEDSQLCOST threshold that was applied to the activity.
event_id - Event ID monitor element
An identifier associated with an event that is used in conjunction with other monitor elements to uniquely identify the event. This monitor element forms a part of the xmlid monitor element in the interfaces that return that element.
Event Type | Logical Data Grouping | Monitor Element Collection Level |
---|---|---|
Change History | changesummary dbdbmcfg ddlstmtexec evmonstart regvar txncompletion utillocation utilphase utilstart utilstop |
Always collected |
Locking |
|
Always collected |
Package Cache |
|
Always collected |
Unit of Work | event_uow | Always collected |
Usage
The value for this identifier is different depending on the type of event record in which it appears:- Locking event monitor records
- An numeric identifier for the event. The ID is recycled at database activation time. Uniqueness is guaranteed by the combination of event_timestamp, event_id, member, and event-type.
- Unit of work event monitor records
- An alias of the UOW ID that is unique per connection. Uniqueness is guaranteed by the combination of event_timestamp, event_id, event-type, member, and appl_id.
- Package cache event monitor record
- An numeric identifier for the event. The ID is recycled at database activation time. Uniqueness is guaranteed by the combination of event_timestamp, event_id, member, and event-type.
- Change history event monitor record
- An numeric identifier for the event. The ID is recycled at database activation time. The uniqueness of events is guaranteed by the combination of event_timestamp, event_id, member, and event-type.
event_monitor_name - Event Monitor Name monitor element
The name of the event monitor that created the event data stream.
- Element identifier
- event_monitor_name
- Element type
- information
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Event Log Header | event_log_header | Always collected |
- Usage
- This element allows you to correlate the data that you are analyzing to a specific event monitor in the system catalog tables. This is the same name that can be found in the NAME column of the SYSCAT.EVENTMONITORS catalog table, which is the name specified on the CREATE EVENT MONITOR and SET EVENT MONITOR statements.
event_time - Event Time monitor element
The date and time an event occurred.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Tablespaces | event_tablespace | - |
Tables | event_table | - |
- Usage
- You can use this element to help relate events chronologically.
event_timestamp - Event timestamp monitor element
The time that this event record was generated by the database manager.
Event Type | Logical Data Grouping | Monitor Element Collection Level |
---|---|---|
Change History | changesummary dbdbmcfg ddlstmtexec evmonstart regvar txncompletion utillocation utilphase utilstart utilstop |
Always collected |
Locking |
|
Always collected |
Package Cache |
|
Always collected |
Unit of Work |
|
Always collected |
event_type - Event Type monitor element
The event type of the event that is being reported. Reported by the change history, locking, and package cache event monitors only.
Many even monitors capture only one type of event. For example, a unit of work event monitor records a unit of work completion event that captures data related to the unit of work when it is completed. Other event monitors, such as the database, table, buffer pool or table space event monitors each capture one type of event after database deactivation.
Event Monitor | Logical Data Grouping | Monitor Element Collection Level |
---|---|---|
Change History | changesummary dbdbmcfg ddlstmtexec evmonstart regvar txncompletion utillocation utilphase utilstart utilstop |
Always collected |
Locking |
|
Always collected |
Unit of work | Not applicable. For more information, see the usage notes for this event monitor in Table 22. | Always collected |
Package cache |
|
Always collected |
Event monitor | Possible values for event_type element | Usage notes |
---|---|---|
Change history |
|
The event_type monitor element is included as a column in the output of this event monitor. |
Locking |
|
The event_type monitor element is included as a column in the output of this event monitor when it writes to either regular or unformatted event (UE) tables. It is also included in the output created by the routines EVMON_FORMAT_UE_TO_TABLES or EVMON_FORMAT_UE_TO_XML. |
Package cache |
|
The event_type monitor element is included as a column in the output of this event monitor when it writes to unformatted event (UE) tables, but not regular tables. It is also included in the output created by the routines EVMON_FORMAT_UE_TO_TABLES or EVMON_FORMAT_UE_TO_XML. |
Unit of work |
|
The event_type monitor element is included as a column in the output of this event monitor only when it writes to an unformatted event (UE) table. Moreover, it is included only in the UE table created by this event monitor; it is not included in the output created by the routines EVMON_FORMAT_UE_TO_TABLES or EVMON_FORMAT_UE_TO_XML. |
evmon_activates - Number of event monitor activations monitor element
The number of times an event monitor has been activated.
- Element identifier
- evmon_activates
- Element type
- counter
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Tables | event_table | Always collected |
Tablespaces | event_tablespace | Always collected |
Bufferpools | event_bufferpool | Always collected |
Deadlocks | event_deadlock | Always collected |
Deadlocks | event_dlconn | Always collected |
Deadlocks with Details | event_detailed_dlconn | Always collected |
Statements | event_stmt_history | Always collected |
Connections* | - | |
Transactions* | - | |
Statistics* | - | |
Threshold violations* | - | |
* This event monitor updates the evmon_activates column only in the catalog table SYSCAT.EVENTMONITORS. The monitor element is not included in any of the logical data groups that are written to event monitor output tables. |
- Usage
- Use this element to correlate information returned by the event
monitors listed in Table 23. This
element is applicable only to write-to-table event monitors; it is
not maintained for event monitors that write to a file or pipe. All of the event monitors in Table 23 update the evmon_activates column of the SYSCAT.EVENTMONITORS catalog table when the event monitor is activated. This change is logged, so the DATABASE CONFIGURATION displays:
If an event monitor is created with the AUTOSTART option, and the first user CONNECTS to the database and immediately DISCONNECTS so that the database is deactivated, a log file is produced.All committed transactions have been written to disk = NO
Unless otherwise noted, these event monitors also include the value for evmon_activates as a column in the tables to which event data is written.
Event monitors not included in this table do not report the evmon_activates monitor element.
evmon_flushes - Number of Event Monitor Flushes monitor element
The number of times the FLUSH EVENT MONITOR SQL statement has been issued.
- Element identifier
- evmon_flushes
- Element type
- information
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Tables | event_table | Always collected |
Tablespaces | event_tablespace | Always collected |
Bufferpools | event_bufferpool | Always collected |
- Usage
- This identifier increments with each successive FLUSH EVENT MONITOR SQL request processed by the database manager after an application has connected to the database. This element helps to uniquely identify database, table, table space and buffer pool data.
evmon_wait_time - Event monitor wait time monitor element
The amount of time that an agent waited for an event monitor record to become available.
A wait occurs when the agent tries to write an event monitor record and the agent is blocked until a fast writer record becomes available. Fast writers are used for high volume, parallel writing of event monitor data to tables, files, or pipes.
The unit of measurement is milliseconds.
Event Type | Event monitor output type | Logical Data Grouping | Monitor Switch |
---|---|---|---|
Unit of work | TABLE, FILE, PIPE | uow_metrics | REQUEST METRICS BASE |
Unit of work | UE TABLE, processed by the EVMON_FORMAT_UE_TO_XML function | Reported in the system_metrics document Always collected | REQUEST METRICS BASE |
Unit of work | UE TABLE, processed by the EVMON_FORMAT_UE_TO_TABLES function | Reported in the metrics document of the UOW_EVENT table and in the UOW_METRICS table Always collected | REQUEST METRICS BASE |
Package cache | TABLE, FILE, PIPE | pkgcache_metrics | ACTIVITY METRICS BASE |
Package cache | UE TABLE, processed by the EVMON_FORMAT_UE_TO_XML function | Reported in the activity_metrics document Always collected | ACTIVITY METRICS BASE |
Package cache | UE TABLE, processed by the EVMON_FORMAT_UE_TO_TABLES function | Reported in the metrics document of the PKGCACHE_EVENT table and in the PKGCACHE_METRICS table Always collected | ACTIVITY METRICS BASE |
Activities | TABLE, FILE, PIPE | event_activitymetrics | ACTIVITY METRICS BASE |
Activities | TABLE, FILE, PIPE | event_activity (reported in the DETAILS XML document) | ACTIVITY METRICS BASE |
Statistics | TABLE, FILE, PIPE | event_scstats (reported in the DETAILS XML document) | REQUEST METRICS BASE |
Statistics | TABLE, FILE, PIPE | event_wlstats (reported in the DETAILS XML document) | REQUEST METRICS BASE |
evmon_waits_total - Event monitor total waits monitor element
The number of times that an agent waited for an event monitor record to become available.
A wait occurs when the agent tries to write an event monitor record and the agent is blocked until a fast writer record becomes available. Fast writers are used for high volume, parallel writing of event monitor data to tables, files, or pipes.
Event Type | Event monitor output type | Logical Data Grouping | Monitor Switch |
---|---|---|---|
Unit of work | TABLE | uow_metrics | REQUEST METRICS BASE |
Unit of work | UE TABLE, processed by the EVMON_FORMAT_UE_TO_XML function | Reported in the system_metrics document Always collected | REQUEST METRICS BASE |
Unit of work | UE TABLE, processed by the EVMON_FORMAT_UE_TO_TABLES function | Reported in the metrics document of the UOW_EVENT table and in the UOW_METRICS table Always collected | REQUEST METRICS BASE |
Package cache | TABLE | pkgcache_metrics | ACTIVITY METRICS BASE |
Package cache | UE TABLE, processed by the EVMON_FORMAT_UE_TO_XML function | Reported in the activity_metrics document Always collected | ACTIVITY METRICS BASE |
Package cache | UE TABLE, processed by the EVMON_FORMAT_UE_TO_TABLES function | Reported in the metrics document of the PKGCACHE_EVENT table and in the PKGCACHE_METRICS table Always collected | ACTIVITY METRICS BASE |
Activities | TABLE | event_activitymetrics | ACTIVITY METRICS BASE |
Activities | TABLE | event_activity (reported in the DETAILS_XML document) | ACTIVITY METRICS BASE |
Statistics | TABLE | event_scstats (reported in the DETAILS_XML document) | REQUEST METRICS BASE |
Statistics | TABLE | event_wlstats (reported in the DETAILS_XML document) | REQUEST METRICS BASE |
exec_list_cleanup_time - Execution list cleanup time monitor element
Time when the routine execution list was last pruned.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ROUTINE table function - get aggregated execution metrics for routines | Always collected |
MON_GET_ROUTINE_DETAILS table function - get aggregated execution metric details for routines | Always collected |
Usage
A routine execution list is a list of all statements (sections) that are executed by an invoked procedure, external function, compiled function, compiled trigger, or anonymous block. Section information appears in the routine execution list if you set the value of the mon_rtn_execlist configuration parameter to ON.
Routine execution list data cannot use more than 20% of the available monitor heap. If the value of the mon_heap_sz configuration parameter is set to AUTOMATIC, the routine execution list data can take up to 20% of the value of the instance_memory configuration parameter.
Regular pruning is expected for databases with workloads that invoke many complex procedures and for databases where multiple features that use the monitor heap are enabled. If the value of the exec_list_cleanup_time configuration parameter is being updated too frequently, ensure that the values of the mon_heap_sz and the instance_memory database configuration parameters are AUTOMATIC, or increase the value of the mon_heap_sz configuration parameter.
exec_list_mem_exceeded - Execution list memory exceeded monitor element
Identifies if there was insufficient memory in the monitor heap to capture all statement information for the routine.
- Y
- Insufficient memory to capture all statement information
- N
- For all other cases
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ROUTINE table function - get aggregated execution metrics for routines | Always collected |
MON_GET_ROUTINE_DETAILS table function - get aggregated execution metric details for routines | Always collected |
Usage
This element is set to 'Y' when routine monitoring could not keep track of all the statements executed by the routine. This tracking inability can occur when the routine execution list data for the database reaches 20% of the available monitor heap or the monitor heap is full. In order for routine monitoring to maintain more entries in its execution list, you can increase the monitor heap size using the mon_heap_sz database configuration parameter, or set the mon_heap_sz and the instance_memory database configuration parameters to AUTOMATIC. If mon_heap_sz is already set to AUTOMATIC, you can increase the instance_memory configuration parameter.
executable_id - Executable ID monitor element
An opaque binary token generated on the data server that uniquely identifies the SQL statement section that was executed. For non-SQL activities, a 0-length string value is returned.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | Always collected |
MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list | Always collected |
MON_GET_PKG_CACHE_STMT table function - Get SQL statement activity metrics in the package cache | Always collected |
MON_GET_PKG_CACHE_STMT_DETAILS table function - get detailed metrics for package cache entries | Always collected |
MON_GET_ROUTINE_EXEC_LIST table function - get list of statements executed by routine | Always collected |
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list | Always collected |
WLM_GET_SERVICE_CLASS_AGENTS table function - list agents running in a service class | Always collected |
WLM_GET_WORKLOAD_OCCURRENCE _ACTIVITIES table function - Return a list of activities | Always collected |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activity | event_activitystmt | - |
Package cache | - | COLLECT BASE DATA |
Usage
Use this monitor element as input to different monitoring interfaces to obtain data about the section. The MON_GET_PKG_CACHE_STMT table function, which is used to get SQL statement activity metrics in the package cache, takes the executable ID as input.
executable_list_size - Size of executable list monitor element
The number of entries that are present within the executable ID listing for a particular unit of work.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Unit of Work | uow |
executable_list_truncated - Executable list truncated monitor element
Indicates whether the executable list is truncated. Possible values are YES or NO. The list can be truncated if there is insufficient memory available to store the entire executable list during processing.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Unit of Work | uow |
execution_id - User Login ID monitor element
The ID that the user specified when logging in to the operating system. This ID is distinct from auth_id, which the user specifies when connecting to the database.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Application | appl_info | Basic |
Application | appl | Basic |
DCS Application | dcs_appl_info | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Connections | event_connheader | - |
- Usage
- You can use this element to determine the operating system userid of the individual running the application that you are monitoring.