Re: Pinning Packages on the shared pool

on very busy systems , ERP type systems or systems where there is less memory 
available . I have seen that  happen where objects coming in are greating that 
available chunks this causing  a full flush before bringing  these objects back 
in. 
Not all databases fit in these circumtances and with memory being cheap people 
can have enough to the point where memory flushes from LRU dont happen . but 
there will always be cases and pinning objects help you ensure that the more 
critical objects are not the ones that are impacted.



________________________________
From: "Joel.Patterson_at_crowley.com" <Joel.Patterson_at_crowley.com>
To: fuadar_at_yahoo.com; prabhu_adam_at_hotmail.com; oracle-l_at_freelists.org
Sent: Mon, March 28, 2011 12:34:08 PM
Subject: RE: Pinning Packages on the shared pool

  
Thank you,
 
But is that likely?   Its analogous to saying they can still phase out even so 
most of the time they are at the most recently used side of the LRU list. 

 
Joel Patterson
Database Administrator
904 727-2546

________________________________
 
From:Fuad Arshad [mailto: fuadar_at_yahoo.com ] 
Sent: Monday, March 28, 2011 11:14 AM
To: Patterson, Joel; prabhu_adam_at_hotmail.com; oracle-l_at_freelists.org
Subject: Re: Pinning Packages on the shared pool
 
not true . Oracle can still phase out even frequently used packages in favor of 
cursors.
A startup trigger is the way and actually I use an oracle utility from MOS 
Toolkit for dynamic marking of Library   Cache objects as Kept (PIND) [ID 
301171.1] 

            
It is  a very useful utility to automatically detect objects and  mark them for 
pinned prior to shutdown and then pin them after startup.
 
 

________________________________
 
From:"Joel.Patterson_at_crowley.com" <Joel.Patterson_at_crowley.com>
To: prabhu_adam_at_hotmail.com;  oracle-l_at_freelists.org
Sent: Mon, March 28, 2011 10:07:56 AM
Subject: RE: Pinning Packages on the shared pool
>  Our appliction team has requested (as per vendor's recommendations), to pin 
>the frequently used packages…
 
Maybe I’m missing something here, so comments are welcome.    If these 6 to 8 
are used frequently, then they will never page out from the LRU list no?  so in 
essence will always be in memory, (or at least almost all of the time).
 
So….  are we not complicating something that is essentially not needed?
 
Joel Patterson
Database Administrator
904 727-2546

________________________________
 
From:oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On 
Behalf Of Prabhu Krishnaswamy
Sent: Thursday, March 24, 2011 12:50 PM
To: oracle-l_at_freelists.org
Subject: Pinning Packages on the shared pool
 
Lists,
 
Our appliction team has requested (as per vendor's recommendations), to pin the 
frequently used packages (around 6 to 8 packages) on the shared pool. We thought 
of pinning the packages using the DB Startup trigger, so every time DB recyles, 
those packages gets included on the memory. Is there any other better way of 
handling this rather than using the startu trigger. Any advice is highly 
appreciated.
 
Thank you,
Prabhu

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