Re: 10046 trace question + ORASRP possible problem.
- From: James Foronda <James.Foronda@xxxxxxx>
- To: Oracle-L@xxxxxxxxxxxxx
- Date: Mon, 03 Jul 2006 19:46:30 -0400
Norman,
If so, the ORASRP version 2.1 is lumping the latch free waits above
into the details for the first statemenmt rather than the second. I
fiddled the latch number to see where ORASRP was puting the latch free
details - it's actually the library cache latch (157) that is being
waited on - 555 is just a dummy number I chose for the experiment.
Sometime last month, I mentioned that I noticed some differences between
Hotsos v4.x profiler and orasrp outputs:
//www.freelists.org/archives/oracle-l/06-2006/msg00119.html
I believe this is one of them... but I do remember that there's
something else. I can not remember what it is right now but I intend to
go back and do the comparison again, make some detailed notes, and I
will report the differences here.
James
--
//www.freelists.org/webpage/oracle-l
Other related posts:
