DB2 Version 10.1 for Linux, UNIX, and WindowsI
id - cluster caching facility identification monitor element
cluster caching facility identifier, as defined in the db2nodes.cfg file.
| Table Function | Monitor Element Collection Level |
|---|---|
| DB2_MEMBER and DB2_CF administrative views and DB2_GET_INSTANCE_INFO table function | Always collected |
| MON_GET_CF table function - Get CF metrics | Always collected |
| MON_GET_CF_CMD table function - Get cluster caching facility command processing time | Always collected |
| MON_GET_CF_WAIT_TIME table function - Get cluster caching facility command wait time | Always collected |
ida_recv_volume - Total data volume received monitor element
The total volume of data (in bytes) that the database server received from an in-database analytics process.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activity | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
| Activity | event_activitymetrics | ACTIVITY METRICS BASE |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Package cache | event_pkgcache_metrics | 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 |
| Unit of work | event_uow_metrics | REQUEST METRICS BASE |
ida_recv_wait_time - Time spent waiting to receive data monitor element
The total amount of time spent waiting to receive data from an in-database analytics process.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activity | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
| Activity | event_activitymetrics | ACTIVITY METRICS BASE |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Package cache | event_pkgcache_metrics | 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 |
| Unit of work | event_uow_metrics | REQUEST METRICS BASE |
ida_recvs_total - Number of times data received monitor element
The total number of times data was received from an in-database analytics process.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activity | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
| Activity | event_activitymetrics | ACTIVITY METRICS BASE |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Package cache | event_pkgcache_metrics | 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 |
| Unit of work | event_uow_metrics | REQUEST METRICS BASE |
ida_send_volume - Total data volume sent monitor element
The total volume of data (in bytes) sent from the database server to an in-database analytics process.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activity | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
| Activity | event_activitymetrics | ACTIVITY METRICS BASE |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Package cache | event_pkgcache_metrics | 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 |
| Unit of work | event_uow_metrics | REQUEST METRICS BASE |
ida_send_wait_time - Time spent waiting to send data monitor element
The total amount of time spent waiting to send data to an in-database analytics process.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activity | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
| Activity | event_activitymetrics | ACTIVITY METRICS BASE |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Package cache | event_pkgcache_metrics | 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 |
| Unit of work | event_uow_metrics | REQUEST METRICS BASE |
ida_sends_total - Number of times data sent monitor element
The total number of times data was sent to an in-database analytics process.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activity | event_activity (reported in the details_xml document) | ACTIVITY METRICS BASE |
| Activity | event_activitymetrics | ACTIVITY METRICS BASE |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Package cache | event_pkgcache_metrics | 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 |
| Unit of work | event_uow_metrics | REQUEST METRICS BASE |
inact_stmthist_sz - Statement history list size monitor element
When a detailed deadlock event monitor with history is running, this element reports the number of bytes being used from the database monitor heap (MON_HEAP_SZ) to keep track of the statement history list entries.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| application | appl | - |
| database | db | - |
- Usage
- You can use this element when tuning the database monitor heap.
idle_agents - Number of Idle Agents monitor element
The number of agents in the agent pool that
are currently unassigned
to an application and are, therefore, idle
.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database Manager | db2 | Basic |
- Usage
- You can use this element to help set the num_poolagents configuration parameter. Having idle agents available to service requests for agents can improve performance.
iid - Index identifier monitor element
Identifier for the index.
| Table Function | Monitor Element Collection Level |
|---|---|
| ADMIN_GET_INDEX_COMPRESS_INFO table function - returns compressed index information | Always collected |
| ADMIN_GET_INDEX_INFO table function - returns index information | Always collected |
| MON_GET_INDEX table function - Get index metrics | Always collected |
| MON_GET_PAGE_ACCESS_INFO table function - Get buffer pool page waiting information | Always collected |
inbound_bytes_received - Inbound Number of Bytes Received monitor element
The number of bytes received by the DB2 Connect gateway from the client, excluding communication protocol usage (for example, TCP/IP).
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| DCS Application | dcs_appl | Basic |
| DCS Statement | dcs_stmt | Statement |
- Usage
- Use this element to measure the throughput from the client to the DB2 Connect gateway.
inbound_bytes_sent - Inbound Number of Bytes Sent monitor element
The number of bytes sent by the DB2 Connect gateway to the client, excluding communication protocol usage (for example, TCP/IP).
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| DCS Application | dcs_appl | Basic |
| DCS Statement | dcs_stmt | Statement |
- Usage
- Use this element to measure the throughput from the DB2 Connect gateway to the client.
inbound_comm_address - Inbound Communication Address monitor element
This is the communication address of the client. For example, it could be an IP address and port number for TCP/IP.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Application | appl_info | Basic |
| DCS Application | dcs_appl_info | Basic |
- Usage
- Use this element for problem determination on DCS applications.
include_col_updates - Include column updates monitor element
Number of include column updates.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_INDEX table function - Get index metrics | Always collected |
incremental_bind - Incremental bind monitor element
Indicates whether the package was incrementally bound at execution time. Possible values are YES or NO.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Locking | lock_participant_activities |
index_jump_scans - Index jump scans monitor element
Number of jump scans. A jump scan is an index scan where there is a gap in the index start and stop keys and sections of the index that will not yield results are skipped.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_INDEX table function - Get index metrics | Always collected |
Usage
You can use this monitor element to validate that jump scans are happening at an expected rate. If the value for this monitor element is not increasing as expected, check the following conditions:- For queries being issued where you expect a jump scan, verify that the target table has an appropriate composite index and that the query predicates introduce an index gap. The DB2® optimizer will not create plans with jump scans if there are no index gaps.
- Jump scans do not scan the following types of indexes:
- range-clustered table indexes
- extended indexes (for example, spatial indexes)
- XML indexes
- text indexes (for Text Search)
index_name - Index name monitor element
The name of an index.
| Table Function | Monitor Element Collection Level |
|---|---|
| ADMIN_GET_INDEX_COMPRESS_INFO table function - returns compressed index information | Always collected |
| ADMIN_GET_INDEX_INFO table function - returns index information | Always collected |
| MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list | Always collected |
index_schema - Index schema monitor element
The name of an index schema.
| Table Function | Monitor Element Collection Level |
|---|---|
| ADMIN_GET_INDEX_COMPRESS_INFO table function - returns compressed index information | Always collected |
| ADMIN_GET_INDEX_INFO table function - returns index information | Always collected |
| MON_GET_INDEX_USAGE_LIST table function - Returns information from an index usage list | Always collected |
index_object_pages - Index Object Pages monitor element
The number of disk pages consumed by all indexes defined on a table.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Table | table | Basic |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Tables | event_table | Always collected |
- Usage
- This element provides a mechanism for viewing the actual amount of space consumed by indexes defined on a particular table. This element can be used in conjunction with a table event monitor to track the rate of index growth over time. This element is not returned for partitioned tables.
index_object_l_pages - Index data logical pages monitor element
The number of logical pages used on disk by all indexes associated with this table. For partitioned tables, the value returned is NULL.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_TABLE table function - Get table metrics | Always collected |
Usage
- This value might
be less than the amount of space physically allocated for the object.
This can happen when you use the REUSE STORAGE option of the TRUNCATE
statement. This option causes storage allocated for the table to continue
to be allocated, although the storage will be considered empty. In
addition, the value for this monitor element might be less than the
amount of space logically allocated for the object, because the total
space logically allocated includes a small amount of additional meta
data.
To retrieve an accurate measure of the logical or physical size of an object, use the ADMIN_GET_TAB_INFO_V97 function. This function provides more accurate information about the size of objects than you can obtain by multiplying the number of pages reported for this monitor element by the page size.
index_only_scans - Index-only scans monitor element
Number of index-only scans. Index-only scans occur when the results of scan was satisfied by access to the index only.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_INDEX table function - Get index metrics | Always collected |
index_scans - Index scans monitor element
Number of index scans.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_INDEX table function - Get index metrics | Always collected |
index_tbsp_id - Index table space ID monitor element
An identifier of the table space that holds indexes created on this table.
| Table Function | Monitor Element Collection Command and Level |
|---|---|
| MON_GET_TABLE table function - Get table metrics | Always collected |
Usage
The value of this element matches a value from column TBSPACEID of view SYSCAT.TABLESPACES.
input_db_alias - Input Database Alias monitor element
The alias of the database provided when calling the snapshot function.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl_id_info | Basic |
| Table Space | tablespace_list | Buffer Pool |
| Buffer Pool | bufferpool | Buffer Pool |
| Table | table_list | Table |
| Lock | db_lock_list | Basic |
- Usage
- This element can be used to identify
the specific database to which
the monitor data applies. It contains blanks unless you requested
monitor
information related to a specific database.
The value of this field may be different than the value of the client_db_alias monitor element since a database can have many different aliases. Different applications and users can use different aliases to connect to the same database.
insert_sql_stmts - Inserts monitor element
This element contains a count of the total number of times the federated server has issued an INSERT statement to 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 the level of database activity directed against this data source by the federated server or an application.
write_activity =
(INSERT statements + UPDATE statements + DELETE statements ) /
(SELECT statements + INSERT statements + UPDATE statements +
DELETE statements)insert_time - Insert Response Time monitor element
The response time is measured as the difference in time between the time the federated server submits an INSERT statement to the data source, and the time the data source responds to the federated server, indicating that the INSERT has been processed.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase_remote | Timestamp |
| Application | appl_remote | Timestamp |
Usage
Use this element to determine the actual amount of time that transpires waiting for INSERTs to this data source to be processed. This information can be useful for capacity planning and tuning.
insert_timestamp - Insert timestamp monitor element
| Table Function | Monitor Element Collection Level |
|---|---|
| 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 |
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Dynamic SQL | dynsql | Basic |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Package cache | - | COLLECT BASE DATA |
Usage
This element specifies the time when the statement was inserted into the cache. It can be used to estimate the lifetime of a statement in the cache.
int_auto_rebinds - Internal Automatic Rebinds monitor element
The number of automatic rebinds (or recompiles) that have been attempted.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | event_db | Always collected |
| Connection | event_conn | Always collected |
- Usage
- Automatic rebinds are the internal binds
the system performs when an
package has been invalidated. The rebind is performed the first time
that
the database
manager needs
to execute
an SQL statement from the package. For example, packages are invalidated
when
you:
- Drop an object, such as a table, view, or index, on which the plan is dependent
- Add or drop a foreign key
- Revoke object privileges on which the plan is dependent.
You can use this element to determine the level of database activity at the application or database level. Since int_auto_rebinds can have a significant impact on performance, they should be minimized where possible.
You can also use this element to determine the percentage of rebind activity using the following formula:int_auto_rebinds / total number of statementsThis information can be useful for analyzing application activity and throughput.
int_commits - Internal commits monitor element
The total number of commits initiated internally by the database manager.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | event_db | Always collected |
| Connection | event_conn | Always collected |
| 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 |
Usage
- A reorganization
- An import
- A bind or pre-compile
- An application ends without executing an explicit SQL COMMIT statement (on UNIX).
- The connection to the database (for database-level information, this is the time of the first connection)
- The last reset of the database monitor counters.
commit_sql_stmts
+ int_commits
+ rollback_sql_stmts
+ int_rollbacks- The connection to the database (for database-level information, this is the time of the first connection)
- The last reset of the database monitor counters.
This calculation can be done at the application or the database level.
int_deadlock_rollbacks - Internal Rollbacks Due To Deadlock monitor element
The total number of forced rollbacks initiated by the database manager due to a deadlock. A rollback is performed on the current unit of work in an application selected by the database manager to resolve the deadlock.
- Element identifier
- int_deadlock_rollbacks
- Element type
- counter
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Connection | event_conn | Always collected |
- Usage
- This element shows the number of
deadlocks that have been broken and
can be used as an indicator of concurrency problems. It is important,
since
int_deadlock_rollbacks lower the throughput of the database.
This value is included in the value given by int_rollbacks.
int_node_splits - Intermediate node splits monitor element
Number of times an intermediate index node was split during an insert operation.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_INDEX table function - Get index metrics | Always collected |
int_rollbacks - Internal rollbacks monitor element
The total number of rollbacks initiated internally by the database manager.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | event_db | Always collected |
| Connection | event_conn | Always collected |
| 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 |
Usage
- A reorganization
- An import
- A bind or pre-compile
- An application ends as a result of a deadlock situation or lock timeout situation
- An application ends without executing an explicit commit or rollback statement (on Windows).
- The connection to the database (for database-level information, this is the time of the first connection)
- The last reset of the database monitor counters.
While this value does not include explicit SQL ROLLBACK statements, the count from the int_deadlock_rollbacks monitor element is included.
commit_sql_stmts
+ int_commits
+ rollback_sql_stmts
+ int_rollbacks- The connection to the database (for database-level information, this is the time of the first connection)
- The last reset of the database monitor counters.
This calculation can be done at the application or the database level.
int_rows_deleted - Internal Rows Deleted monitor element
This is the number of rows deleted from the database as a result of internal activity.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Application | stmt | Basic |
| Dynamic SQL | dynsql | Statement |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | event_db | Always collected |
| Connection | event_conn | Always collected |
| Statements | event_stmt | Always collected |
- Usage
- This element can help you gain insight into internal
activity within
the database
manager of
which you might
not be aware. If this activity is high, you may want to evaluate
your table
design to determine if the referential constraints or triggers that
you have
defined on your database are necessary. Internal delete activity can be a result of:
- A cascading delete enforcing an ON CASCADE DELETE referential constraint
- A trigger being fired.
int_rows_inserted - Internal Rows Inserted monitor element
The number of rows inserted into the database as a result of internal activity caused by triggers.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Application | stmt | Basic |
| Dynamic SQL | dynsql | Statement |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | event_db | Always collected |
| Connection | event_conn | Always collected |
| Statements | event_stmt | Always collected |
- Usage
- This element can help you gain insight into the internal activity within the database manager. If this activity is high, you may want to evaluate your design to determine if you can alter it to reduce this activity.
int_rows_updated - Internal Rows Updated monitor element
This is the number of rows updated from the database as a result of internal activity.
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | dbase | Basic |
| Application | appl | Basic |
| Application | stmt | Basic |
| Dynamic SQL | dynsql | Statement |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Database | event_db | Always collected |
| Connection | event_conn | Always collected |
| Statements | event_stmt | Always collected |
- Usage
- This element can help you gain insight into internal
activity within
the database
manager of
which you might
not be aware. If this activity is high, you may want to evaluate
your table
design to determine if the referential constraints that you have defined
on
your database are necessary. Internal update activity can be a result of:
- A set null row update enforcing a referential constraint defined with the ON DELETE SET NULL rule
- A trigger being fired.
intra_parallel_state - Current state of intrapartition parallelism monitor element
The current state of intrapartition parallelism reported at statement, activity, transaction, or workload level. Possible values are "YES" to indicate that intrapartition parallelism is enabled so a statement can run with subagents; and "NO" to indicate that intrapartition parallelism is disabled.
| 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_CONNECTION table function - Get connection metrics | Always collected |
| MON_GET_CONNECTION_DETAILS table function - Get detailed connection metrics (reported in DETAILS XML document) | Always collected |
| MON_GET_UNIT_OF_WORK table function - Get unit of work metrics | Always collected |
| MON_GET_UNIT_OF_WORK_DETAILS table function - Get detailed unit of work metrics | Always collected |
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Activities | - | Always collected |
| Locking | ||
| Unit of work |
invocation_id - Invocation ID monitor element
An identifier that distinguishes one invocation of a routine from others at the same nesting level within a unit of work. It is unique within a unit of work for a specific nesting level.
The invocation_id monitor element is an alias of the stmt_invocation_id monitor element.
| 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 |
|---|---|---|
| Activities | event_activitystmt | - |
| Locking | - | - |
| Deadlocks with Details History Values1 | event_stmt_history | - |
| Deadlocks with Details History1 | event_stmt_history | - |
| Unit of work | Reported in the package list. | - |
- 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
You can use this element to uniquely identify the invocation in which a particular SQL statement has been executed. You can also use this element in conjunction with other statement history entries to see the sequence of SQL statements that caused the deadlock.
ipc_recv_volume - Interprocess communication received volume monitor element
The amount of data received by data server from clients over IPC. This value is reported in bytes.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Statistics | event_scstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Statistics | event_wlstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Unit of work | Reported in the system_metrics document. | - |
ipc_recv_wait_time - Interprocess communication received wait time monitor element
The time spent by an agent receiving an incoming client request using the IPC communications protocol. The value is reported in milliseconds.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Statistics | event_scstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Statistics | event_wlstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Unit of work | Reported in the system_metrics document. | - |
ipc_recvs_total - Interprocess communication receives total monitor element
The number of times data was received by the database server from the client application using IPC.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Statistics | event_scstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Statistics | event_wlstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Unit of work | Reported in the system_metrics document. | - |
ipc_send_volume - Interprocess communication send volume monitor element
The amount of data sent by data server to clients over the IPC protocol. This value is reported in bytes.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Statistics | event_scstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Statistics | event_wlstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Unit of work | Reported in the system_metrics document. | - |
ipc_send_wait_time - Interprocess communication send wait time monitor element
The time spent blocking on an IPC send to the client. The value is given in milliseconds.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Statistics | event_scstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Statistics | event_wlstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Unit of work | Reported in the system_metrics document. | - |
ipc_sends_total - Interprocess communication send total monitor element
The number of times data was sent by the database server to client applications using IPC.
| Event Type | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Statistics | event_scstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Statistics | event_wlstats (reported in the details_xml document) | REQUEST METRICS BASE |
| Unit of work | Reported in the system_metrics document. | - |
is_system_appl - Is System Application monitor element
Indicates whether the application is a system application.
| Table function | Monitor element collection level |
|---|---|
| MON_GET_APPL_LOCKWAIT table function - Get information about locks for which an application is waiting | Always collected |
| MON_GET_CONNECTION table function - Get connection metrics | Always collected |
| MON_GET_CONNECTION_DETAILS table function - Get detailed connection metrics (reported in DETAILS XML document) | Always collected |
| MON_GET_UNIT_OF_WORK table function - Get unit of work metrics | Always collected |
| MON_GET_UNIT_OF_WORK_DETAILS table function - Get detailed unit of work metrics (reported in DETAILS XML document) | Always collected |
| Snapshot Level | Logical Data Grouping | Monitor Switch |
|---|---|---|
| Application | appl_info | Basic |
Usage
- 0
- user application
- 1
- system application