Re: READ wait events when inserting data into a CLOB
From: Saibabu Devabhaktuni <saibabu_d_at_yahoo.com>
Date: Wed, 5 Dec 2012 13:02:51 -0800 (PST)
Message-ID: <1354741371.87203.YahooMailNeo_at_web161305.mail.bf1.yahoo.com>
Martin,
You'd typically see "direct path" reads and writes for LOB insert operations if the lob is stored out of line or if the lob size exceed 4K. You may be getting "db file sequential read" waitevent for your indexes on the table. You'd also see "db file sequential read" waitevent for lobindex operations.
Date: Wed, 5 Dec 2012 13:02:51 -0800 (PST)
Message-ID: <1354741371.87203.YahooMailNeo_at_web161305.mail.bf1.yahoo.com>
Martin,
You'd typically see "direct path" reads and writes for LOB insert operations if the lob is stored out of line or if the lob size exceed 4K. You may be getting "db file sequential read" waitevent for your indexes on the table. You'd also see "db file sequential read" waitevent for lobindex operations.
Another possibility is flashback feature requiring blocks to be read from the disk prior to performing block new operation.
I see below trace data very interesting, why same block is being read with "db file sequentially read" and "direct path read".
WAIT #139690535902720: nam='db file sequential read' ela= 321 file#=5 block#956449 blocks=1 obj#425 tim54644922208727 WAIT #139690535902720: nam='direct path read' ela= 216 file number=5 firstdba956449 block cnt=1 obj#425 tim54644922208998
Thanks,
Sai
http://sai-oracle.blogspot.com
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Dec 05 2012 - 22:02:51 CET