This parameter controls the collection of request metrics
on the entire database and affects requests executing in any DB2® service classes.
- Configuration type
- Database
- Parameter type
-
- Default [range]
- BASE [NONE, BASE, EXTENDED]
- Upgrade Note
- On databases created before V9.7 and
then upgraded to V9.7 or
higher, the mon_req_metrics parameter is set
to NONE by default.
If you set this configuration parameter to
BASE,
all metrics reported through the following interfaces are collected
for all requests executed on the data server, irrespective of the DB2 service class the request runs
in:
- MON_GET_UNIT_OF_WORK
- MON_GET_UNIT_OF_WORK_DETAILS
- MON_GET_CONNECTION
- MON_GET_CONNECTION_DETAILS
- MON_GET_SERVICE_SUBCLASS
- MON_GET_SERVICE_SUBCLASS_DETAILS
- MON_GET_WORKLOAD
- MON_GET_WORKLOAD_DETAILS
- Statistics event monitor (DETAILS_XML monitor element in the event_wlstats
and event_scstats logical data groups)
- Unit of work event monitor
If you set this configuration parameter to
EXTENDED,
the same metrics are collected as under the BASE setting. In addition,
the values reported for the following monitor elements are determined
with more granularity:
- total_section_time
- total_section_proc_time
- total_routine_user_code_time
- total_routine_user_code_proc_time
- total_routine_time
For information about how the EXTENDED setting affects these
monitor elements, refer to the detailed monitor element descriptions.
If
you set this configuration parameter to NONE, the
metrics reported through the previously listed interfaces, are collected
only for the subset of requests running in a DB2 service class whose service superclass has
the COLLECT REQUEST METRICS clause set to BASE.
DB2 Version 10.1 for Linux, UNIX, and Windows