RE: Pinning Packages on the shared pool
- From: <Joel.Patterson@xxxxxxxxxxx>
- To: <fuadar@xxxxxxxxx>, <prabhu_adam@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 28 Mar 2011 13:34:08 -0400
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@xxxxxxxxx]
Sent: Monday, March 28, 2011 11:14 AM
To: Patterson, Joel; prabhu_adam@xxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
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@xxxxxxxxxxx" <Joel.Patterson@xxxxxxxxxxx>
To: prabhu_adam@xxxxxxxxxxx; oracle-l@xxxxxxxxxxxxx
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@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Prabhu Krishnaswamy
Sent: Thursday, March 24, 2011 12:50 PM
To: oracle-l@xxxxxxxxxxxxx
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
Other related posts:
