RE: Latch Free / Shared Pool on Fetch
- From: "Larry Elkins" <elkinsl@xxxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 6 Jul 2004 08:18:17 -0500
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@xxxxxxxxx
214.954.1781
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jonathan Lewis
> Sent: Saturday, July 03, 2004 5:07 AM
> To: oracle-l@xxxxxxxxxxxxx
> 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
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx
put 'unsubscribe' in the subject line.
--
Archives are at //www.freelists.org/archives/oracle-l/
FAQ is at //www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
Other related posts:
