ACT_COMPLETED_TOTAL:The total number of activities that have been successfully completed.

ACT_REJECTED_TOTAL:The total number of activities that have been rejected.

ACTIVE_HASH_JOINS:The number of active hash joins currently being performed.

ACTIVE_OLAP_FUNCS:The number of active OLAP functions currently in use.

ACTIVE_SORTS: The number of sorts in the database that currently have a sort heap allocated.

AGENT_WAIT_TIME:The total amount of time that agents have spent waiting.

AGENT_WAITS_TOTAL:The total number of waits by agents.

AGENTS_TOP: The maximum number of agents for all applications is at the database level.

APP_RQSTS_COMPLETED_TOTAL:The total number of application requests that have been completed.

APPLS_CUR_CONS: The number of applications that are currently connected to the database.

APPLS_IN_DB2: The number of applications that are currently connected to the database, and for which the database manager is currently processing a request.

BINDS_PRECOMPILES: The number of binds and pre-compiles attempted. You can use this element to gain insight into the current level of activity within the database manager. This value does not include the count of int_auto_rebinds, but it does include binds that occur as a result of the REBIND PACKAGE command.

CLIENT_IDLE_WAIT_TIME:The total time the client has spent waiting while idle.

COMMIT_SQL_STMTS:The total number of SQL statements committed.

CONNECTIONS_TOP: The highest number of simultaneous connections to the database since the database was activated.

COORD_AGENTS_TOP: The highest number of coordinating agents. If the peak number of coordinating agents represents too high a workload for this node, you can reduce this upper boundary by changing the max_coordagents configuration parameter.

CT_ABORTED_TOTAL:The total number of activities that have been aborted.

DDL_SQL_STMTS: The number of SQL Data Definition Language (DDL) statements that were executed.

DEADLOCKS: The number of deadlocks that have occurred.

DIRECT_READ_REQS: Use the following formula to calculate the average number of sectors that are read by a direct read: direct_reads / direct_read_reqs.

DIRECT_READ_TIME: Time spent doing direct read operations.

DIRECT_READS: Direct reads are performed in units, the smallest being a 512-byte sector. They are used when: Reading LONG VARCHAR columns, Reading LOB (large object) columns, Performing a backup.

DIRECT_WRITE_REQS: Use the following formula to calculate the average number of sectors that are written by a direct write: direct_writes / direct_write_reqs.

DIRECT_WRITE_TIME: Time spent doing direct write operations.

DIRECT_WRITES: Direct writes are performed in units, the smallest being a 512-byte sector. They are used when: Writing LONG VARCHAR columns, Writing LOB (large object) columns, Performing a restore, Performing a load, Allocating new extents for SMS table space if MPFA is enabled (which is the default).

DYNAMIC_SQL_STMTS: The number of dynamic SQL statements that were attempted.

ELAPSED_EXEC_TIME_MS: The total time (in milliseconds) required to execute all the statements for a particular application during the specified time period.

ELAPSED_EXEC_TIME_S: The total time (in seconds) required to execute all the statements for a particular application during the specified time period.

FAILED_SQL_STMTS: The number of SQL statements that were attempted, but failed.

FIRST_ACTIVE_LOG:The identifier for the first active log.

IMPLICIT_REBINDS:The number of implicit rebinds that have occurred.

INT_AUTO_REBINDS: The number of commits initiated internally by the database manager.

INT_COMMITS: The number of commits initiated internally by the database manager.

INT_DEADLOCK_ROLLBACKS: The 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.

INT_ROLLBACKS: The number of rollbacks initiated internally by the database manager.

INT_ROWS_DELETED: The number of rows deleted from the database as a result of internal activity.

INT_ROWS_INSERTED: The number of rows inserted into the database as a result of internal activity caused by triggers.

INT_ROWS_UPDATED: The number of rows updated from the database as a result of internal activity.

LAST_ACTIVE_LOG:The identifier for the last active log.

LOCK_ESCALS: The number of times that locks have been escalated from several row locks to a table lock.

LOCK_LIST_IN_USE: The total number of bytes of lock list memory in use.

LOCK_TIMEOUTS: The number of times that a request to lock an object timed-out instead of being granted.

LOCK_WAIT_TIME: The total elapsed time (in milliseconds) spent waiting for locks.

LOCK_WAITS: The number of times that applications or connections waited for locks.

LOCKS_HELD: The number of locks currently held.

LOCKS_WAITING: The number of agents waiting on a lock.

LOG_DISK_WAIT_TIME:The total time spent waiting for disk I/O during logging.

LOG_DISK_WAITS_TOTAL:The total number of waits for disk I/O during logging.

LOG_HADR_WAIT_TIME:The total time spent waiting for HADR (High Availability Disaster Recovery) logging.

LOG_HADR_WAITS_TOTAL:The total number of waits related to HADR logging.

LOG_HELD_BY_DIRTY_PAGES: The amount of log (in bytes) corresponding to the difference between the oldest dirty page in the database and the top of the active log.

LOG_READ_TIME:The total time spent on reading log data.

LOG_READ_TIME_NS: The total elapsed time spent by the logger reading log data from the disk. For event monitors that write to tables, the value of this element is given in microseconds by using the BIGINT data type.

LOG_READ_TIME_S: At the database level, this is the number of subagents for all applications.

LOG_READS: The number of log pages read from disk by the logger.

LOG_TO_REDO_FOR_RECOVERY: The size of the log (in bytes) that will have to be redone for crash recovery.

LOG_WRITE_TIME:The total time spent on writing log data.

LOG_WRITE_TIME_NS: The total elapsed time spent by the logger writing log data to the disk. For event monitors that write to tables, the value of this element is given in microseconds by using the BIGINT data type.

LOG_WRITE_TIME_S: At the database level, this is the number of subagents for all applications.

LOG_WRITES: The number of log pages written to disk by the logger.

NUM_ASSOC_AGENTS: At the database level, this is the number of subagents for all applications.

NUM_INDOUBT_TRANS: The number of outstanding in-doubt transactions in the database. Indoubt transactions hold log space for uncommitted transactions, which can cause the logs to become full. When the logs are full, further transactions cannot be completed. The resolution of this problem involves a manual process of heuristically resolving the in-doubt transactions. This monitor element provides a count of the number of currently outstanding in doubt transactions that must be heuristically resolved.

NUM_LOCKS_HELD:The number of locks currently held.

NUM_LOCKS_WAITING:The number of locks that are currently waiting.

NUM_LOG_BUFFER_FULL: The number of times agents had to wait for log data to write to disk while copying log records into the log buffer.

NUM_LOG_DATA_FOUND_IN_BUFFER: The number of times log data was read from buffer instead of from disk, which is slower.

NUM_LOG_PART_PAGE_IO: Number of I/O requests issued by the logger for writing partial log data to disk. To determine if the current disk is adequate for logging, use this metric in conjunction with log_writes, log_write_time, and num_log_write_io.

NUM_LOG_READ_IO: Number of I/O requests issued by the logger to read log data from disk. To determine if the current disk is adequate for logging, use this metric in conjunction with log_reads and log_read_time.

NUM_LOG_WRITE_IO: Number of I/O requests issued by the logger to write log data to disk. To determine if the current disk is adequate for logging, use this metric in conjunction with log_writes and log_write_time.

POOL_ASYNC_DATA_READ_REQS: Number of asynchronous read requests by the prefetcher to the operating system. These requests are usually large block I/Os of multiple pages.

POOL_ASYNC_DATA_READS: Number of data pages read in from the table space physical containers by asynchronous engine dispatchable units for all types of table spaces. To determine the number of physical read that were performed synchronously, use this metric along with the pool_data_p_reads metrics.

POOL_ASYNC_DATA_WRITES: Number of times a buffer pool data page was physically written to disk by either an asynchronous page cleaner or prefetcher. To determine how well the buffer page cleaners are performing, use this metric in conjunction with pool_data_writes and pool_async_data_writes.

POOL_ASYNC_INDEX_READ_REQS:Number of asynchronous index read requests from the pool.

POOL_ASYNC_INDEX_READS: Number of index pages read in from the physical table space containers by asynchronous engine dispatchable units for all types of table spaces. To determine how well the prefetchers are working, company the ratio of asynchronous reads to total physical reads. Use this information to tune the num_ioservers configuration parameter.

POOL_ASYNC_INDEX_WRITES: Number of times a buffer pool index page was physically written to disk by either an asynchronous page cleaner or prefetcher.

POOL_ASYNC_READ_TIME: Total number of milliseconds spent reading in data and index pages from physical table space containers by asynchronous engine dispatchable units for all types of table spaces. Use this metric to analyze the I/O work being performed.

POOL_ASYNC_WRITE_TIME: Total number of milliseconds spent writing data or index pages from the buffer pool to disk by database manager page cleaners. Use this metric to analyze the I/O work being performed.

POOL_DATA_FROM_ESTORE: Number of buffer pool data pages read from the extended storage monitor.

POOL_DATA_L_READS: number of data pages which have been requested from the buffer pool (logical) for regular and large table spaces. The functionality to record buffer pool information at the statement level is supported for API and CLP snapshot requests.

POOL_DATA_P_READS: number of data pages read in from the table space containers (physical) for regular and large table spaces. The functionality to record buffer pool information at the statement 7 level is supported for API and CLP snapshot requests.

POOL_DATA_WRITES: number of times a buffer pool data page was physically written to disk.

POOL_DRTY_PG_STEAL_CLNS: Number of times a page cleaner was invoked because a synchronous write was needed during the victim buffer replacement for the database.

POOL_DRTY_PG_THRSH_CLNS: Number of times a page cleaner was invoked because a buffer pool had reached the dirty page threshold criterion for the database.

POOL_INDEX_L_READS: number of index pages which have been requested from the buffer pool (logical) for 9 regular and large table spaces. The functionality to record buffer pool information at the statement level is supported for API and CLP snapshot requests.

POOL_INDEX_P_READS: number of index pages read in from the table space containers (physical) for regular and large table spaces. The functionality to record buffer pool information at the statement level is supported for API and CLP snapshot requests.

POOL_INDEX_WRITES: number of times a buffer pool index page was physically written to disk.

POOL_LSN_GAP_CLNS: Number of times a page cleaner was invoked because the logging space used had reached a predefined criterion for the database.

POOL_NO_VICTIM_BUFFER: Number of times an agent did not have a preselected victim buffer available.

POOL_READ_TIME: Number of milliseconds spent reading in data and index pages from the physical table space for all types of table spaces.

POOL_TEMP_DATA_L_READS: Number of data pages which have been requested from the logical buffer pool for temporary table spaces.

POOL_TEMP_DATA_P_READS: Number of data pages read in from the physical table space containers for temporary table spaces.

POOL_TEMP_INDEX_L_READS: Number of index pages which were requested from the logical buffer pool for temporary table spaces.

POOL_TEMP_INDEX_P_READS: Number of index pages read in from the physical table space containers for temporary table spaces.

POOL_TEMP_XDA_P_READS:Number of temporary XDA physical reads from the pool.

POOL_WRITE_TIME: Number of milliseconds spent physically writing data or index pages from the buffer pool to disk.

POOL_XDA_L_READS:The buffer pool XDA data logical reads monitor element.

POOL_XDA_P_READS:Number of XDA physical reads from the pool.

POOL_XDA_WRITES:Number of XDA writes to the pool.

PREFETCH_WAIT_TIME: Number of milliseconds spent waiting for an I/O prefetcher server to finish loading pages into the buffer pool.

ROLLBACK_SQL_STMTS:The total number of SQL statements that have been rolled back.

ROWS_DELETED: number of row deletions attempted.

ROWS_INSERTED: number of row insertions attempted.

ROWS_MODIFIED:The total number of rows modified.

ROWS_READ: number of rows read from tables.

ROWS_SELECTED: number of rows that have been selected and returned to the application.

ROWS_UPDATED: number of row updates attempted.

RQSTS_COMPLETED_TOTAL:The total number of requests completed.

SEC_LOG_USED_TOP: The maximum number of bytes of secondary log space used.

SEC_LOGS_ALLOCATED: Number of secondary log files currently being used for the database.

SELECT_SQL_STMTS: The number of SQL SELECT statements that were executed.

SORT_HEAP_ALLOCATED: The number of allocated pages of sort heap space for all sorts at the level chosen and at the current time.

SORT_OVERFLOWS: The number of sorts that ran out of sort heap and may have required disk space for temporary storage.

SORT_SHRHEAP_ALLOCATED: The total amount of shared sort memory allocated in the database.

SORT_SHRHEAP_TOP: Database-wide shared sort memory high-water mark in 4k pages.

STATIC_SQL_STMTS: The number of static SQL statements that were attempted.

TOT_LOG_USED_TOP: The maximum number of bytes used for log space.

TOTAL_ACT_TIME:The total time of activity processing.

TOTAL_ACT_WAIT_TIME:The total time spent waiting during activity processing.

TOTAL_APP_COMMITS: Total number of commit statements issued by the client application.

TOTAL_APP_ROLLBACKS: Total number of rollback statements issued by the client application.

TOTAL_COMMIT_TIME:The total time spent on commit operations.

TOTAL_COMPILATIONS:The total number of compilations performed.

TOTAL_COMPILE_TIME:The total time spent on compilation.

TOTAL_CONS: number of newly opened connections to the database.

TOTAL_CPU_TIME:The total CPU time consumed.

TOTAL_LOG_AVAILABLE: Number of bytes of active log space in the database that is not being used by uncommitted transactions.

TOTAL_LOG_USED: Number of bytes of active log space currently used in the database.

TOTAL_SEC_CONS: The number of connections made by a subagent to the database at the node.

TOTAL_SORT_TIME: The total elapsed time (in milliseconds) for all sorts that have been executed.

TOTAL_LOCK_TIME: Total lock time is calculated based on the number of blocking sessions per second granularity. This does not consider the duration when a transaction is rolled back during a session-level or server-level lock timeout.

TOTAL_SORTS: The number of sorts that have been executed.

TOTAL_RQST_TIME:The total time spent on processing requests.

TOTAL_WAIT_TIME:The total time spent waiting across all operations.

TOT_LOG_USED_TOP: The maximum amount of total log space used (in bytes).

UID_SQL_STMTS: Number of SQL UPDATE, INSERT, and DELETE statements that were executed.

UNREAD_PREFETCH_PAGES: Number of pages that the prefetcher read in that were never used.