R
range_adjustment - Range Adjustment monitor element
This value represents the offset into the container array in which a range actually starts.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_container_id - Range Container monitor element
An integer that uniquely defines a container within a range.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_end_stripe - End Stripe monitor element
This value represents the number of the last stripe in a range.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_max_extent - Maximum Extent in Range monitor element
This value represents the maximum extent number that is mapped by a range.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_max_page_number - Maximum Page in Range monitor element
This value represents the maximum page number that is mapped by a range.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_num_containers - Number of Containers in Range monitor element
This value represents the number of containers in the current range.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_number - Range Number monitor element
This value represents the number of a range within the table space map.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_offset - Range Offset monitor element
The offset from stripe 0 of the beginning of the stripe set to which a range belongs.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_start_stripe - Start Stripe monitor element
This value represents the number of the first stripe in a range.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
range_stripe_set_number - Stripe Set Number monitor element
This value represents the stripe set in which a range resides.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | tablespace_range | Basic |
- Usage
- This element is applicable only to a DMS table space.
reads_on_standby_enabled - reads on standby enabled monitor element
Indicates whether the reads on standby feature is enabled.
Table function | Monitor element collection level |
---|---|
MON_GET_HADR table function - Returns high availability disaster recovery (HADR) monitoring information | Always collected |
Usage
- Y (Yes)
- N (No)
reclaim_wait_time - Reclaim wait time monitor element
In a DB2® pureScale® environment, this element represents the amount of time spent waiting on page locks, where the lock request caused a page to be reclaimed. The unit of measurement for time is in milliseconds.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activities | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
Activities | event_activitymetrics | ACTIVITY METRICS BASE |
Statistics | event_scstats (reported in the metrics document) | REQUEST METRICS BASE |
Statistics | event_wlstats (reported in the metrics document) | REQUEST METRICS BASE |
Unit of work | - | Always collected |
Usage
The time spent waiting for reclaims on space map pages is counted separately and reported in the spacemappage_reclaim_wait_time monitor element.
reclaimable_space_enabled - Reclaimable space enabled indicator monitor element
If the table space is enabled for reclaimable storage, then this monitor element returns a value of 1. Otherwise, it returns a value of 0.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_TABLESPACE table function - Get table space metrics | Always collected |
regvar_collection_type - Registry variable collection type monitor element
Indicates when the registry variable value was collected.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Change History | REGVAR | Always collected |
Usage
The change history event monitor collected this value as:- I
- The initial value that was captured when the event monitor was activated.
- U
- Updated value
regvar_level - Registry variable level monitor element
Indicates the level of the registry variable.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Change History | REGVAR | Always collected |
Usage
For the change history event monitor, the level of the registry variable is one of:- E
- Environment
- G
- Global
- I
- Instance-level
- P
- Database partition
regvar_name - Registry variable name monitor element
The name of the registry variable.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Change History | REGVAR | Always collected |
Usage
For the change history event monitor, this element identifies the registry variable that was updated as part of a REGVAR event, or captured at event monitor startup as part of a REGVARVALUES event. These events represent the following:- REGVAR
- Changing a registry variable value
- REGVARVALUES
- Capturing registry variable values at event monitor startup
regvar_old_value - Registry variable old value monitor element
The old value for the registry variable.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Change History | REGVAR | Always collected |
Usage
For the change history event monitor, if the registry variable value was not set, this value is an empty string.regvar_value - Registry variable value monitor element
This is the value for the registry variable.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Change History | REGVAR | Always collected |
Usage
For the change history event monitor, if the value was not set, this value is an empty string.Only immediate registry variable updates generate REGVAR events.
rej_curs_blk - Rejected Block Cursor Requests monitor element
The number of times that a request for an I/O block at server was rejected and the request was converted to non-blocked I/O.
- Element identifier
- rej_curs_blk
- Element type
- counter
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Application | appl | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Connection | event_conn | Always collected |
- Usage
- If there are many cursors blocking
data, the communication heap may
become full. When this heap is full, an error is not returned. Instead,
no
more I/O blocks are allocated for blocking cursors. If cursors are
unable
to block data, performance can be affected.
If a large number of cursors were unable to perform data blocking, you may be able to improve performance by:
- Increasing the size of the query_heap database manager configuration parameter.
rem_cons_in - Remote Connections To Database Manager monitor element
The current number of connections initiated from remote clients to the instance of the database manager that is being monitored.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database Manager | db2 | Basic |
Usage
Shows the number of connections from remote clients to databases in this instance. This value will change frequently, so you may need to sample it at specific intervals over an extended period of time to get a realistic view of system usage. This number does not include applications that were initiated from the same instance as the database manager.
When used in conjunction with the local_cons monitor element, these elements can help you adjust the setting of the max_coordagents and max_connections configuration parameters.
rem_cons_in_exec - Remote Connections Executing in the Database Manager monitor element
The number of remote applications that are currently connected to a database and are currently processing a unit of work within the database manager instance being monitored.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database Manager | db2 | Basic |
Usage
This number can help you determine the level of concurrent processing occurring on the database manager. This value will change frequently, so you may need to sample it at specific intervals over an extended period of time to get a realistic view of system usage. This number does not include applications that were initiated from the same instance as the database manager.
When used in conjunction with the local_cons_in_exec monitor element, this element can help you adjust the setting of the max_coordagents configuration parameter.
If max_coordagents is set to AUTOMATIC, then you do not need to make any adjustments. If it is not set to AUTOMATIC and if the sum of rem_cons_in_exec and local_cons_in_exec is close to max_coordagents, you should increase the value of max_coordagents.
remote_lock_time - Remote Lock Time monitor element
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase_remote | Timestamp |
Application | appl_remote | Timestamp |
Usage
Use this element to determine how much actual time is spent at this data source in a remote lock.
remote_locks - Remote Locks monitor element
This element contains a count of the total number of remote locks that the federated server has called at this data source on behalf of any application since the start of the federated server instance or the last reset of the database monitor counters, whichever is latest.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase_remote | Basic |
Application | appl_remote | Basic |
- Usage
- Use this element to determine how many remote locks were made remotely at the data source.
remote_member - Remote member monitor element
The numeric identifier for the database member to which data was sent or from which data was received, using the fast communication manager (FCM).
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_FCM_CONNECTION_LIST - Get details for all FCM connections | Always collected |
Usage
All the metrics returned by the MON_GET_FCM_CONNECTION_LIST table function apply to the FCM connection between the members described in the member and remote_member monitor elements.
reopt - Reopt bind option monitor element
The REOPT bind option used to precompile this package. Possible values are: NONE, ONCE, and ALWAYS.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Locking | lock_participant_activities |
reorg_completion - Reorganization Completion Flag monitor element
Table reorganization success indicator, which includes the reclamation of extents from a multidimensional clustering (MDC) or insert time cluserting (ITC) table. For partitioned tables, this value indicates the completion status for the data partition.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
- Usage
- This element will have a value of 0 if a table or data partition
reorganize operation is successful. If a table or data partition reorganize
operation is unsuccessful, this element will have a value of -1. Success
and failure values are defined in sqlmon.h as follows:
- Success: SQLM_REORG_SUCCESS
- Failure: SQLM_REORG_FAIL
In the case of an unsuccessful table reorganization, see the history file for any diagnostic information, including warnings and errors. This data can be accessed by using the LIST HISTORY command. For partitioned tables, the completion status is indicated per data partition. If index re-create fails on a partitioned table, the failed status is updated on all data partitions. See the administration notification log for further diagnostic information.
reorg_current_counter - Reorganize Progress monitor element
A unit of progress that indicates the amount of reorganization that has been completed. The amount of progress this value represents is relative to the value of reorg_max_counter, which represents the total amount of table reorganization that is to be done.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
Usage
table reorg progress = reorg_current_counter / reorg_max_counter * 100
reorg_end - Table Reorganize End Time monitor element
The end time of a table reorganization including a reorganization to reclaim extents from a multidimensional clustering (MDC) or insert time clustering (ITC) table. For partitioned tables, this time indicates the end time for each data partition reorganization.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_index_id - Index Used to Reorganize the Table monitor element
The index being used to reorganize the table.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_long_tbspc_id - Table Space Where Long Objects are Reorganized monitor element
The table space in which any long objects (LONG VARCHAR or LOB data) will be reorganized. For partitioned tables, this is the table space in which each partition's LONG VARCHAR and LOB will be reorganized.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_max_counter - Total Amount of Reorganization monitor element
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_max_phase - Maximum Reorganize Phase monitor element
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_phase - Table reorganization phase monitor element
Indicates the reorganization phase of the table. For partitioned tables, this will also indicate the reorganization phase for each data partition. This applies to offline table reorganizations only.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
Usage
- Sort: SQLM_REORG_SORT
- Build: SQLM_REORG_BUILD
- Replace: SQLM_REORG_REPLACE
- Index Recreate: SQLM_REORG_INDEX_RECREATE
- Dictionary Build: SQLM_REORG_DICT_SAMPLE
For partitioned tables, the Index Recreate phase for partitioned indexes (if any) might be directly entered after the replace phase for that data partition. The reorg_phase element will indicate the Index Recreate phase only after the successful completion of all prior phases on every data partition.
- XML Reorg: SQLM_REORG_XML_DATA
- XML Dictionary Build: SQLM_REORG_XML_DICT_SAMPLE
- Scan: SQLM_REORG_SCAN
- Drain: SQLM_REORG_DRAIN
- Release: SQLM_REORG_RELEASE
reorg_phase_start - Reorganize Phase Start Time monitor element
The start time of a phase of table reorganization or reclaim reorganization. For partitioned tables, this will also indicate the start time of a reorganization phase for each data partition. During the index re-create phase, data groups for all data partitions are updated at the same time for nonpartitioned indexes.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_rows_compressed - Rows Compressed monitor element
Number of rows compressed in the table during reorganization.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
- Usage
- A running count of the number of rows
compressed in the table during
reorganization. Some records may never be compressed (if the record
size
is less than the minimum record length).
It is important to note that this row count does not measure the effectiveness of data compression. It only displays the number of records meeting compression criteria.
reorg_rows_rejected_for_compression - Rows Rejected for Compression monitor element
Number of rows that were not compressed during reorganization due to the record length being less than or equal to the minimum record length.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
- Usage
- A record will not be compressed if it is less than or equal to the minimum record length. The number of rows rejected reflects a running count for these records that fail to meet this compression requirement.
reorg_start - Table Reorganize Start Time monitor element
The start time of a table reorganization including a reorganization to reclaim extents from a multidimensional clustering (MDC) or insert time clustering (ITC) table. For partitioned tables, this indicates the start time for each data partition reorganization.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_status - Table Reorganize Status monitor element
The status of an in-place (online) table or a data partition level reorganization. This is not applicable to classic (offline) table reorganizations.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
- Usage
- An in-place table or data partition reorganization
can be in
one of the following states (states are listed with their corresponding
defines from sqlmon.h):
- Started/Resumed: SQLM_REORG_STARTED
- Paused: SQLM_REORG_PAUSED
- Stopped: SQLM_REORG_STOPPED
- Completed: SQLM_REORG_COMPLETED
- Truncate: SQLM_REORG_TRUNCATE
reorg_tbspc_id - Table Space Where Table or Data partition is Reorganized monitor element
The table space in which the table will be reorganized. For partitioned tables, this indicates the table space where each data partition is reorganized.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_type - Table Reorganize Attributes monitor element
Table reorganize attribute settings.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
- Usage
- The following are possible attribute settings.
Each attribute
setting is based upon a bit flag value defined in db2ApiDf.h.
- Allow Write Access: DB2REORG_ALLOW_WRITE
- Allow Read Access: DB2REORG_ALLOW_READ
- Allow No Access: DB2REORG_ALLOW_NONE
- Recluster Via Index Scan: DB2REORG_INDEXSCAN
- Reorg Long Field LOB Data: DB2REORG_LONGLOB
- No Table Truncation: DB2REORG_NOTRUNCATE_ONLINE
- Replace Compression Dictionary: DB2REORG_RESET_DICTIONARY
- Keep Compression Dictionary: DB2REORG_KEEP_DICTIONARY
- Reclaim Extents: DB2REORG_RECLAIM_EXTS
In addition to the preceding attribute settings, the following attributes are listed in the CLP output of the GET SNAPSHOT FOR TABLES command. These attribute settings are based on the values of other attribute settings or table reorganize monitor elements.- Reclustering: If the value of the reorg_index_id monitor element is non-zero, then the table reorganize operation has this attribute.
- Reclaiming: If the value of the reorg_index_id monitor element is zero, then the table reorganize operation has this attribute.
- Inplace Table Reorg: If the reorg_status monitor element has a value that is not null, then the in-place (online) reorganization method is in use.
- Table Reorg: If the reorg_phase monitor element has a value that is not null, then the classic (offline) reorganization method is in use.
- Recluster Via Table Scan: If the DB2REORG_INDEXSCAN flag is not set, then the table reorganize operation has this attribute.
- Reorg Data Only: If the DB2REORG_LONGLOB flag is not set, then the table reorganize operation has this attribute.
reorg_xml_regions_compressed - XML regions compressed monitor element
Number of XML regions that were compressed during the table reorganization process.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
reorg_xml_regions_rejected_for_compression - XML regions rejected for compression monitor element
Number of XML regions that were not compressed during the table reorganization process.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table_reorg | Basic |
replay_type - HADR replication type monitor element
Table function | Monitor element collection level |
---|---|
MON_GET_HADR table function - Returns high availability disaster recovery (HADR) monitoring information | Always collected |
Usage
- PHYSICAL
req_agent_tid - Thread identifier for agent waiting to acquire lock monitor element
Thread identifier of the agent or system entity that is waiting to acquire the lock.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_APPL_LOCKWAIT table function - get information about locks for which an application is waiting | Always collected |
req_application_handle - Identifier for application waiting to acquire lock monitor element
System-wide unique ID for the application that is waiting to acquire the lock.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_APPL_LOCKWAIT table function - get information about locks for which an application is waiting | Always collected |
req_executable_id - Identifier for statement section waiting to acquire lock monitor element
The binary token generated on the data server that uniquely identifies the SQL statement section which is waiting to acquire a lock. For non-SQL activities, a 0-length string value is returned.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_APPL_LOCKWAIT table function - get information about locks for which an application is waiting | Always collected |
req_member - Member of application waiting to acquire lock monitor element
Database member where the application waiting to acquire this lock is located.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_APPL_LOCKWAIT table function - get information about locks for which an application is waiting | Always collected |
request_exec_time_avg - Request execution time average monitor element
Arithmetic mean of the execution times for requests associated with this service subclass since the last reset. If the internally tracked average has overflowed, the value -2 is returned. This monitor element returns -1 when COLLECT AGGREGATE REQUEST DATA for the service subclass is set to NONE. Units are milliseconds.
When you remap activities between service subclasses with a REMAP ACTIVITY action, the request_exec_time_avg mean counts the partial request in each subclass involved in remapping.
Table Function | Monitor Element Collection Level |
---|---|
WLM_GET_SERVICE_SUBCLASS_STATS table function - Return statistics of service subclasses | COLLECT AGGREGATE REQUEST DATA |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Statistics | event_scstats | - |
Usage
Use this statistic to quickly understand the average amount of time that is spent processing each request on a member in this service subclass.
This average can also be used to determine whether or not the histogram template used for the request execution time histogram is appropriate. Compute the average request execution time from the request execution time histogram. Compare the computed average with this monitor element. If the computed average deviates from the true average reported by this monitor element, consider altering the histogram template for the request execution time histogram, using a set of bin values that are more appropriate for your data.
rf_log_num - Log being rolled forward monitor element
The log being processed in the rollforward operation.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | rollforward | Basic |
Usage
If a rollforward is in progress, this element identifies the log involved. In a DB2 pureScale environment, the rf_log_num monitor element identifies the log file from each log stream that is currently involved in the rollforward operation.
rf_status - Log Phase monitor element
The status of the recovery.
- Element identifier
- rf_status
- Element type
- information
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | rollforward | Basic |
- Usage
- This element indicates the progression of a recovery. It indicates if the recovery is in an undo (rollback) or redo (rollforward) phase.
rf_timestamp - Rollforward Timestamp monitor element
The timestamp of the last committed transaction..
- Element identifier
- rf_timestamp
- Element type
- timestamp
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | rollforward | Timestamp |
- Usage
- If a rollforward is in progress, this is the timestamp of the last committed transaction processed by rollforward recovery. This is an indicator of how far the rollforward operation has progressed.
rf_type - Rollforward Type monitor element
The type of rollforward in progress.
- Element identifier
- rf_type
- Element type
- information
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table Space | rollforward | Basic |
- Usage
- An indicator of whether recovery is happening at a database or table space level.
rollback_sql_stmts - Rollback Statements Attempted monitor element
The total number of SQL ROLLBACK statements that have been attempted.
- Element identifier
- rollback_sql_stmts
- Element type
- counter
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Basic |
Database | dbase_remote | Basic |
Application | appl | Basic |
Application | appl_remote | Basic |
DCS Database | dcs_dbase | Basic |
DCS Application | dcs_appl | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Connection | event_conn | Always collected |
- Usage
- A rollback can result from an application request, a deadlock,
or an error situation. This element only counts the number
of rollback statements issued from applications.
At the application level, this element can help you determine the level of database activity for the application and the amount of conflict with other applications. At the database level, it can help you determine the amount of activity in the database and the amount of conflict between applications on the database.
Note: You should try to minimize the number of rollbacks, since higher rollback activity results in lower throughput for the database.It may also be used to calculate the total number of units of work, by calculating the sum of the following expression:commit_sql_stmts + int_commits + rollback_sql_stmts + int_rollbacks
rolled_back_agent_id - Rolled Back Agent monitor element
Agent that was rolled back when a deadlock occurred.
- Element identifier
- rolled_back_agent_id
- Element type
- information
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Deadlocks | event_deadlock | Always collected |
- Usage
- A system administrator can use this information to determine which application did not complete its updates, and determine which applications should be restarted.
rolled_back_appl_id - Rolled Back Application monitor element
Application id that was rolled back when a deadlock occurred.
- Element identifier
- rolled_back_appl_id
- Element type
- information
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Deadlocks | event_deadlock | Always collected |
- Usage
- A system administrator can use this information to determine which application did not complete its updates, and determine which applications should be restarted.
rolled_back_participant_no - Rolled back application participant monitor element
The participant number identifying the rolled back application.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Locking | - | Always collected |
Deadlocks1 | event_deadlock | Always collected |
- 1
- This event monitor 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
A system administrator can use this information to determine which application did not complete its updates, and determine which application should be started.
rolled_back_sequence_no - Rolled Back Sequence Number monitor element
The sequence number of the application that was rolled back when a deadlock occurred.
- Element identifier
- rolled_back_sequence_no
- Element type
- information
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Deadlocks | event_deadlock | Always collected |
- Usage
- A system administrator can use this information to determine which application did not complete its updates, and determine which applications should be restarted.
root_node_splits - Root node splits monitor element
Number of times the root node of the index was split during an insert operation.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_INDEX table function - Get index metrics | Always collected |
routine_id - Routine ID monitor element
A unique routine identifier.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in the DETAILS XML document) | Always collected |
MON_GET_PKG_CACHE_STMT | Always collected |
MON_GET_PKG_CACHE_STMT_DETAILS - Get detailed metrics for package cache entries | Always collected |
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 |
MON_GET_ROUTINE_EXEC_LIST table function - get list of statements executed by routine | Always collected |
MON_GET_SECTION_ROUTINE table function - get list of routines for input section | 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 |
---|---|---|
Activities | event_activitystmt | Always collected |
Unit of work | uow_package_list | Always collected |
Package cache | pkgcache_metrics | Always collected |
Usage
The value of this element matches a value from column ROUTINEID of view SYSCAT.ROUTINES. The value of this element depends on the table function or logical data group that is reporting it.
routine_id
identifies the routine that executed
the activity. For example, if the procedure P1 executes an INSERT
statement, then the routine_id
returned for the INSERT
statement identifies the P1 routine.- MON_GET_ACTIVITY_DETAILS
- WLM_GET_SERVICE_CLASS_AGENTS
- WLM_GET_WORKLOAD_OCCURRENCE_ACTIVITIES
- event_activitystmt
routine_id
identifies the routine invoked by
a CALL statement. - MON_GET_PKG_CACHE_STMT
- MON_GET_PKG_CACHE_STMT_DETAIL
- pkgcache_metrics
routine_id
is only returned for CALL statements.
For all other statements, 0 is returned.routine_id
identifies
the routine associated with the returned information.- MON_GET_ROUTINE
- MON_GET_ROUTINE_DETAILS
- MON_GET_ROUTINE_EXEC_LIST
- MON_GET_SECTION_ROUTINE
routine_id
identifies the routine that executed
statements in a package.- uow_package_list
routine_module_name - Routine module name monitor element
Unqualified name of the module to which the routine belongs.
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 |
MON_GET_ROUTINE_EXEC_LIST table function - get list of statements executed by routine | Always collected |
MON_GET_SECTION_ROUTINE table function - get list of routines for input section | Always collected |
routine_name - Routine name monitor element
Unqualified name of the routine.
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 |
MON_GET_ROUTINE_EXEC_LIST table function - get list of statements executed by routine | Always collected |
MON_GET_SECTION_ROUTINE table function - get list of routines for input section | Always collected |
routine_schema - Routine schema monitor element
Schema name of the routine when the routine does not belong to a module, otherwise this is the schema name of the module to which the routine belongs.
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 |
MON_GET_ROUTINE_EXEC_LIST table function - get list of statements executed by routine | Always collected |
MON_GET_SECTION_ROUTINE table function - get list of routines for input section | Always collected |
routine_type - Routine type monitor element
Identifies the type of routine.
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 |
MON_GET_ROUTINE_EXEC_LIST table function - get list of statements executed by routine | Always collected |
MON_GET_SECTION_ROUTINE table function - get list of routines for input section | Always collected |
Usage
- C
- Dynamically prepared compound SQL statement or PL/SQL anonymous block
- F
- Function
- P
- Procedure
- T
- Trigger
rows_deleted - Rows deleted monitor element
This is the number of row deletions attempted.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_TABLE table function - Get table metrics | Always collected |
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list | DATA OBJECT METRICS BASE |
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Basic |
Database | dbase_remote | Basic |
Application | appl | Basic |
Application | appl_remote | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Connection | event_conn | Always collected |
- Usage
- You can use this element to gain insight into the current level
of activity within the database.
This count does not include the attempts counted in the int_rows_deleted monitor element.
rows_fetched - Rows fetched monitor element
The number of rows read from the table.
This monitor element is an alias of the rows_read monitor element.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activities | event_activity | Statement |
Usage
See the rows_read monitor element for details.
rows_inserted - Rows inserted monitor element
The number of row insertions attempted.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_TABLE table function - Get table metrics | Always collected |
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list | DATA OBJECT METRICS BASE |
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Basic |
Database | dbase_remote | Basic |
Application | appl | Basic |
Application | appl_remote | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Connection | event_conn | Always collected |
- Usage
- You can use this element to gain insight into the current level
of activity within the database.
In a federated system, multiple rows can be inserted, per INSERT statement, because the federated server can push INSERT FROM SUBSELECT to the data source, when appropriate.
This count does not include the attempts counted in the int_rows_inserted monitor element.
rows_modified - Rows modified monitor element
The number of rows inserted, updated, or deleted.
This monitor element is an alias of the rows_written monitor element.
This monitor element includes activity for rows in permanent tables and temporary tables. It is possible in certain circumstances for its value to be greater than the sum of the monitor elements rows_inserted, rows_updated, and rows_deleted.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activities | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
Activities | event_activitymetrics | ACTIVITY METRICS BASE |
Statistics | event_scstats (reported in the metrics document) | REQUEST METRICS BASE |
Statistics | event_wlstats (reported in the metrics document) | REQUEST METRICS BASE |
Unit of work | Reported in the system_metrics document. | REQUEST METRICS BASE |
Activities | event_activity | Statement |
Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
Usage
See the rows_written monitor element for details.
rows_read - Rows read monitor element
The number of rows read from the table.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Basic |
Table | table | Table |
Application | appl | Basic |
Application | stmt | Basic |
Application | subsection | Statement |
Dynamic SQL | dynsql | Statement |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activities | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
Activities | event_activitymetrics | ACTIVITY METRICS BASE |
Statistics | event_scstats (reported in the metrics document) | REQUEST METRICS BASE |
Statistics | event_wlstats (reported in the metrics document) | REQUEST METRICS BASE |
Unit of work | Reported in the system_metrics document. | REQUEST METRICS BASE |
Connection | event_conn | Always collected |
Tables | event_table | Always collected |
Statements | event_stmt | Always collected |
Transactions | event_xact | Always collected |
Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
Usage
This element helps you identify tables with heavy usage for which you may want to create additional indexes. To avoid the maintenance of unnecessary indexes, use the SQL EXPLAIN statement to determine if the package uses an index.
SELECT AVG(SALARY) FROM USERID.EMPLOYEE
This count includes the value in the overflow_accesses monitor element. Additionally, this count does not include any index accesses. That is, if an access plan uses index access only and the table is not touched to look at the actual row, then the value of the rows_read monitor element is not incremented.
rows_returned - Rows returned monitor element
This monitor element is an alias of the fetch_count monitor element.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Activities | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
Activities | event_activitymetrics | ACTIVITY METRICS BASE |
Statistics | event_scstats (reported in the metrics document) | REQUEST METRICS BASE |
Statistics | event_wlstats (reported in the metrics document) | REQUEST METRICS BASE |
Unit of work | Reported in the system_metrics document. | REQUEST METRICS BASE |
Activities | event_activity | Always collected |
Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
Usage
This element can be used to help determine thresholds for rows returned to the application or can be used to verify that such a threshold is configured correctly and doing its job.
rows_returned_top - Actual rows returned top monitor element
For service classes, when you remap activities between service subclasses with a REMAP ACTIVITY action, only the rows_returned_top high watermark of the service subclass where an activity completes is updated. High watermarks of service subclasses an activity is mapped to but does not complete in are unaffected.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Statistics | event_scstats | - |
Statistics | event_wcstats | - |
Statistics | event_wlstats | - |
Usage
Use this element to know the highest DML activity actual rows returned reached on a member for a service class, workload, or work class in the time interval collected.
rows_selected - Rows Selected monitor element
This is the number of rows that have been selected and returned to the application.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Basic |
Database | dbase_remote | Basic |
Application | appl | Basic |
Application | appl_remote | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Connection | event_conn | Always collected |
- Usage
- You can use this element to gain insight into the current level
of activity within the database.
This element does not include a count of rows read for actions such as COUNT(*) or joins.
For a federated system;, you can compute the average time to return a row to the federated server from the data source:
You can use these results to modify CPU speed or communication speed parameters in SYSCAT.SERVERS. Modifying these parameters can impact whether the optimizer does or does not send requests to the data source.average time = rows returned / aggregate query response time
Note: This element is collected at the dcs_dbase and dcs_appl snapshot monitor logical data groups if the gateway being monitored is at DB2 database version 7.2 or lower.
rows_updated - Rows updated monitor element
This is the number of row updates attempted.
Table Function | Monitor Element Collection Level |
---|---|
MON_GET_TABLE table function - Get table metrics | Always collected |
MON_GET_TABLE_USAGE_LIST table function - Returns information from a table usage list | DATA OBJECT METRICS BASE |
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | dbase | Basic |
Database | dbase_remote | Basic |
Application | appl | Basic |
Application | appl_remote | Basic |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Database | event_db | Always collected |
Connection | event_conn | Always collected |
- Usage
- You can use this element to gain insight into the current level
of activity within the database.
This value does not include updates counted in the int_rows_updated monitor element. However, rows that are updated by more than one update statement are counted for each update.
rows_written - Rows Written monitor element
This is the number of rows changed (inserted, deleted or updated) in the table.
Snapshot Level | Logical Data Grouping | Monitor Switch |
---|---|---|
Table | table | Basic |
Application | appl | Basic |
Application | stmt | Basic |
Application | subsection | Statement |
Dynamic SQL | dynsql | Statement |
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Connection | event_conn | Always collected |
Tables | event_table | Always collected |
Statements | event_stmt | Always collected |
Transactions | event_xact | Always collected |
- Usage
- A high value for table-level information indicates there is heavy usage of the table and you may
want to use the Run Statistics (RUNSTATS) utility to maintain efficiency of the packages used for
this table.
For application-connections, statements, and dynsql logical data groupings, this element includes the number of rows inserted, updated, and deleted in temporary tables. It is possible in certain circumstances for its value to be greater than the sum of the monitor elements rows_inserted, rows_updated, and rows_deleted.
At the application, transaction, and statement levels, this element can be useful for analyzing the relative activity levels, and for identifying candidates for tuning.
rqsts_completed_total - Total requests completed monitor element
The total number of requests executed, including both application and internal requests. For service subclasses, this monitor element is only updated where the request completes. If the request moved between different service subclasses, it is not counted twice.
Event Type | Logical Data Grouping | Monitor Switch |
---|---|---|
Statistics | event_scstats (reported in the metrics document) | REQUEST METRICS BASE |
Statistics | event_wlstats (reported in the metrics document) | REQUEST METRICS BASE |
Unit of work | Reported in the system_metrics document. | REQUEST METRICS BASE |