Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: Latch Free / Shared Pool on Fetch
An event, one that checks for heap corruption (a bug related to a
kcoapl_blkchk error), was the culprit. When digging deeper into the latches,
there was a *lot* of activity on "kghdmp: heap descriptor". Not that we knew
what it *meant*, but an Oracle Support analyst recognized that as heap check
taking place, something that would not normally appear unless certain
event(s) are set.
Regards,
Larry G. Elkins
elkinsl_at_flash.net
214.954.1781
> -----Original Message-----
> From: oracle-l-bounce_at_freelists.org
> [mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Jonathan Lewis
> Sent: Saturday, July 03, 2004 5:07 AM
> To: oracle-l_at_freelists.org
> Subject: Re: Latch Free / Shared Pool on Fetch
>
>
>
> Just a couple of guesses
>
> Do you have cursor_sharing set to force or similar ?
>
> Is there a pl/sql function call or globally packaged
> variable in the SQL statement ?
>
> Does the statement reference sys_context()
>
>
> Regards
>
> Jonathan Lewis
>
> http://www.jlcomp.demon.co.uk
>
> http://www.jlcomp.demon.co.uk/faq/ind_faq.html
> The Co-operative Oracle Users' FAQ
>
> http://www.jlcomp.demon.co.uk/seminar.html
> Optimising Oracle Seminar - schedule updated May 1st
-- Archives are at http://www.freelists.org/archives/oracle-l/ FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------Received on Tue Jul 06 2004 - 08:11:34 CDT