RE: Pinning Packages on the shared pool

From: Mark W. Farnham <mwf_at_rsiz.com>
Date: Thu, 24 Mar 2011 16:04:07 -0400
Message-ID: <01bb01cbea5e$a31970d0$e94c5270$_at_rsiz.com>

+1 to Mark's approach. Avoiding elapsed time and doing anything not required for maintenance and (shudder) recovery bounces is a saver of precious time.  

mwf  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Powell, Mark
Sent: Thursday, March 24, 2011 3:04 PM
To: oracle-l_at_freelists.org
Subject: RE: Pinning Packages on the shared pool  

We wrote our own database instance startup and shutdown scripts. Our startup scripts pin numerous Oracle and home-grown packages and execute a dummy procedure to load the entire package into memory since back in 7.x days pinning only loaded the package specification into memory.  

This works well for us and easily allows us to start the database without firing the load and pin process when we want to.    

---

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

Received on Thu Mar 24 2011 - 15:04:07 CDT