Re: Trying to locate a cursor with very little information
From: Chen Shapira <cshapi_at_gmail.com>
Date: Tue, 7 Jul 2009 16:04:27 -0700
Message-ID: <e37540930907071604u3322cba1y88d71af799ac2c04_at_mail.gmail.com>
I don't have the sql text in the trace file, but Oracle still have the cursor in the shared pool.
And Oracle knows that cursor #2 from a specific process is related to a specific open cursor in the pool (otherwise exec and fetch calls would fail). So there must be a way to find the sql text from Oracle's SGA. I was hoping someone already figured it out...
Date: Tue, 7 Jul 2009 16:04:27 -0700
Message-ID: <e37540930907071604u3322cba1y88d71af799ac2c04_at_mail.gmail.com>
I don't have the sql text in the trace file, but Oracle still have the cursor in the shared pool.
And Oracle knows that cursor #2 from a specific process is related to a specific open cursor in the pool (otherwise exec and fetch calls would fail). So there must be a way to find the sql text from Oracle's SGA. I was hoping someone already figured it out...
Chen
On Tue, Jul 7, 2009 at 3:51 PM, Daniel Fink<daniel.fink_at_optimaldba.com> wrote:
> If you don't have the PARSE or PARSING lines, you won't have the sql text.
> However, if the STAT lines were written, you might be able to reverse
> engineer the statement from the plan. Use the STAT lines to see what plans
> use those operations and what statements use those plans.
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Jul 07 2009 - 18:04:27 CDT