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
http://www.free-online-exams.com
Much of the statement I/O is spent on waiting for a lock on the table specified in the Object column.
| Description | |
| What to do next | Select the findings type to examine lock for the statement in the Activity workspace. |
| Advice | To reduce the lock wait for the table, consider the following solutions: n Check to see if the lock appears in the Current workspace. If so, examine the lock chain to identify the statement holding the lock. n Try to identify the locking statement in the Activity workspace using the narrow time frames matching the lock periods. Now focus on the locked table and associated statements. The DML statement (and update queries) that are not waiting for locks are the immediate suspects. Findings refer to the whole statement - not to a specific execution plan. If a step doesn't exist in the selected execution plan (unless this is the result of an index overhead), switch to another plan and locate the relevant step. |
No comments:
Post a Comment