Re: dbms_shared_pool.keep
From: ddf <oratune_at_msn.com>
Date: Fri, 15 May 2009 12:46:49 -0700 (PDT)
Message-ID: <46f0e1b4-8a9c-4bec-b2a3-b8815d132494_at_s16g2000vbp.googlegroups.com>
On May 15, 2:34 pm, "Matthias Hoys" <a..._at_spam.com> wrote:
> "Shakespeare" <what..._at_xs4all.nl> wrote in message
>
> news:4a0dbedc$0$195$e4fe514c_at_news.xs4all.nl...
>
>
>
>
>
> > Mladen Gogala schreef:
> >> 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.
>
> > AFAIK, pinning those packages is a well known way to speed up APEX.
>
> > IIWIW
>
> > Shakespeare
>
> I also remember "something" about DBMS_SHARED_POOL.KEEP being of no more use
> for 10g.
> I didn't know this was a known trick to speed up APEX, although I can't
> remember reading about this on the OTN forum. Something to try out next
> week.
>
> Matthias- Hide quoted text -
>
> - Show quoted text -
Date: Fri, 15 May 2009 12:46:49 -0700 (PDT)
Message-ID: <46f0e1b4-8a9c-4bec-b2a3-b8815d132494_at_s16g2000vbp.googlegroups.com>
On May 15, 2:34 pm, "Matthias Hoys" <a..._at_spam.com> wrote:
> "Shakespeare" <what..._at_xs4all.nl> wrote in message
>
> news:4a0dbedc$0$195$e4fe514c_at_news.xs4all.nl...
>
>
>
>
>
> > Mladen Gogala schreef:
> >> 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.
>
> > AFAIK, pinning those packages is a well known way to speed up APEX.
>
> > IIWIW
>
> > Shakespeare
>
> I also remember "something" about DBMS_SHARED_POOL.KEEP being of no more use
> for 10g.
> I didn't know this was a known trick to speed up APEX, although I can't
> remember reading about this on the OTN forum. Something to try out next
> week.
>
> Matthias- Hide quoted text -
>
> - Show quoted text -
Nothing in DBMS_SHARED_POOL is listed as deprecated in the 11g documentation, nor in the 10gR2 docs.
David Fitzjarrell Received on Fri May 15 2009 - 14:46:49 CDT