Re: Debugging a buffer busy waits
Date: Mon, 30 Mar 2009 20:44:28 +0000 (UTC)
On Sat, 28 Mar 2009 18:30:33 +0100, Ste wrote:
> Hi all,
> Last day I've encountered a problem with a procedure waiting due to a
> buffer busy waits. In v$session_wait I've found FILE# and BLOCK#.
> Looking in DBA_SEGMENTS I've discovered incriminated blocks is belonging
> to a table called 'DUMMYTBL'.
> Ok, now I can discover which other SIDs are using this table?
> P3 code is 130 meaning no suitable images are found of this block.
> Deadlock are not signalled in alert.log.
You could try V$ACCESS table.Received on Mon Mar 30 2009 - 15:44:28 CDT