Re: dbms_shared_pool.keep

From: joel garry <joel-garry_at_home.com>
Date: Fri, 15 May 2009 16:43:51 -0700 (PDT)
Message-ID: <acd68998-28e7-4695-9f33-f9e2345facd5_at_j9g2000prh.googlegroups.com>



On May 15, 11:17 am, Mladen Gogala <mla..._at_bogus.email.com> wrote:
> Today, I noticed a performance problem on one of my databases. Statspack
> was showing quite a few of library cache waits. Most of the waiting
> sessions were trying to execute the same procedure and the problem was
> alleviated to significant degree by pinning the the package that contains
> the offending procedure, as well as all of the other PL/SQL objects
> belonging to FLOWS_03000.
> Trouble is, I distinctly remember rading an article claiming that using
> DBMS_SHARED_POOL.KEEP is not good, that it is, in fact, obsolete. I can't
> locate the article so I will ask anyone who thinks that I shouldn't have
> done what I did, to explain me why? In other words, am I missing something
> or not? I have sufficient free memory, no danger of 4031 in the near
> future.
>
> --http://mgogala.freia.com

While I never found what I was looking for about which you asked (in the 5 minutes allotted, I was thinking perhaps you were thinking of the recycle/keep stuff), I did find this gem, flushing a single cursor, which I had never noticed before: http://el-caro.blogspot.com/2007_10_01_archive.html

jg

--
_at_home.com is bogus.
“Not everything in politics is rational.” - Jerry Brown
“I understand that, I've watched you a long time.” - Roger Hedgecock
http://www3.signonsandiego.com/stories/2009/may/15/1m15brown235851-brown-stops-lunch-gop-turf/?uniontrib
Received on Fri May 15 2009 - 18:43:51 CDT

Original text of this message