-
ORA-4031 running export
Hi all !
Full database export fails with the following errors :
. exporting default and system auditing options
EXP-00008: ORACLE error 4031 encountered
ORA-04031: unable to allocate 4096 bytes of shared memory ("shared pool","BEGIN:1 := "SYS"."DBMS_AQ_E...","PL/SQL MPCODE","BAMIMA: Bam Buffer")
EXP-00083: The previous problem occurred when calling SYS.DBMS_AQ_EXP_QUEUES.audit_sysprivs_exp
There was no changes in the system and everything worked fine until yesterday. Any ideas what is going on ?
Thanks a lot in advance.
-
Hi,
What version of the database are you running? there is a bug relating to this error which appears in 8.1.7 (fixed in 8.1.7.2 and above)
Regards
Jim
Oracle Certified Professional
"Build your reputation by helping other people build theirs."
"Sarcasm may be the lowest form of wit but its still funny"
Click HERE to vist my website!
-
It is the 8.1.7.0.0 release ...
Is there any other solution than migrating to solve the problem ? Because it is quit urgent, we absolutly have to export the database today !
Thanks a lot inf advance for your replies ...
-
How about exporting individual schemas instead of exporting whole database. Though lengthy but I guess it should work...
Sameer
-
Unfortunatly, the full database export is a part of our everyday batch script, so we cannot rewrite it right now and we need to save the whole database and not only the database's schemas (including tablespace definition, roles, database links...).
-
Does anyone has experienced the same problem ?
-
ORA-04031 unable to allocate string bytes of shared memory ("string","string","string","string")
Cause: More shared memory is needed than was allocated in the shared pool.
Action: If the shared pool is out of memory, either use the DBMS_SHARED_POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE.
Does using what the action says help?
Tarry Singh
I'm a JOLE(JavaOracleLinuxEnthusiast)
--- Everything was meant to be---
-
If the issue is related to the bug 1397603 then the following workaround will allow to to perform the export:
add the following to your init.ora and bounce the db
_db_handles_cached = 0
Regards
Jim
Oracle Certified Professional
"Build your reputation by helping other people build theirs."
"Sarcasm may be the lowest form of wit but its still funny"
Click HERE to vist my website!
-
Thanks a lot for your advices ...
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|