Today on a busy production system I saw dozens of sessions waiting on buffer busy waits events. p1 and p2 from v$session_wait were the same and mapped to one of our very large unique indexes on a large table. For all but one of the sessions, p3=130. Using Metalink and Steve Adams's website, it seems p3=130 means that "the block is being read by another session and no other suitable block image was found, so we wait until the read is completed, a buffer cache deadlock, or the kernel can't get a buffer in a certain amount of time and assumes a deadlock". For the single, non-p3-130 session, p3=1. I killed the session where p3=1 (it shouldn't have been running anyway) and things went back to normal quickly. My question - what does it mean when p3=1 on buffer busy waits for an index? I must be looking in the wrong documentation, but I can't find the answer anywhere. Thanks.
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: John Clarke INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).
