Hi Larry and list,
As everyone has said, the consultant was mistaken. This email is just to add my
2c to the matter of what happens with an invalidation.
When a library cache object is marked for keeping a bit flag called the keep
mask is set in the library cache handle for that object to indicate which heaps
are to be kept. This flag field is visible as KGLHDKMK in the X$KGLOB family of
X$ tables. During an invalidation it is the library cache object itself that is
invalidated, not its handle, and the low order bit of KGLOBFLG is reset
accordingly. Despite the invalidation of the object, the handle with its keep
mask persists in the cache, and when the object is reloaded there is no need to
do anything to re-establish the kept status of the object heaps.
By the way, it is rather unhelpful to speak of keeping as pinning. In the
context of the library cache a pin is lock held by a particular session on one
or more of the heaps of an object. In the context of the shared pool, a pin is a
bit flag in the header of a recreatable chunk indicating whether it is eligible
to be aged out or flushed from the shared pool. Library cache object heaps that
are marked for keeping may not be pinned in either sense.
@ Regards,
@ Steve Adams
@ http://www.ixora.com.au/
@ http://www.christianity.net.au/
-----Original Message-----
Sent: Saturday, 28 April 2001 11:50
To: Multiple recipients of list ORACLE-L
Rafiq,
Thanks for taking the time to address this aspect. Those are the type of
details that help me in some of the areas I am trying to get my arms around
and better understand. I was aware of how the objects could become
invalidated, but, I didn't know it would be "re-pinned". It's something I
had wondered about but hadn't had the chance to look into yet.
Once again, thanks for your comments, as well as thanks to everyone else who
took the time to respond.
Regards,
Larry G. Elkins
[EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mohammad
> Rafiq
> Sent: Friday, April 27, 2001 4:33 PM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Pinning Packages Question
>
>
> Normally aging does not kick out pinned objects provided shared pool is
> rightly sized but there are situations when application because
> of dropping
> some objects makes pinned objects invalid and hence they are reloaded as
> kept=YES again.
>
> for example in following list this objects are pinned and shared pool is
> right sized but they are reloaded more than once because of invalidation.
>
> OWNER name K LOADS EXECUTIONS KEP
> ----- ------------------------- ---------- ---------- ---------- ---
> OLAPA PCS_PKG1 0 8 0 YES
> OLAPA HTZ_SRT_PACKAGE_OLAP 12 9 0 YES
> OLAPA HTZ_SRT_PACKAGE_OLAP 12 9 0 YES
>
> Hope this explanation will help..
> Regards
> Rafiq
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Steve Adams
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
