That was it - JAVA_POOL_SIZE too small. Thanks.
I am assuming the Java option was installed by default although the
applications do not use Java VM. I really don't want to chew up so much of
the SGA with the java pool.
I guess I will have to recreate the database.
Regards
Ray
"Vladimir M. Zakharychev" <bob@dpsp-yes.com> wrote in message
news:a9ebko$1q2$1@babylon.agtel.net...
..and those synonyms are for JOX classes (ncomp-ed system Java classes).
There
are a lot of them loaded when Java VM is created. As for the last
question:
this error message may be a bit misguiding because there's separate
"shared
pool" for Java VM - and this is what is referenced in this particular
error message.
It has [almost] nothing to do with Oracle's shared pool. As I said,
increase
JAVA_POOL_SIZE to at least 35 megs (I am always putting it to 50+) and
bounce the db, then retry export.
--
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.
"Vladimir M. Zakharychev" <bob@dpsp-yes.com> wrote in message
news:a9eb5k$1k5$1@babylon.agtel.net...
Increase your JAVA_POOL_SIZE and retry. Default is usually
inappropriate,
I'd recommend having this value at 50 megs or more.
--
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.
"Ray Teale" <ray@BLAHholly.com.au> wrote in message
news:cspu8.1982$c_3.267928@ozemail.com.au...
Hi All,
I posted this question a while ago but didn't get any replies that I
could
see.
It is still a problem for me so I'm posting again in the hope somebody
can
help.
I was trying to do a full database export (Version 8.1.6.0.0 on Sun
Sparc)
of a fairly small database but got the following error message:
. exporting referential integrity constraints
. exporting synonyms
EXP-00008: ORACLE error 4031 encountered
ORA-04031: unable to allocate 4032 bytes of shared memory ("shared
pool","oracle/aurora/rdbms/DbmsJavaSYS","joxlod: in
ehe","ioc_allocate_pal")
EXP-00000: Export terminated unsuccessfully
.. after all the database users and tables had been exported, just at
the
time the system was ". exporting synonyms."
Well I thought this was a bit strange for such a small database but I
doubled the shared_pool_size, bounced the database and tried again.
Same
problem - it failed at the same spot.
So I tried again - this time the shared pool was 15 times the original
size
but still the export failed at the same spot.
So I checked the synonyms and found there are nearly 10000, most owned
by
PUBLIC and pointing to tables in SYS, and none created by me for my
application.
Couple of questions:
1. What are synonyms in the following format for (examples chosen at
random
below) and do I need them (there are lots) :
SYNONYM_NAME TABLE_NAME
---------------- -----------------------------
-
/10076b23_OraCustomDatumClosur /10076b23_OraCustomDatumClosur
/10322588_HandlerRegistryHelpe /10322588_HandlerRegistryHelpe
/10739900_GenericURLDirContext /10739900_GenericURLDirContext
/1079c94d_NumberConstantData /1079c94d_NumberConstantData
java/security/KeyPairGenerator
java/security/KeyPairGenerator
java/security/MessageDigest
java/security/MessageDigest
2. Would exporting synonyms really put that much of a strain on the
shared
pool? Why?
OK .. so that was about four questions..
Kindest Regards (and apologies for any formatting issues.)
Ray Teale
