Re: Debugging a buffer busy waits
From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Mon, 30 Mar 2009 20:44:28 +0000 (UTC)
Message-ID: <gqravc$vdd$2_at_solani.org>
On Sat, 28 Mar 2009 18:30:33 +0100, Ste wrote:
Date: Mon, 30 Mar 2009 20:44:28 +0000 (UTC)
Message-ID: <gqravc$vdd$2_at_solani.org>
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.
>
> Thanks
> Ste
You could try V$ACCESS table.
-- http://mgogala.freehostia.comReceived on Mon Mar 30 2009 - 15:44:28 CDT