RE: Latch Free / Shared Pool on Fetch

Larry,

>Why is a shared pool latch taken when (between?) fetching rows
>from a query?
>I have a trace file where once we start hitting the fetch lines, we are
>seeing latch free waits on the shared pool (9.2.0.5, p2 of
>156=shared pool).

This particular question has been vexing me as well :) The only sane explanation that I could come up with is that there could be recursive sql being executed between each fetch, probably via an inline function that requires parsing (soft/hard) that would require the shared pool latch to be taken out. Is this the case? Keep in mind also both 10046 as well as v$session_wait only record the last _instrumented_ wait, and the process could be executing code that is not instrumented......

One of my frustrations with the 10046 trace is that it does not snapshot/record data from v$sesstat, which I believe could yield some clues or at least explain where c=<> was possibly consumed. Not bashing the 10046 trace, just pointing out a helpful but missing item....

Let us know!
John Kanagaraj <><
DB Soft Inc
Phone: 408-970-7002 (W)

Listen to great, commercial-free christian music 24x7x365 at http://www.klove.com

• The opinions and facts contained in this message are entirely mine and do not reflect those of my employer or customers **

  ---

  Please see the official ORACLE-L FAQ: http://www.orafaq.com

  ---

  To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line. -- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html

  ---