Database monitoring measures

This page lists available measures for database monitoring.

  • Session count - all databases: Overall number of sessions for all databases.
  • Sessions connected to the monitored database: Number of sessions for monitored databases.
  • Sessions connected to non-monitored databases: Number of sessions for non-monitored databases.
  • Activities - Completed: Average number of successfully completed activities per second. Use this element to determine the throughput of activities in the system. Refer to the DB2 documentation for the following monitor elements:
  • Activities - Rejected: Average number of rejected activities per second. Use this element to determine whether predictive thresholds and work actions that prevent execution are effective, and whether they are too restrictive. Refer to the DB2 documentation for the following monitor elements:
  • Activities - Aborted: Average number of cancelled activities per second, or activities completed with errors. Activities may be cancelled due to cancellation, errors, or reactive thresholds. Refer to the DB2 documentation for the following monitor elements:
  • SQL processing time: Average number of seconds spent on processing SQL per second, including time spent to perform section execution. Refer to the DB2 documentation for the following monitor elements:
  • Commit and rollback processing time: Average time spent on commits and rollbacks per second, including time spent to commit processing and rollback operations on the database server. Refer to the DB2 documentation for the following monitor elements:
  • Administration tasks processing time: Average time spent on administration tasks per second, including time spent to perform run stats, reorg, load processing, online backups, and index builds on database server. Refer to the DB2 documentation for the following monitor elements:
  • User routines processing time, Average number time spent on executing routines outside of known DB2 per second. Refer to the DB2 documentation for the following monitor elements:
  • Compilation time: Average time spent on compilation per second, including time spent performing explicit and implicit compiles on the database server. Refer to the DB2 documentation for the following monitor elements:
    • TOTAL_COMPILE_PROC_TIME
    • TOTAL_IMPLICIT_COMPILE_PROC_TIME
      Explicit compiles are compilations directly initiated by a user request such as a bind, rebind, prepare or execute immediate. Implicit compiles are compilations not directly requested by the user. For example, an implicit compilation may occur when executing a statement that was bound using the VALIDATE RUN option if the statement needs to be compiled at execution time.
  • Connection management time: Average time spent on connection management per second, including time spent processing a connection or switch user request. Refer to the DB2 documentation for the following monitor elements:
  • CPU time: Average amount of CPU time used within DB2 per second. It includes both user and system CPU time. Refer to the DB2 documentation for the following monitor elements:
  • Read time: Average time per second spent to:
    • Read in data and index pages from the table space containers (physical) for all types of table spaces.
    • Perform the direct reads.
    • Read data and index pages from the table space containers (physical) by asynchronous engine dispatchable units (EDUs) for all types of table spaces. Refer to the DB2 documentation for the following monitor elements:
  • Write time: Average time per second spent to:
  • Total wait time: Average time spent to waiting within DB2 per second. Refer to the DB2 documentation for the following monitor elements: