Tuesday, June 14, 2011

Heavy I/O Due To Direct Access 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


Statement I/O is spent on direct I/O (usually representing the SQL Loader in the direct path), on the object specified in the Object column.
Heavy I/O Due To Direct Access findings

Description
What to do next
Perform one of the following options:
n   Click the Locate icon to find the relevant step in the execution plan.
n   Select the findings type to investigate the objects used and their structure in the Objects tab.
n   Select the Activity workspace, locate the statement associated with objects, and drill to the object (table/index) consumption for the statement in the Activity workspace.
Advice
To reduce the I/O consumption for the object, consider the following solutions:
n   If this is the result of an SQL loader utility in a direct path, make sure the temporary segments for the index updates are on a fast device.
n   Use the SINGLEROW option.
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.


    
Get Oracle Certifications for all Exams
Free Online Exams.com

No comments: