Looks like another Java shared pool overrun. Increase JAVA_POOL_SIZE
and bounce the db. This "shared pool" has [almost] nothing to do with
conventional shared pool. And AFAIR there were some memory leaks in
JDBC, so you better install the latest patchset for your OS (8.1.7.3 is
latest, but not sure it's available for linux/intel). But most probably you
are simply running out of Java shared pool here on heavy load.
--
Vladimir Zakharychev (bob@dpsp-yes.com) http://www.dpsp-yes.com
Dynamic PSP(tm) - the first true RAD toolkit for Oracle-based internet applications.
All opinions are mine and do not necessarily go in line with those of my employer.
"Dirk Versavel" <dirk.versavel_at_smartlounge.be> wrote in message
news:4eeeef52.0204152330.7ad9f467_at_posting.google.com...
> Dear,
>
> I'm running oracle 8.1.7 on RedHat Linux 6.2.
>
> Since some time (since the database is more intensively used), the
> database stops responding about once a week. A database restart is
> necessary.
>
> The error is:
> ORA-04031: unable to allocate 4096 bytes of shared memory ("shared
> pool","BEGIN :p := CTX_QUERY.PREFER...","PL/SQL MPCODE","BAMIMA: Bam
> Buffer")
>
> I tried to raise the "shared_pool_size" in the init.ora file but it
> does not seem te help much!
>
> The database is used by a number of J2EE based web applications using
> the oracle type 4 JDBC driver (classes12.zip). Could there be a
> 'memory leak' in the driver of in the client application causing these
> memory problem?
>
> We are also using intermedia quite intensively.
>
> Please help!
>
> Dirk
Received on Wed Apr 17 2002 - 11:33:06 CDT
