[9i] Not enough large pool during export

[Volker Zink]

I have a problem with a 9i.2 database. During export i always get
following error (its in german):

....
.. Kontext-Namespaces werden exportiert
.. Exportieren der Fremdfunktions-Bibliotheksnamen
.. Synonyme vom Typ PUBLIC werden exportiert
EXP-00008: ORACLE-Fehler 4031 gefunden
ORA-04031: 4032 Bytes des gemeinsamen Speichers konnten nicht
zugewiesen werden ("large pool","unknown
object","ioc_make_sub2","ioc_allocate_pal")
EXP-00000: Der Export-Vorgang endete mit Fehlern

The export-command is

exp user/pw@db file=db.exp log=db.log full=y

The first time i saw the error i increased the large pool from 40M to
56M. Didn't help. I increased it even further to 104M
(shutdown/startup after the change included). Still i get the same
error during export. And always at the same line (Synonyme vom Typ
PUBLIC werden exportiert/Synonyms of type PUBLIC are being exported).
Fortunately this is not a production database. I have databases in
production with a large_pool_size of 56M and never had a problem with
export, even if they have large amounts of data compared to the
database which causes the problem.

So whats wrong? I assume its not the large pool.

Thanks

Volker

[Steve]

Vo*********@porabo.ch (Volker Zink) wrote in message news:<fd**************************@posting.google. com>...

I have a problem with a 9i.2 database. During export i always get
following error (its in german):

...
. Kontext-Namespaces werden exportiert
. Exportieren der Fremdfunktions-Bibliotheksnamen
. Synonyme vom Typ PUBLIC werden exportiert
EXP-00008: ORACLE-Fehler 4031 gefunden
ORA-04031: 4032 Bytes des gemeinsamen Speichers konnten nicht
zugewiesen werden ("large pool","unknown
object","ioc_make_sub2","ioc_allocate_pal")
EXP-00000: Der Export-Vorgang endete mit Fehlern

The export-command is

exp user/pw@db file=db.exp log=db.log full=y

The first time i saw the error i increased the large pool from 40M to
56M. Didn't help. I increased it even further to 104M
(shutdown/startup after the change included). Still i get the same
error during export. And always at the same line (Synonyme vom Typ
PUBLIC werden exportiert/Synonyms of type PUBLIC are being exported).
Fortunately this is not a production database. I have databases in
production with a large_pool_size of 56M and never had a problem with
export, even if they have large amounts of data compared to the
database which causes the problem.

So whats wrong? I assume its not the large pool.

Thanks

Volker

Hello Volker,
I found this in some older thread:

- increasing the JAVA_POOL_SIZE to the default one 20 mb

maybe you should try this

Steve

[Volker Zink]

st***********@yahoo.de (Steve) wrote in message news:<70**************************@posting.google. com>...

Vo*********@porabo.ch (Volker Zink) wrote in message news:<fd**************************@posting.google. com>...

I have a problem with a 9i.2 database. During export i always get
following error (its in german):

...
. Kontext-Namespaces werden exportiert
. Exportieren der Fremdfunktions-Bibliotheksnamen
. Synonyme vom Typ PUBLIC werden exportiert
EXP-00008: ORACLE-Fehler 4031 gefunden
ORA-04031: 4032 Bytes des gemeinsamen Speichers konnten nicht
zugewiesen werden ("large pool","unknown
object","ioc_make_sub2","ioc_allocate_pal")
EXP-00000: Der Export-Vorgang endete mit Fehlern

The export-command is

exp user/pw@db file=db.exp log=db.log full=y

The first time i saw the error i increased the large pool from 40M to
56M. Didn't help. I increased it even further to 104M
(shutdown/startup after the change included). Still i get the same
error during export. And always at the same line (Synonyme vom Typ
PUBLIC werden exportiert/Synonyms of type PUBLIC are being exported).
Fortunately this is not a production database. I have databases in
production with a large_pool_size of 56M and never had a problem with
export, even if they have large amounts of data compared to the
database which causes the problem.

So whats wrong? I assume its not the large pool.

Thanks

Volker

Hello Volker,
I found this in some older thread:

- increasing the JAVA_POOL_SIZE to the default one 20 mb

maybe you should try this

Steve

That did the trick.

Thanks.

Volker