We've lot buffer busy waits in data block with P3 value 130 in V$session.
I've read about this in few notes, but still I do not understand few things.
P3=130 means:
-------------
Block is being read by another session and no other
suitable block image was found, so we wait until the read
is completed. This may also occur after a buffer cache
assumed deadlock. The kernel can't get a buffer in a
certain amount of time and assumes a deadlock.
Therefore it will read the CR version of the block.
Does it mean that the block is being held in an incompatible mode by the
first session or set of sessions reading it in shared mode, and current
session is trying to lock it exclusively for a DML and waiting for the same.
What are steps we can take to avoid this types of buffer busy waits?
Thanks for your help.
Sri
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Srikannan Gopalsamy
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
