Re: shared pool latching issue and missing time in trace file

without going into the time details: In any case looking similar, I'd always check for child cursor issues. Having lots of children for one SQL, can cause heavy library cache lookup concurrency.

I had a presentation on this on Collaborate and OOW 2012, maybe you want to have a look:
http://www.usn-it.de/index.php/2012/09/30/oracle-open-world-resolving-child-cursor-issues-resulting-in-mutex-waits/

I'm always interested in details and cases, so can you please tell us your DB version, and what v$session and v$sql_shared_cursor looks like?

BR
Martin Klier

Sigrid Keydana schrieb:
> Hi,
>
> sorry for the misformatted mail this morning - I'm trying again.
>
> I'd like to ask for your advice debugging a shared pool latching problem. For background, let me state that in general, in the application concerned, shared pool fragmentation has been a known issue, but less so in the present since quite some work has been done to reduce hard parsing. However, there is a statement (which I cannot reproduce here but might do so in a masked form if required) that regularly causes the alert (deemed "harmless" by Oracle Support, see 330239.1)

-- 
Usn's IT Blog for Linux, Oracle, Asterisk
http://www.usn-it.de


-- 
Usn's IT Blog for Linux, Oracle, Asterisk
http://www.usn-it.de

--
http://www.freelists.org/webpage/oracle-l