Measures reported by TibSessWaitTest
The test monitors the session level wait events on the Tibero database server and reports key performance statistics pertaining to every event. Effective wait analysis helps determine where the database spends most of its time, and which current connections are responsible for the reported waits.
Outputs of the test : One set of results for each target database server being monitored.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Total_waits |
Indicates the total number of times waits happened on this event since the last measurement period. |
Number |
If the value of this measure is very high, then you can drill down further using the detailed diagnosis capability (if enabled) of the eG Enterprise suite to discover which current connections may be responsible for this. The detailed diagnosis of this measure reveals the session IDs of the sessions that caused the wait events to occur, the users who initiated the sessions, and the total number of waits, wait time, and the maximum wait time for every session. |
| Total_waits_timedout |
Indicates the total number of waits on this event that timed out since the last measurement period. |
Number |
A large number of timed out wait events is typically, undesirable. Use Oracle-specific documentation to probe the cause of the timeout. |
| Avg_time_waited |
Indicates the average duration for which the waits on this wait event persisted since the last measurement period. |
Secs |
Ideally, the value of this measure should be low. A very high value or a consistent increase in this value is indicative of a problem situation requiring further investigation. Use the detailed diagnosis capability to zoom into the session that has contributed to the abnormal increase in wait time. |
| Max_time_waited |
Indicates the high watermark of wait time for this wait event. |
Secs |
|
|