When we open the performance page of a particular database we can see the below image:
Working with Average Waiting Session Graph of OEM grid control
The Average Active Sessions chart of the Performance page shows potential problems inside the database, including how much CPU users are consuming. The wait classes show how much of the database activity is consumed by waiting for a resource such as disk I/O and many more details. We can see all the detals in right panel of the Average Waiting Session graph.
Suppose when we open the performance tab we see the huge increase in “application waits”. this is the colored portion of the Average Active Sessions graph.
Then we decide to investigate this further, and clicks the graph. This drills down to next figure, which shows the actual breakdown of the application waits, most of which are type “enq: TX – row lock contention.”
It is possible to change the period of time to be examined by simply dragging the shaded area of the graph with the mouse. Doing this displays the sessions and SQL statements active in that time period.
Now we examines the Top SQL list and clicks the top-most SQL ID.
The SQL statement corresponding to this SQL ID is displayed in next figure. The sessions that have issued this SQL statement are also displayed on the same page.
The issue has been identified as row lock contention, and the SQL statement causing this issue has also been found. So far, this information has come from the Database Performance page and the drill-downs
Working with Average Waiting Session Graph of OEM grid control
The Average Active Sessions chart of the Performance page shows potential problems inside the database, including how much CPU users are consuming. The wait classes show how much of the database activity is consumed by waiting for a resource such as disk I/O and many more details. We can see all the detals in right panel of the Average Waiting Session graph.
Suppose when we open the performance tab we see the huge increase in “application waits”. this is the colored portion of the Average Active Sessions graph.
Then we decide to investigate this further, and clicks the graph. This drills down to next figure, which shows the actual breakdown of the application waits, most of which are type “enq: TX – row lock contention.”
It is possible to change the period of time to be examined by simply dragging the shaded area of the graph with the mouse. Doing this displays the sessions and SQL statements active in that time period.
Now we examines the Top SQL list and clicks the top-most SQL ID.
The SQL statement corresponding to this SQL ID is displayed in next figure. The sessions that have issued this SQL statement are also displayed on the same page.
The issue has been identified as row lock contention, and the SQL statement causing this issue has also been found. So far, this information has come from the Database Performance page and the drill-downs
No comments:
Post a Comment