Re: ORA-4031

From: Ana C. Dent <anacedent_at_hotmail.com>
Date: Mon, 16 Aug 2004 00:37:32 GMT
Message-ID: <Xns9546B34C86A8ASunnySD@68.6.19.6>

"DK" <dakight_at_bellsouth.net> wrote in
news:l6TTc.843$B53.769_at_bignews6.bellsouth.net:

> We got a ora-4031 in a production environment.
> In in an effort to circumvent the 4031 we;
>
> a.
> increased the size of the shared pool
>
> b.
> have asked the developers to use bind variables
>
> c. are
> flushing the shared pool nightly
>
> d.
> eliminated the session_cached_cursors=1000 from the spfile(9.2.0.5)
>
>
>
> Questions;
>
> 1. The dba on duty said that he could not get into the database.
> Will a 4031 cause a database to lock up?
Not likely?
What in the alert_SID.log file?

> 2. We run an analyze nightly.

WHY?
Do you have any proof that doing has a net benefit & no downside risk/cost?

>I'm I buying anything by flushing the shared pool?
No.

I suggest you should be pinning all your packages into the SGA at database startup. Received on Sun Aug 15 2004 - 19:37:32 CDT