Page History
...
If you want detailed information on a wait event, in the Association area, click the row of the event that you want to view detailed information for. The Tab heading indicates the newly selected entity, and the Main area displays over time graphs for the wait event you drilled down to. There is no Association Area data for a wait event. See “How How most tabs are structured” on page 22structured.
| Anchor | ||||
|---|---|---|---|---|
|
...
| Column | Description |
|---|---|
| Wait Event | Name of the Oracle wait event. |
| In Oracle Sub-State | Equivalent Precise for Oracle wait sub-state. See “Wait States” on page 35.* Wait States. |
| Idle | Indicates whether Precise for Oracle categorizes the wait event as an idle event. Precise for Oracle considers certain events, such as sql*net message from client, rdbms ipc message or pmon timer, as idle because Oracle is effectively sleeping and not consuming any resources. The categorization affects the top 10 wait events displayed in the Wait Event view of the Tier or an instance. |
| Waits | Total number of occurrences of the wait event. |
| Timeouts | Total number of occurrences of the wait event that exceeded the timeout. Some events have a timeout associated with them. |
| Times Waited (Sum.) | Total time waited, displayed as a duration and bar graph. |
...
| Info |
|---|
The pie chart will not display what are considered to be idle events. |
See “Examining latches” on page 176 Examining latches.
To examine top 10 wait events
...
- First examine logical I/Os. See “Examining consistent gets” on page 176 Examining consistent gets.
- Now examine physical I/Os. For our example, the Statistics tab shows sampled data from the same time period as that shown for consistent gets over time. We can see that the average read and write time follows the number of physical I/O operations reasonably close, particularly the first peak on September 22nd. This indicates that there is some contention between I/O operations, perhaps because they are all reading from different points on the same disk, causing a rise in seek time.
...