Page History
...
The PMDB is the repository of the Precise product suite which stores application performance data for long-term analysis and trending reports. For more information, see the Precise Administration Guide.
| Anchor | ||||
|---|---|---|---|---|
|
...
The following agents are available:
| Agent name | Description |
|---|---|
| Application Performance agent | Precise for DB2 provides a complete view of application performance management by capturing, measuring and correlating performance metrics from all critical system components. |
| SAP™ | If ERP support is installed, the Collector also includes SAP. This agent provides data on the activities and resource consumption of packaged application entities. This data can help you identify ERP users, transactions, reports, and so on, that are heavy users of DB2 resources. The current version only supports SAP. |
| Storage agents | EMC Storage. See “Optional Collector extensions” on page 11. |
Precise Listener and Precise for DB2 FocalPoint
...
If ERP support is installed, the Collector provides detailed information on the activities and resource consumption of "packaged application" entities. It enables you to identify ERP users, transactions, reports, and so on, that are heavy users of DB2 resources and to drill down to the statements executed by them and the objects they accessed. See the Precise Installation Guide or the Precise Administration Guide.
| Anchor | ||||
|---|---|---|---|---|
|
...
The following table lists the existing In DB2 states.
Table 1-1 In DB2 states
| In DB2 state | Description |
|---|---|
| Using CPU | Time spent by the application using CPU. |
| CPU Wait | Time spent by the application waiting for CPU. |
| Sync I/O Wait | Time spent by the application waiting for a synchronous I/O request to/from the buffer pool. |
| Direct I/O Wait | Time spent by the application waiting for a direct I/O request of LOB or long column to/from the tablespace file bypassing the buffer pool. |
| Prefetch Wait | Time spent by the application waiting for a prefetcher to read into the buffer pool the next group of pages. |
| Lock Wait | Time spent by the application waiting for the release of a lock. |
| I/O Error Wait | Time spent by the application waiting for all active applications using a tablespace to release it in case of I/O error. The application that encounters an I/O error in a tablespace must wait to acquiesce the entire tablespace. |
| Remote Query Wait | Time spent by the application waiting for pending results from a remote federated server. |
| Utility Wait | Time spent by the application while waiting during running of a utility (command) such as: backup, restore, load, unload, restart, acquiesce and create a db. |
Overall Activity Graphs
The Overall Activity resource consumption graphs display information on total time spent in DB2 and a breakdown of activities outside of DB2. Overall Activity can help answer the question: Is the application spending its time in DB2 or elsewhere?"
The following table lists the Overall Activity states.
Table 1- 2 Overall Activity states
| Overall Activity state | Description |
|---|---|
| In DB2 (Summed) | Time spent by the selected item or items in the selected category executing an SQL statement. |
| UOW Waiting | Time spent by the application waiting for a request or input. For example, a Unit Of Work wait takes place when (1) a user starts a Command Line Processor session, connect to the database and then do nothing, (2) a client application executes an SQL statement, displays its result set on a window and waits for next GUI request while still connected, (3) export application writes fetched rows to an output file. |
| Decoupled from DB agent | Time spent by the application when a database agent (process) is not assigned to the connected application. This happens when using connection concentrator (MAX_CONNECTIONS > MAXCAGENTS). It is impossible to tell whether the application is idle or the application is waiting for an available database agent. |
| Connect Pending | Time spent by the application waiting for DB2 to complete connect request. |
| Disconnect Pending | Time spent by the application waiting for DB2 to complete disconnect request. |
| Wait for Remote Request | Time spent by the application waiting for a remote DB2 server to complete SQL execution. |
| Wait for Commit Phase II | Time spent by the application waiting for the coordinator to request DB2 to start commit phase II. This state is also known as an in-doubt transaction. |
| Anchor | ||||
|---|---|---|---|---|
|
...
More information on Precise, its products, technical notes, and so on, can be found in the Release Notes document for this version.
...
.
...