Re: How to find the exact SQL locking others?
From: Alex Fatkulin <afatkulin_at_gmail.com>
Date: Mon, 2 Jul 2012 13:00:31 -0400
Message-ID: <CAMVw97Kruhn+gyytU1HUeR3w0kakPWBisKvmPn7PCd=YyQQc9w_at_mail.gmail.com>
This is true, just keep in mind that nothing prevents a session from closing a cursor, locks/transactions are not linked to cursors in any way I know of.
Date: Mon, 2 Jul 2012 13:00:31 -0400
Message-ID: <CAMVw97Kruhn+gyytU1HUeR3w0kakPWBisKvmPn7PCd=YyQQc9w_at_mail.gmail.com>
This is true, just keep in mind that nothing prevents a session from closing a cursor, locks/transactions are not linked to cursors in any way I know of.
You can continue for quite a while, like see if you got lucky and stuff got captured in ASH, etc.
On Mon, Jul 2, 2012 at 12:43 PM, Andy Klock <andy_at_oracledepot.com> wrote:
>
>
> On Monday, July 2, 2012, Alex Fatkulin <afatkulin_at_gmail.com> wrote:
>> sql_id/prev_sql_id for session 1 will be useless. The first statement
>> executed by session 1 might event be out of shared pool by now!
>>
>
> True, but you might still be able to see a trace of it in v$open_cursor.
>
> Andy
-- Alex Fatkulin, http://afatkulin.blogspot.com Enkitec, http://www.enkitec.com -- http://www.freelists.org/webpage/oracle-lReceived on Mon Jul 02 2012 - 12:00:31 CDT