Re: dbms_shared_pool.keep

From: <>
Date: Fri, 15 May 2009 17:01:09 -0700 (PDT)
Message-ID: <>

On May 15, 2:17 pm, Mladen Gogala <> 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.
> --

You can't believe everything you read ... especially if you cannot find it any more eh?

What's wrong exactly with pinning important packages if you have enough memory? Received on Fri May 15 2009 - 19:01:09 CDT

Original text of this message