Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: ORA-04031 and shared pool

Re: ORA-04031 and shared pool

From: Mark D Powell <mark.powell_at_eds.com>
Date: 3 Sep 2001 11:21:54 -0700
Message-ID: <178d2795.0109031021.e5d2561@posting.google.com>


"Howard J. Rogers" <howardjr_at_www.com> wrote in message news:<3b90971d$1_at_news.iprimus.com.au>...
> There's a bug in 8.1.5 that means when timed_statistics=TRUE then no sharing
> of SQL statements is possible -so everything will be being re-parsed like
> crazy (bye-bye Library Cache).
>
> Extraordinary, but true.
>
> Allegedly fixed in 8.1.6 (and I think we might have heard about it if not)
>
> Regards
> HJR
>
> > > > >
> > > > Mario, we had have the same problem since upgrading to version 8.1.7.
> > > > We have entered a two tars with Oracle support and they have been
> > > > little help. We have verified all our shared memory settings. We ran
> > > > the SQL Oracle provided to see SQL that is causing other SQL to flush
> > > > out of the pool and no luck there. We upped our shared pool by 20M
> > > > over version 8.0.5 (not including separate 20M for java, which we do
> > > > not use) and no help. We show 20% free when jobs start dieing.
> > > >
> > > > We can run about three weeks before we have a problem. But once we
> > > > have a problem jobs just die with 04031 or 06508 and the only way to
> > > > clear the problem is to bounce the system. Flushing the pool does not
> > > > work. We pin all our large packages at instance startup plus most of
> > > > the heavy hit Oracle provided packages. If we do weekly maintenance
> > > > and bounce the system every week we do not get the errors, but leave
> > > > the system running for about three weeks and production dies.
> > > >
> > > > We are going with the weekend bounce. What a pain.
> > > >
> > > > -- Mark D Powell --
> >
> > No support has not mentioned any issues with timed statistics, which
> > we do have set to true. We need the stats for occassional tuning and
> > have had them set to true in our production instance since version
> > 7.0.
> >
> > I may well ask about it though.
> >
> > -- Mark --

Howard, Thanks for the bug update information.

Received on Mon Sep 03 2001 - 13:21:54 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US