Tuesday, June 14, 2011

Heavy Statement Wait

Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com


The statement is a major consumer of Oracle resources. By tuning the statement, you may free resources needed by other statements and processes.
Heavy Statement findings

Description
What to do next
Try to determine what is causing the statement's high resource consumption. In the SQL workspace, examine the text of the relevant statement, and its findings, execution plan, change data and statistics.
Advice
For resource consumption, these are the possible scenarios:
n   Object wait on statement objects.
Use SQL findings to identify the heaviest waiting object.
n   High CPU consumption without object wait.
Check the number of executions (to identify possible infinite loops) or intensive statements (with a low average time but a high aggregated CPU time).
n   Instance-related wait (such as: internal lock wait, shared pool wait, and redo log wait).
In this case, switch to the Statistics workspace and examine the breakdown of this state in Oracle events.
n   A change in the execution plan.
If this is responsible for the statement's performance degradation, check the History tab and the All Plans view to identify the actual change that caused the slowdown.
n   Check the Binds tab for possible offensive values resulting in differing execution plans and performance.



Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: