Re: Debugging a buffer busy waits
From: <stevedhoward_at_gmail.com>
Date: Sun, 29 Mar 2009 05:04:54 -0700 (PDT)
Message-ID: <f545034a-3928-44c4-b321-0a4d072fb926_at_v19g2000yqn.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: Sun, 29 Mar 2009 05:04:54 -0700 (PDT)
Message-ID: <f545034a-3928-44c4-b321-0a4d072fb926_at_v19g2000yqn.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
Hi,
What version?
Regards,
Steve Received on Sun Mar 29 2009 - 07:04:54 CDT