DB2 Version 9.7 for Linux, UNIX, and Windows
DB2 Version 9.7 for Linux, UNIX, and Windows
Time spent waiting to write an audit record. The value is given in milliseconds.
| Table Function | Monitor Element Collection Level |
|---|---|
| MON_GET_CONNECTION_DETAILS table function - Get detailed connection metrics (reported in DETAILS XML document) | REQUEST METRICS BASE |
| MON_GET_SERVICE_SUBCLASS_DETAILS table function - Get detailed service subclass metrics (reported in DETAILS XML document) | REQUEST METRICS BASE |
| MON_GET_UNIT_OF_WORK_DETAILS table function - Get detailed unit of work metrics (reported in DETAILS XML document) | REQUEST METRICS BASE |
| MON_GET_WORKLOAD_DETAILS table function - Get detailed workload metrics (reported in DETAILS XML document) | REQUEST METRICS BASE |
| MON_GET_ACTIVITY_DETAILS table function - Get complete activity details (reported in DETAILS XML document) | ACTIVITY METRICS BASE |
| MON_GET_PKG_CACHE_STMT_DETAILS table function - get detailed metrics for package cache entries | ACTIVITY METRICS BASE |
| 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 |
| Package cache | Reported in the activity_metrics document. | ACTIVITY METRICS BASE |
| Statistics | event_scmetrics* | REQUEST METRICS BASE |
| Statistics | event_wlmetrics* | REQUEST METRICS BASE |
| * When returned as part of this logical data group, this element reflects the change in value of this metric since the last statistics collection or database activation, whichever was more recent. | ||
Use this monitor element to determine the amount of time an agent spends waiting to open and write an audit event synchronously to disk.
In a typical scenario, only one agent attempts to open the audit log file at a time, as the other agents wait for access to the audit common subsystem before opening the file. Therefore, the wait time usually represents the time spent waiting to write the file to disk by the operating system. Audit utilities might lock the audit log file during execution, which causes a longer than normal wait time for agents to open and write to the audit log file. If asynchronous auditing is enabled, audit events that are larger than the asynchronous audit buffer are written directly to disk, instead of to the buffer, and contribute to the wait time.
Outside of the special audit utility scenario, the wait time depends on the speed of the disks and how quickly the operating system can write the data to them. In order to reduce this wait time for a given application and audit configuration, you might tune the operating system or use faster disks.