Re: Debugging a buffer busy waits
From: <johnbhurley_at_sbcglobal.net>
Date: Sat, 28 Mar 2009 12:13:06 -0700 (PDT)
Message-ID: <23ea25a5-645e-42ae-9a65-9729554abcb2_at_k2g2000yql.googlegroups.com>
On Mar 28, 1:30 pm, Ste <s..._at_ste.it> 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
Date: Sat, 28 Mar 2009 12:13:06 -0700 (PDT)
Message-ID: <23ea25a5-645e-42ae-9a65-9729554abcb2_at_k2g2000yql.googlegroups.com>
On Mar 28, 1:30 pm, Ste <s..._at_ste.it> 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
Why don't you look for SQL in your database instance that is going after DUMMYTBL? Received on Sat Mar 28 2009 - 14:13:06 CDT