Re: Is this serious?

Are you pinning frequently used objects in the shared pool? If not you should be. That reduces fragmentation which is usually the cause of ORA-4031. How big is your shared pool?

There are also known memory leaks in the shared pool in earlier versions of 8i. 8.1.6 was the worst. Avoid it like the plague. As someone else stated you need to get up to the latest release of 8.1.7 for your platform.

"Tom" <tomNOSPAM_at_eazyriders.com> wrote in message news:n67d9.9261$Me5.70638758_at_news-text.cableinet.net...
> Hi,
>
> We are running 8.1.5 on Solaris7.
> About once every month or so i get errors from the instance that are the
> following....
>
> Exception in thread "main" uk.co.goodtech.listener.ListenerException:
> uk.co.goodtech.listener.ListenerException: Problem generating index:
> java.sql.SQLException:
> ORA-04031: unable to allocate 4096 bytes of shared memory ("shared
> pool","DBMS_LOB","PL/SQL MPCODE","BAMIMA: Bam Buffer")
> ORA-06508: PL/SQL: could not find program unit being called
> ORA-06512: at line 1 at
>

 uk.co.goodtech.listener.ListenerManager.notifyListeners(ListenerManager.java
> :136)
> at uk.co.goodtech.cms.RebuildIndexes.indexSection(RebuildIndexes.java:81)
> at uk.co.goodtech.cms.RebuildIndexes.main(RebuildIndexes.java:60)
>
> now the other instances seem fine when this happens and it seems to
 revover
> itself before i can get to fix it. Does this problem look serious as when
 it
> occurred once i had to bounce the instance. Reading up on the error it
 seems
> it could be memory related but i'll be interested to hear if others have
> seem this. A search on google shows the problem but not really a
 resolution.
>
> thanks
>
> Tom
>
>
>
Received on Tue Sep 03 2002 - 15:11:39 CDT