Expdp error ORA-39095

Hi
i m new to expdp i used to start to use expdp recently from exp.
since it is having so many features within that.
want to know some thing like abt the err:ORA-39095
when i searched in google what they suggested to use filesize or some suggest to give dumpfile=1.dmp ,2.dmp,3.dmp like that. and some suggested to use %U.dmp
so i m totally confusing what its exact resolution of this error? and kindly suggest me to how to proceed
i think i m not well understoodl properly and then i have given parallel=4 then i remove the parallel parameter now backup happened so can anybody explain how parallel and dumpfile will works whether one parallel processes start to write one dumpfile like that or what?
and also morning i have taken schema exp the dumpfile size 105MB . but afternoon by using expdp its splits upto 4 .dmp file 1.dmp, 2.dmp,3.dmp like that so each and every file is having around 40MB.
what these files will do and suppose if i want to restore how can i restore by using these many dumpfiles ?
pls advise i think these all are basic abt expdp but struggling need some help or some docs with examples.
Thanks,
M.Murali..

1- You can use the dynamic format (i.e dumpfile=full_%U.dmp) :
The 'wildcard' specification for the dump file can expand up to 99 files.
If 99 files have been generated before the export has completed, it will again return the ORA-39095 error.
2- If this is yet not enough and more files are needed, a workaround would be to speficy a bigger 'filesize' parameter.
3- If this is inconvenient, another option is to use this syntax:
dumpfile=fullexp%U.dmp, fullexp2_%U.dmp, fullexp3_%U.dmp
which can expand up to 3*99 files.
If encountering problems containing the dump in a single directory using this solution, you may prefer
this syntax:
dumpfile=dmpdir1:fullexp1_%U.dmp, dmpdir2:fullexp2_%U.dmp, dmpdir3:fullexp3_U.dmp
(assuming the 3 directory objects listed above had been already created first).
also here are some links to get ur started
http://www.oracle-base.com/articles/10g/OracleDataPump10g.php
http://www.orafaq.com/wiki/Datapump

Similar Messages

EXPDP error - ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOA

Greetings All,
Oracle 11g (11.2.0.0) on Windows 2008 R2
I am getting the error below during a schema export of just 1 particular schema. Other schema expdp’s don’t encounter this problem.
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [REF_CONSTRAINT:"CM_MASTER"."PPY_PEN_FK"]
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8165
----- PL/SQL Call Stack -----
object      line object
handle    number name
000000047B38A000     18990 package body SYS.KUPW$WORKER
000000047B38A000      8192 package body SYS.KUPW$WORKER
000000047B38A000      2823 package body SYS.KUPW$WORKER
000000047B38A000      8847 package body SYS.KUPW$WORKER
000000047B38A000      1649 package body SYS.KUPW$WORKER
000000047A576CD0         2 anonymous block
Job "CM_MASTER"."EXP_CM_MASTER" stopped due to fatal error at 17:11:30I have deleted the identified constraint, but then errors out again on another constraint.
I have found a tentative resolution for the ORA-39126 error (delete database stats, then gather database stats) but have not done so yet.
I have tried deleting the statistics for just the schema (cm_master), and then re-gathered stats for the same schema. Still get the error.
I am concerned about the ORA-04063: package body “XDB.DBMS_XDBUTIL_INT” has errors.
I have unlocked and set new password for the XDB user, but am not able to logon as XDB to re-compile the package body in question.
We had some maintenance applied over the weekend that “revoked execute from public” on the following packages:
dbms_datapump
dbms_crypto
dbms_crypto_toolkit
dbms_java_test
dbms_random
dbms_sql
utl_file
utl_http
utl_mail
utl_smtp
utl_tcpThe user performing the export with the problem (cm_master) was then granted execute back on the following packages:
dbms_datapump
dbms_crypto
dbms_random
dbms_sql
utl_file
utl_http
utl_mail
(not: dbms_crypto_toolkit, dbms_java_test, utl_smtp, utl_tcp,)Other schemas were granted execute on the following packages and are NOT having expdp problems:
dbms_datapump
dbms_sql
utl_file
utl_http
utl_mail
(not: dbms_crypto, dbms_crypto_toolkit, dbms_random, utl_smtp, utl_tcp )I don't think the public revokes are causing this error because the "Other schemas" do not have this error and were not specifically granted back all of the public revokes that cm_master received back.
I appreciate any suggestions.
Thanks for your time,
Bob
Edited by: Snyds on Jun 5, 2012 10:03 AM

rjamya,
I checked dba_registry, all 18 rows returned are VALID.
I attempted to compile the package body identified in the error messages:
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errorswith
alter package xdb.dbms_xdbutil_int compile body;I got thje following results
Error starting at line 60 in command:
alter package xdb.dbms_xdbutil_int compile body
Error report:
SQL Command: package XDB.DBMS_XDBUTIL_INT
Failed: ORA-24344: success with compilation error
24344. 00000 - "success with compilation error"
*Cause:    A sql/plsql compilation error occurred.
*Action:   Return OCI_SUCCESS_WITH_INFO along with the error code
package XDB.DBMS_XDBUTIL_INT altered.Any other suggestions regarding how to resolve errors in the XDB.DBMS_ packages?
I also tried granting CM_MASTER execute on the packages that I revoked execute to PUBLIC on, with no effect.
I tried “exclude=REF_CONSTRAINT” on the export, the problem seemed to move to the next section:
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 96.31 MB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [PACKAGE_BODY:"CM_MASTER"."SR_MAINTENANCE"]
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8165
----- PL/SQL Call Stack -----
object      line object
handle    number name
000000047B38A000     18990 package body SYS.KUPW$WORKER
000000047B38A000      8192 package body SYS.KUPW$WORKER
000000047B38A000      2823 package body SYS.KUPW$WORKER
000000047B38A000      8847 package body SYS.KUPW$WORKER
000000047B38A000      1649 package body SYS.KUPW$WORKER
000000047A576CD0         2 anonymous block
Job "CM_MASTER"."EXP_CM_MASTER" stopped due to fatal error at 19:36:23I tried the suggestion from my Google-ing, drop database statistics, then gather database statistics. No effect, same error.
I also tried granting CM_MASTER execute on the packages that I revoked execute to PUBLIC on, with no effect.
Again what seems odd is that I can export other schemas without errors.
Any other suggestions, please.
Thanks,
Bob
Edited by: Snyds on Jun 5, 2012 12:04 PM

Expdp error ORA-31693?

hi
when i use the "expdp" command with the key "query",that make some errors like this:
ORA-31693: Table data object "USER"."USERINFO":"SYS_P4645" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P2485" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P2705" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P2945" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P5405" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P3225" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P4205" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P6845" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P7585" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P3985" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P4925" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P509" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P5145" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P6525" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P2225" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P1481" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P3705" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P7085" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P7325" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P1985" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P3485" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P469" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P449" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P529" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P549" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P11754" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P11561" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P4425" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P409" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P1149" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P11947" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P6205" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P929" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P5665" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P570" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P5945" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P9631" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P11175" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P1845" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P10017" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P10210" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P10403" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P10596" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P10982" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P11368" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P389" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P9245" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P10789" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P789" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P8473" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P8666" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P9438" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P9824" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P1765" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P12140" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P8859" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P9052" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P7887" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P7885" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P12333" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P12719" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P12526" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ORA-31693: Table data object "USER"."USERINFO":"SYS_P12912" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEPOPULATE callout
ORA-29400: data cartridge error
KUP-04038: internal error: kupax-meta1
ths

Pl post details of OS and database versions, along with how exactly you are executing expdp. MOS Doc 467950.1 (ORA-31693 AND ORA-02019 When Using EXPDP Over Network Link With Parallel > 1) might be relevant.
HTH
Srini

ORA-39095: Dump file space has been exhausted

Hello Friends,
DB Version : 10.2.0.4
OS : SUN Solaris 10
We have a server with 10 RAC databases running on it. From 1st node we have a scheduled export job for all the databases. All the databases are using a common script and we are passing parameters (example as below)
/opt/oracle/admin/DBA/dbatools/expdpdb.sh -d w111pr1 (here w111pr1 is the SID)
Out of 10 databases, full export job is working fine for 9 databases. only for 1 database (which i mentioned above), export is failing with below error
ORA-39095: Dump file space has been exhausted: Unable to allocate 16384 bytes
Job "OPS$ORACLE"."SYS_EXPORT_FULL_39" stopped due to fatal error at 00:06:13
After analyzing I found that in the script we are not using '%U' option for dump file which might cause the problem. But if this is the real issue, it should fail for other 9 databases also. But even without '%U' option, it is working for other databases.
One more thing.... all the export backups will run in a difference of 1/2 hour. Do we need anything with OS processes?
Anyone faced this kind of issue earlier? If so please let me know what can be a better way to handle it.
Thanks in advance...
P.S: export is executing fine when issued manually.

what are your dumpfile, parallel and filesize parameter values in the shell script? does the shell script has one size fits all parameter settings? Also are there any other errors? Can you share the expdp command ?
Edited by: rjamya on Jun 7, 2012 4:41 AM

EXPDP got error ORA-39014,ORA-39029 in oracle 10.2.0.4

oracle database = 10.2.0.4
OS= Oracle enterprise linux 4.8
after run expdp file i got the following error:
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31671: Worker process DW01 had an unhandled exception.
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 1352
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 7073
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 2829
ORA-24795: Illegal ROLLBACK attempt made
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 10915
ORA-02354: error in exporting/importing data
ORA-39773: parse of metadata stream faile
how could i solve my problm????
help me

user12189421 wrote:
ulimit -n
131072
lsof | grep oracle | wc -l
2332
cat /proc/sys/fs/file-nr
2520 0 357686In that case you need to check with your system admin.
Error: ORA 447
Text:   fatal error in background process
Cause: One of the background processes completed unexpectedly.
Action: Restart the system.
        Check and, if necessary, correct the problem indicated by the
        background trace file in BACKGROUND_DUMP_DEST.
*** Important: The notes below are for experienced users - See Note:22080.1
Diagnosis:
      - Check the alert log and trace files for all trace files around
     the time of the error. It is common for one trace to point at another
     process. Follow the list until you get a file with a real
     error in it. If unsure collect ALL trace files.
      - If all traces point to a process with no tracefile (Eg: LGWR)
     check whether any new tablespaces or datafiles have been added
     recently
     Check whether sum(number of datafiles +
                       number of redolog files +
                          number of controlfiles)
                is less than
                          (user's unix open file limit. eg. nfile on SUN,
                              maxfile on HP)Regards
Anurag

Oracle 10g expdp fatal error (ORA-39125 & ORA-01801)

Key phrases: ORA-39125 ... DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS] ... date format is too long
Hello,
While performing a routine export (expdp) of schemas in an Oracle 10.2 instance on Linux, a fatal error (ORA-39125) was genereted. A screen capture, including the error messages follows.
Export: Release 10.2.0.1.0 - 64bit Production on Wednesday, 20 May, 2009 15:34:44
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-01801: date format is too long for internal buffer
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.KUPW$WORKER", line 6241
----- PL/SQL Call Stack -----
object line object
handle number name
0x807d2378 14916 package body SYS.KUPW$WORKER
0x807d2378 6300 package body SYS.KUPW$WORKER
0x807d2378 2340 package body SYS.KUPW$WORKER
0x807d2378 6861 package body SYS.KUPW$WORKER
0x807d2378 1262 package body SYS.KUPW$WORKER
0x801d2490 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_13" stopped due to fatal error at 15:34:54
Has anyone run into this problem?
Is it related to an Oracle bug?
Are there fixes/workarounds?
Thanks in advance,
Alan

Hi,
There have been fixes to this area. I don't know if this exact error has been fixed, but getting the latest patchset would be a good place to start.
Thanks
Dean

Expdp with ORA-04063: package body "SYS.DBMS_CUBE_EXP" error

Hi,
I try to use expdp to export all tables from schema BAW, but hit the following error. Oracle version is 11.2.0.2, and the package body "SYS.DBMS_CUBE_EXP" is invalid. Any idea to fix it?
Starting "BAW"."SYS_EXPORT_SCHEMA_01": baw/******** directory=DATA_PUMP_DIR met
rics=yes schemas=baw dumpfile=baw.dmp
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS [
ORA-31642: the following SQL statement fails:
BEGIN "SYS"."DBMS_CUBE_EXP".SCHEMA_CALLOUT(:1,0,1,'11.02.00.02.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 1245
ORA-04063: package body "SYS.DBMS_CUBE_EXP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_CUBE_EXP"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 8353
----- PL/SQL Call Stack -----
object line object
handle number name
7000004c9656fe0 19208 package body SYS.KUPW$WORKER
7000004c9656fe0 8385 package body SYS.KUPW$WORKER
7000004c9656fe0 12748 package body SYS.KUPW$WORKER
7000004c9656fe0 2546 package body SYS.KUPW$WORKER
7000004c9656fe0 9054 package body SYS.KUPW$WORKER
7000004c9656fe0 1688 package body SYS.KUPW$WORKER
7000004c9659720 2 anonymous block
object line object
handle number name
7000004c9656fe0 19208 package body SYS.KUPW$WORKER
7000004c9656fe0 8385 package body SYS.KUPW$WORKER
7000004c9656fe0 12748 package body SYS.KUPW$WORKER
7000004c9656fe0 2546 package body SYS.KUPW$WORKER
7000004c9656fe0 9054 package body SYS.KUPW$WORKER
7000004c9656fe0 1688 package body SYS.KUPW$WORKER
7000004c9659720 2 anonymous block
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS [
ORA-31642: the following SQL statement fails:
BEGIN "SYS"."DBMS_CUBE_EXP".SCHEMA_CALLOUT(:1,0,1,'11.02.00.02.00'); END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 1245
ORA-04063: package body "SYS.DBMS_CUBE_EXP" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_CUBE_EXP"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPW$WORKER", line 8353
----- PL/SQL Call Stack -----
object line object
handle number name
7000004c9656fe0 19208 package body SYS.KUPW$WORKER
7000004c9656fe0 8385 package body SYS.KUPW$WORKER
7000004c9656fe0 12748 package body SYS.KUPW$WORKER
7000004c9656fe0 2546 package body SYS.KUPW$WORKER
7000004c9656fe0 9054 package body SYS.KUPW$WORKER
7000004c9656fe0 1688 package body SYS.KUPW$WORKER
7000004c9659720 2 anonymous block
Job "BAW"."SYS_EXPORT_SCHEMA_01" stopped due to fatal error at 16:07:26
e

The simple solution to this problem is, and its working perfectly with me on 11gR2 resolving the subject error.
To avoid this problem, perform relational exports excluding OLAP's Analytic Workspaces.
1) Remove workspace package from export:
a. Connect sys/password as sysdba
b. create table sys.exppkgact$_backup as select * from sys.exppkgact$;
(Backup package before deleting it)
c. delete from sys.exppkgact$ where package = 'DBMS_CUBE_EXP' and schema= 'SYS';
d. commit;
4) Run the export.

Expdp fails with error ORA-39006: internal error writing on a windows share

Hi!
I need to get the following configuration working:
Linux Server (CentOS 5 32 bits) with Oracle 11.2.0.1.0
Windows Server 2003 SP2 32 bits.
On the windows server I have created a user called oracle, who is member of oinstall and dba groups. (On Linux username, and group membership is the same).
After that, I share a directory on D:\data_pump (I gave the full control of directory to oracle user). I mount the windows share on my linux as follows:
mount -t cifs //winserver/data_pump /u04/oradata/data_pump -o user=oracle,password="pass",uid=oracle,gid=oinstall
As the linux oracle user I'm capable of create and edit files, but:
I connect to my database, create the directory called DATA_PUMP pointing to my cifs mount point, and, after that, I issue the following expdp sentence:
expdp system DIRECTORY=DATA_PUMP DUMPFILE=test4.dmp LOGFILE=test4.log FULL=yes
And I get the following error:
ORA-39006: internal error
Looking at expdp log I found the following information:
ORA-39097: Data Pump job encountered unexpected error -31643
ORA-39065: unexpected master process exception in FILE
ORA-31643: unable to close dump file "/u04/oradata/data_pump/gaston4.dmp"
ORA-19510: failed to set size of 1 blocks for file "/u04/oradata/data_pump/gaston4.dmp" (block size=4096)
ORA-27045: unable to close the file
Linux Error: 5: Input/output error
Additional information: 4
Do you have any suggestions?
Thanks in advance.

Hi, see metalink:
Bug 8313127: EXPDP EXPORT TO CIFS MOUNT ON WINDOWS FROM LINUX FAILS
http://kr.forums.oracle.com/forums/thread.jspa?threadID=923398

Expdp error anyone have an idea on how to fix this?

I'm trying to get an export of a database that has encrypted columns. Exp really isn't a good option I'd have to unencrypt the columns first everytime.
First I create the directory D:\DPDUMP and give Everyone SERVICE and SYSTEM full rights to the directory. Oracle runs as the Local System account.
Created new user myuser that has the role DBA with EXP_FULL_DATABASE etc.
Made directory object.
CREATE DIRECTORY dpump_dir_01 AS 'D:\DPDUMP';
grant read, write on directory dpump_dir_01 to myuser;
Run expdp as myuser with following PARFILE entries just testing on the tables that are giving me problems.
DIRECTORY=dpump_dir_01
LOGFILE=Encryptest.log
DUMPFILE=Encryptest.dmp
FULL=N
encryption_password=********
TABLES=MYBANK.CARDAGREEMENT
CONTENT=ALL
get errors
ORA-39006: internal error
ORA-39213: Metadata processing is not available
I've added USERID="/ as sysdba" to the PARFILE.
I've tried it to the default DATA_PUMP_DIR after giving read write to that with the same error. expdp TABLES=MYBANK.CARDAGREEMENT.
No matter what I do I get this error. So far what I've seen is a Directory permissions issue normally causes it and granting access fixes it but I'm having no luck at all.

Here the error definition message, have you try the recommanded action ?
ORA-39213: Metadata processing is not available
Cause: The Data Pump could not use the Metadata API. Typically, this is caused by the XSL stylesheets not being set up properly.
Action: Connect AS SYSDBA and execute dbms_metadata_util.load_stylesheets to reload the stylesheets.
Nicolas.

EXPDP Error in Oracle 11.2.0.1.0

Hello Team,
I have a problem in executing expdp/impdp in oracle version 11.2.0.1.0. Following is the error output. Traditional exp/imp is working fine.
Note: command executed on Oracle Linux on VMware
[oracle1@rac1 test]$ expdp
Export: Release 11.2.0.1.0 - Production on Mon Aug 12 15:29:39 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Username: system
Password:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORA-31626: job does not exist
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
ORA-06512: at "SYS.KUPV$FT", line 991
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
Regards,

Hello DK2010,
=======================================================================================================
SQL> set lines 100
SQL> set pagesize 200
SQL> /
OWNER                          OBJECT_TYPE
OBJECT_NAME
OBJECT_ID STATUS
SYS                            PACKAGE
DBMS_INTERNAL_LOGSTDBY
      5067 VALID
SYS                            PACKAGE BODY
DBMS_INTERNAL_LOGSTDBY
     10780 INVALID
===================================================================================================
UTLRP.SQL output:
====================================================================================================
SQL> @utlrp.sql
TIMESTAMP
COMP_TIMESTAMP UTLRP_BGN 2013-08-12 16:03:24
DOC>   The following PL/SQL block invokes UTL_RECOMP to recompile invalid
DOC>   objects in the database. Recompilation time is proportional to the
DOC>   number of invalid objects in the database, so this command may take
DOC>   a long time to execute on a database with a large number of invalid
DOC>   objects.
DOC>
DOC>   Use the following queries to track recompilation progress:
DOC>
DOC>   1. Query returning the number of invalid objects remaining. This
DOC>      number should decrease with time.
DOC>         SELECT COUNT(*) FROM obj$ WHERE status IN (4, 5, 6);
DOC>
DOC>   2. Query returning the number of objects compiled so far. This number
DOC>      should increase with time.
DOC>         SELECT COUNT(*) FROM UTL_RECOMP_COMPILED;
DOC>
DOC>   This script automatically chooses serial or parallel recompilation
DOC>   based on the number of CPUs available (parameter cpu_count) multiplied
DOC>   by the number of threads per CPU (parameter parallel_threads_per_cpu).
DOC>   On RAC, this number is added across all RAC nodes.
DOC>
DOC>   UTL_RECOMP uses DBMS_SCHEDULER to create jobs for parallel
DOC>   recompilation. Jobs are created without instance affinity so that they
DOC>   can migrate across RAC nodes. Use the following queries to verify
DOC>   whether UTL_RECOMP jobs are being created and run correctly:
DOC>
DOC>   1. Query showing jobs created by UTL_RECOMP
DOC>         SELECT job_name FROM dba_scheduler_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>
DOC>   2. Query showing UTL_RECOMP jobs that are running
DOC>         SELECT job_name FROM dba_scheduler_running_jobs
DOC>            WHERE job_name like 'UTL_RECOMP_SLAVE_%';
DOC>#
DECLARE
ERROR at line 1:
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
ORA-06512: at "SYS.UTL_RECOMP", line 781
ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_INTERNAL_LOGSTDBY"
ORA-06512: at line 4
TIMESTAMP
COMP_TIMESTAMP UTLRP_END 2013-08-12 16:03:25
DOC> The following query reports the number of objects that have compiled
DOC> with errors (objects that compile with errors have status set to 3 in
DOC> obj$). If the number is higher than expected, please examine the error
DOC> messages reported with each object (using SHOW ERRORS) to see if they
DOC> point to system misconfiguration or resource constraints that must be
DOC> fixed before attempting to recompile these objects.
DOC>#
OBJECTS WITH ERRORS
                 13
DOC> The following query reports the number of errors caught during
DOC> recompilation. If this number is non-zero, please query the error
DOC> messages in the table UTL_RECOMP_ERRORS to see if any of these errors
DOC> are due to misconfiguration or resource constraints that must be
DOC> fixed before objects can compile successfully.
DOC>#
ERRORS DURING RECOMPILATION
                          0
PL/SQL procedure successfully completed.
SQL> SELECT owner, object_type, object_name, object_id, status FROM SYS.dba_objects where object_name = 'DBMS_INTERNAL_LOGSTDBY';
OWNER                          OBJECT_TYPE
OBJECT_NAME
OBJECT_ID STATUS
SYS                            PACKAGE
DBMS_INTERNAL_LOGSTDBY
      5067 VALID
SYS                            PACKAGE BODY
DBMS_INTERNAL_LOGSTDBY
     10780 INVALID
==================================================
SELECT owner,object_type,object_name,status FROM dba_objects WHERE status = 'INVALID' ORDER BY owner, object_type, object_name;SQL> SQL>
OWNER                          OBJECT_TYPE         OBJECT_NAME                    STATUS
DBSNMP                         PACKAGE             BSLN                           INVALID
DBSNMP                         PACKAGE             BSLN_INTERNAL                  INVALID
DBSNMP                         PACKAGE BODY        BSLN                           INVALID
DBSNMP                         PACKAGE BODY        BSLN_INTERNAL                  INVALID
DBSNMP                         SYNONYM             MGMT_BSLN                      INVALID
PUBLIC                         SYNONYM             DBA_LOGSTDBY_LOG               INVALID
PUBLIC                         SYNONYM             DBMS_ADVISOR                   INVALID
PUBLIC                         SYNONYM             DBMS_SQLPA                     INVALID
PUBLIC                         SYNONYM             DBMS_SQLTUNE                   INVALID
SYS                            FUNCTION            LOGSTDBY$TABF                  INVALID
SYS                            FUNCTION            LOGSTDBY$UTABF                 INVALID
SYS                            PACKAGE             DBMS_ADVISOR                   INVALID
SYS                            PACKAGE             DBMS_SQLDIAG_INTERNAL          INVALID
SYS                            PACKAGE             DBMS_SQLPA                     INVALID
SYS                            PACKAGE             DBMS_SQLTUNE                   INVALID
SYS                            PACKAGE             DBMS_SQLTUNE_INTERNAL          INVALID
SYS                            PACKAGE             PRVT_ADVISOR                   INVALID
SYS                            PACKAGE BODY        AS_REPLAY                      INVALID
SYS                            PACKAGE BODY        DBMS_ADDM                      INVALID
SYS                            PACKAGE BODY        DBMS_ADVISOR                   INVALID
SYS                            PACKAGE BODY        DBMS_APPLY_ERROR               INVALID
SYS                            PACKAGE BODY        DBMS_ARCH_PROVIDER_INTL        INVALID
SYS                            PACKAGE BODY        DBMS_ASH_INTERNAL              INVALID
SYS                            PACKAGE BODY        DBMS_AUTOTASK_PRVT             INVALID
SYS                            PACKAGE BODY        DBMS_AUTO_TASK_EXPORT          INVALID
SYS                            PACKAGE BODY        DBMS_CAPTURE_SWITCH_ADM        INVALID
SYS                            PACKAGE BODY        DBMS_CAPTURE_SWITCH_INTERNAL   INVALID
SYS                            PACKAGE BODY        DBMS_COMPRESSION               INVALID
SYS                            PACKAGE BODY        DBMS_DBFS_CONTENT_ADMIN        INVALID
SYS                            PACKAGE BODY        DBMS_DBFS_HS                   INVALID
SYS                            PACKAGE BODY        DBMS_FEATURE_USAGE             INVALID
SYS                            PACKAGE BODY        DBMS_FEATURE_USAGE_INTERNAL    INVALID
SYS                            PACKAGE BODY        DBMS_INTERNAL_LOGSTDBY         INVALID
SYS                            PACKAGE BODY        DBMS_ISCHED                    INVALID
SYS                            PACKAGE BODY        DBMS_LOGREP_EXP                INVALID
SYS                            PACKAGE BODY        DBMS_LOGSTDBY                  INVALID
SYS                            PACKAGE BODY        DBMS_MANAGEMENT_PACKS          INVALID
SYS                            PACKAGE BODY        DBMS_PROPAGATION_INTERNAL      INVALID
SYS                            PACKAGE BODY        DBMS_REPORT                    INVALID
SYS                            PACKAGE BODY        DBMS_SERVER_ALERT              INVALID
SYS                            PACKAGE BODY        DBMS_SERVER_ALERT_PRVT         INVALID
SYS                            PACKAGE BODY        DBMS_SMB                       INVALID
SYS                            PACKAGE BODY        DBMS_SMB_INTERNAL              INVALID
SYS                            PACKAGE BODY        DBMS_SPACE                     INVALID
SYS                            PACKAGE BODY        DBMS_SPM                       INVALID
SYS                            PACKAGE BODY        DBMS_SPM_INTERNAL              INVALID
SYS                            PACKAGE BODY        DBMS_SQLDIAG                   INVALID
SYS                            PACKAGE BODY        DBMS_SQLDIAG_INTERNAL          INVALID
SYS                            PACKAGE BODY        DBMS_SQLPA                     INVALID
SYS                            PACKAGE BODY        DBMS_SQLTCB_INTERNAL           INVALID
SYS                            PACKAGE BODY        DBMS_SQLTUNE                   INVALID
SYS                            PACKAGE BODY        DBMS_SQLTUNE_INTERNAL          INVALID
SYS                            PACKAGE BODY        DBMS_SQLTUNE_UTIL1             INVALID
SYS                            PACKAGE BODY        DBMS_SQLTUNE_UTIL2             INVALID
SYS                            PACKAGE BODY        DBMS_STATS                     INVALID
SYS                            PACKAGE BODY        DBMS_STATS_INTERNAL            INVALID
SYS                            PACKAGE BODY        DBMS_STREAMS_ADM               INVALID
SYS                            PACKAGE BODY        DBMS_STREAMS_ADM_UTL           INVALID
SYS                            PACKAGE BODY        DBMS_STREAMS_AUTO_INT          INVALID
SYS                            PACKAGE BODY        DBMS_STREAMS_SM                INVALID
SYS                            PACKAGE BODY        DBMS_SWRF_INTERNAL             INVALID
SYS                            PACKAGE BODY        DBMS_SWRF_REPORT_INTERNAL      INVALID
SYS                            PACKAGE BODY        DBMS_UNDO_ADV                  INVALID
SYS                            PACKAGE BODY        DBMS_WORKLOAD_CAPTURE          INVALID
SYS                            PACKAGE BODY        DBMS_WORKLOAD_REPLAY           INVALID
SYS                            PACKAGE BODY        DBMS_WORKLOAD_REPOSITORY       INVALID
SYS                            PACKAGE BODY        DBMS_WRR_INTERNAL              INVALID
SYS                            PACKAGE BODY        DBMS_XPLAN                     INVALID
SYS                            PACKAGE BODY        HM_SQLTK_INTERNAL              INVALID
SYS                            PACKAGE BODY        LOGMNR_DICT_CACHE              INVALID
SYS                            PACKAGE BODY        PRVT_ACCESS_ADVISOR            INVALID
SYS                            PACKAGE BODY        PRVT_ADVISOR                   INVALID
SYS                            PACKAGE BODY        PRVT_COMPRESSION               INVALID
SYS                            PACKAGE BODY        PRVT_HDM                       INVALID
SYS                            PACKAGE BODY        PRVT_PARTREC_NOPRIV            INVALID
SYS                            PACKAGE BODY        PRVT_REPORT_TAGS               INVALID
SYS                            PACKAGE BODY        PRVT_SQLADV_INFRA              INVALID
SYS                            PACKAGE BODY        PRVT_SQLPA                     INVALID
SYS                            PACKAGE BODY        PRVT_SQLPROF_INFRA             INVALID
SYS                            PACKAGE BODY        PRVT_SQLSET_INFRA              INVALID
SYS                            PACKAGE BODY        PRVT_SYS_TUNE_MVIEW            INVALID
SYS                            PACKAGE BODY        PRVT_TUNE_MVIEW                INVALID
SYS                            PACKAGE BODY        PRVT_WORKLOAD                  INVALID
SYS                            PACKAGE BODY        PRVT_WORKLOAD_NOPRIV           INVALID
SYS                            PROCEDURE           DBMS_FEATURE_AUM               INVALID
SYS                            PROCEDURE           DBMS_FEATURE_AUTOSTA           INVALID
SYS                            PROCEDURE           DBMS_FEATURE_AWR               INVALID
SYS                            PROCEDURE           DBMS_FEATURE_REGISTER_ALLFEAT INVALID
SYS                            PROCEDURE           DBMS_FEATURE_SEGADV_USER       INVALID
SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES1        INVALID
SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES2        INVALID
SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES3        INVALID
SYS                            PROCEDURE           DBMS_FEATURE_UTILITIES4        INVALID
SYS                            PROCEDURE           DBMS_FEATURE_WCR_CAPTURE       INVALID
SYS                            PROCEDURE           DBMS_FEATURE_WCR_REPLAY        INVALID
SYS                            PROCEDURE           LOGMNR_KRVRDA_TEST_APPLY       INVALID
SYS                            TYPE                SCHEDULER$_REMOTE_ARG          INVALID
SYS                            TYPE                SCHEDULER$_REMOTE_ARG_LIST     INVALID
SYS                            TYPE                SCHEDULER$_REMOTE_DB_JOB_INFO INVALID
SYS                            TYPE BODY           WRI$_ADV_ABSTRACT_T            INVALID
SYS                            TYPE BODY           WRI$_ADV_COMPRESSION_T         INVALID
SYS                            TYPE BODY           WRI$_ADV_HDM_T                 INVALID
SYS                            TYPE BODY           WRI$_ADV_OBJSPACE_TREND_T      INVALID
SYS                            TYPE BODY           WRI$_ADV_SQLACCESS_ADV         INVALID
SYS                            TYPE BODY           WRI$_ADV_SQLTUNE               INVALID
SYS                            TYPE BODY           WRI$_ADV_TUNEMVIEW_ADV         INVALID
SYS                            TYPE BODY           WRI$_REPT_PLAN_DIFF            INVALID
SYS                            TYPE BODY           WRI$_REPT_SQLMONITOR           INVALID
SYS                            TYPE BODY           WRI$_REPT_SQLPI                INVALID
SYS                            TYPE BODY           WRI$_REPT_SQLT                 INVALID
SYS                            VIEW                AQ$AQ_PROP_TABLE_R             INVALID
SYS                            VIEW                AQ$SCHEDULER$_EVENT_QTAB_R     INVALID
SYS                            VIEW                AQ$SCHEDULER$_REMDB_JOBQTAB    INVALID
SYS                            VIEW                AQ$SCHEDULER$_REMDB_JOBQTAB_R INVALID
SYS                            VIEW                AQ$SCHEDULER_FILEWATCHER_QT_R INVALID
SYS                            VIEW                AQ$_AQ$_MEM_MC_F               INVALID
SYS                            VIEW                AQ$_AQ_PROP_TABLE_F            INVALID
SYS                            VIEW                AQ$_SCHEDULER$_EVENT_QTAB_F    INVALID
SYS                            VIEW                AQ$_SCHEDULER$_REMDB_JOBQTAB_F INVALID
SYS                            VIEW                AQ$_SCHEDULER_FILEWATCHER_QT_F INVALID
SYS                            VIEW                DBA_LOGSTDBY_LOG               INVALID
121 rows selected.
=================================================================================================================
How do i fix this invalid sys objects.
Regards,

[help]oracle 10.2.0.1 expdp error

when i try to use exp to export all the data under an user account, here comes some error of failure in export some table which not supported by exp
EXP-00104: datatype (BINARY_FLOAT) of column GP in table XXXX.ADAA_DATA is not supported, table will not be exported
so I try to use new feature of 10g expdp,but another errors goes up again
I get on command line:
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_EXPORT_SCHEMA_01 for user TEST
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT", line 1193
ORA-39062: error creating master process DM00
ORA-39107: Master process DM00 violated startup protocol. Master error:
ORA-06533: Subscript beyond count
and in the trace file,here comes some message is similar to the following:
Oracle process number: 24
Windows thread id: 904, image: ORACLE.EXE (DM00)
**** SERVICE NAME:(SYS$USERS) 2006-07-18 22:20:59.689*
**** SESSION ID:(146.18) 2006-07-18 22:20:59.689*
KUPM: Error detected by MCP
KUPM: ORA-39097: Data Pump job encountered unexpected error -44002
KUPM: ORA-39065: unexpected master process exception in MAIN
KUPM: ORA-44002: invalid object name
KUPM:     ORA-06512: at "SYS.DBMS_ASSERT", line 283
KUPM:     ORA-06512: at "SYS.KUPM$MCP", line 484
KUPM:--------------------------------------------------------------------------------
PL/SQL Call Stack--------------------------------------------------------------------------------
KUPM:       object      line object
KUPM:       handle    number name
KUPM:     1CE0FC44     10592 package body SYS.KUPM$MCP
KUPM:     1CE0FC44       917 package body SYS.KUPM$MCP
KUPM:     1CCF8CAC         2 anonymous block
KUPM: In RESPOND_TO_START
KUPM: Killing workers on fatal exception...
KUPM: In check_workers...
kupprdp: Error 6533 detected in master process DM00.
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-31666: Master process DM00 had an unhandled exception.
ORA-06533: Subscript beyond count
ORA-06512: at "SYS.KUPM$MCP", line 8636
ORA-06512: at "SYS.KUPM$MCP", line 5794
ORA-06512: at "SYS.KUPM$MCP", line 936
ORA-06512: at line 2

I got some help from metalink and my version is 10.2.0.1 based on win2003 server 32bit
ORA-44002 error raised when using the Data Pump based export utility [ID 603469.1]
In this Document
Symptoms
Cause
Solution
Applies to:
Oracle Server - Enterprise Edition - Version: 10.2.0.3
This problem can occur on any platform.
Symptoms
-- Problem Statement:
The following errors are reported while performing a Data Pump based export operation.
KUPM: Error detected by MCP
KUPM: ORA-39097: Data Pump job encountered unexpected error -44002
KUPM: ORA-39065: unexpected master process exception in MAIN
KUPM: ORA-44002: invalid object name
KUPM: ORA-06512: at "SYS.DBMS_ASSERT", line 283
KUPM: ORA-06512: at "SYS.KUPM$MCP", line 484
KUPM: ----- PL/SQL Call Stack -----
KUPM: object line object
KUPM: handle number name
KUPM: 39f4f8298 10619 package body SYS.KUPM$MCP
KUPM: 39f4f8298 917 package body SYS.KUPM$MCP
KUPM: 39f4fbe80 2 anonymous block
KUPM: In RESPOND_TO_START
KUPM: Killing workers on fatal exception...
KUPM: In check_workers...
kupprdp: Error 6533 detected in master process DM00.
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-31666: Master process DM00 had an unhandled exception.
ORA-06533: Subscript beyond count
ORA-06512: at "SYS.KUPM$MCP", line 8677
ORA-06512: at "SYS.KUPM$MCP", line 5832
ORA-06512: at "SYS.KUPM$MCP", line 936
ORA-06512: at line 2
Cause
A synonym with a name that matched an Oracle RDBMS reserved name was found to exist.
After the customer found out that such a synonym existed and they removed it, the export ran
successfully.
Solution
-- To implement the solution, please execute the following steps::
Avoid using object names that match reserved names of the Oracle RDBMS software release.
but the solution makes me confuse...what to do?
"Avoid using object names that match reserved names of the Oracle RDBMS software release" ?? I don't have synonym
Edited by: gunsnroses_xjapan on Aug 3, 2010 1:31 AM

EXPDP error for 11gR2

Hi,
All of the sudden today I have been getting expdp errors only just one schema that I try to export, whereas all my other run perfectly fine.
     Oracle Datapump export for ODC on 120228 at 1203
     Building parameter files for ODC
     EXPORT Parameters ----
     schemas=iims
     content=all
     flashback_time='2012/02/28 12:03:06'
     parallel=4
     job_name=iims_120228_1203
     directory=DATA_PUMP_DIR
     dumpfile=ODC.iims.120228_1203.dp_export_file%U.dmp
     logfile=ODC.iims.120228_1203.dp_export.log
     filesize=5G
     Export: Release 11.2.0.3.0 - Production on Tue Feb 28 12:03:07 2012
     Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
     Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
     With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,
     Data Mining and Real Application Testing options
     Starting "GNW_DBMAINT"."IIMS_120228_1203": GNW_DBMAINT/********@ODC
parfile=/dba/prod/scripts/infiles/ODC.iims.120228_1203.dp_export.par
     Estimate in progress using BLOCKS method...
     Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
     Total estimation using BLOCKS method: 17.96 GB
     Processing object type SCHEMA_EXPORT/USER
     Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
     Processing object type SCHEMA_EXPORT/ROLE_GRANT
     Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
     Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
     Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
     Processing object type SCHEMA_EXPORT/TYPE/GRANT/OWNER_GRANT/OBJECT_GRANT
     Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
     Processing object type SCHEMA_EXPORT/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
     Processing object type SCHEMA_EXPORT/TABLE/TABLE
     Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
     Processing object type SCHEMA_EXPORT/TABLE/COMMENT
     Processing object type SCHEMA_EXPORT/TABLE/AUDIT_OBJ
     Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
     Processing object type SCHEMA_EXPORT/PACKAGE/GRANT/OWNER_GRANT/OBJECT_GRANT
     Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
     Processing object type SCHEMA_EXPORT/FUNCTION/GRANT/OWNER_GRANT/OBJECT_GRANT
     Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
     Processing object type SCHEMA_EXPORT/PROCEDURE/GRANT/OWNER_GRANT/OBJECT_GRANT
     Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
     Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
     Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
     Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
     Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_INDEX/INDEX
     Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
     Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
     Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_INDEX/INDEX_STATISTICS
     Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
     . . exported "IIMS"."IIMS_GLC_INTERFACE_CS"          1.833 GB 6443778 rows
     Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
     Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
     Processing object type SCHEMA_EXPORT/MATERIALIZED_VIEW
     Processing object type SCHEMA_EXPORT/REFRESH_GROUP
     . . exported "IIMS"."T_ACCOUNTING_TRN_DETAIL"        1.060 GB 7779037 rows
ORA-39097: Data Pump job encountered unexpected error -12801
ORA-39065: unexpected master process exception in MAIN
ORA-12801: error signaled in parallel query server PZ99, instance dd0152alyn:ODC1 (1)
ORA-01460: unimplemented or unreasonable conversion requested
     Job "GNW_DBMAINT"."IIMS_120228_1203" stopped due to fatal error at 12:08:14Been trying to google this one but can't really seems to find anything.
Any help? Version 11.2.0.2 on Solaris 5.10, 2 node RAC

I tried that , did not work.
expdp abansal6dba DIRECTORY='DP_EXP_DIR' schemas='oltp_user' cluster=n dumpfile='oltp_user0417.dump' logfile='oltp_useroltp_user0417.log'
ORA-39065: unexpected master process exception in MAIN
ORA-12801: error signaled in parallel query server PZ99, instance prod-rac12.wp.cl.datapipe.net:WNPPROD2 (2)
ORA-01460: unimplemented or unreasonable conversion requested
Job "ABANSAL6DBA"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at 12:12:15
Bug 13350027: DATAPUMP TERMINATED DUE TO ORA-1460 does not have solution either.

DATA-PUMP ERROR: ORA-39070 Database on Linux, Client on Win 2008

Hi,
i want to make a datapump export from client Windows 2008. I define dpdir as 'C:\DPDIR'.
While making expdp
expdp login\pass@ora directory=dpdir dumpfile=dump.dmp logfile=log.log full=y
i get those errors
ORA-39002:niepoprawna operacja
ORA-39070:nie mozna otworzyc pliku dziennik
ORA-29283:niepoprawna operacja na pliku
ORA-06512:przy "sys.utl_file", linia 536
ORA-29283:niepoprawna operacja na pliku
(decriptions in polish)
I found out, that datapump is saving files to the Linux Server (where database is). When i define 'C:\DPDIR' it doesn't recognize it because there is no such directory on Linux.
How can I save datapump export dumpfile on Windows?

tstefanski wrote:
Hi,
i want to make a datapump export from client Windows 2008. I define dpdir as 'C:\DPDIR'.
While making expdp
expdp login\pass@ora directory=dpdir dumpfile=dump.dmp logfile=log.log full=y
i get those errors
ORA-39002:niepoprawna operacja
ORA-39070:nie mozna otworzyc pliku dziennik
ORA-29283:niepoprawna operacja na pliku
ORA-06512:przy "sys.utl_file", linia 536
ORA-29283:niepoprawna operacja na pliku
(decriptions in polish)
I found out, that datapump is saving files to the Linux Server (where database is). When i define 'C:\DPDIR' it doesn't recognize it because there is no such directory on Linux.
How can I save datapump export dumpfile on Windows?
>Hi,
i want to make a datapump export from client Windows 2008. I define dpdir as 'C:\DPDIR'.
While making expdp
expdp login\pass@ora directory=dpdir dumpfile=dump.dmp logfile=log.log full=y
i get those errors
ORA-39002:niepoprawna operacja
ORA-39070:nie mozna otworzyc pliku dziennik
ORA-29283:niepoprawna operacja na pliku
ORA-06512:przy "sys.utl_file", linia 536
ORA-29283:niepoprawna operacja na pliku
(decriptions in polish)
I found out, that datapump is saving files to the Linux Server (where database is). When i define 'C:\DPDIR' it doesn't recognize it because there is no such directory on Linux.
How can I save datapump export dumpfile on Windows?
expdp can only create dump file on DB Server system itself.

IMPDP Errors ORA-39083 ORA-01918

Oracle Database 10.2
OS IBM AIX
Hi
I have to do one datapump import into one database. The source database is different.
The dumpfile contains 3 different schemas. And I need to import into one schema with a different name.
For example, Export dump contains AB, CD and EF.
I need to import only EF user into new database and it should become MN.
I have used remap_schema=EF:MN
The following is the import parfile.
userid='/ as sysdba'
directory=DF_DUMP
dumpfile=AMRC%U.dmp
remap_schema=EF:MN
remap_tablespace=RM100:TS100
remap_tablespace=DATA100:DATA300
job_name=MNIMPORT
logfile=MNIMPORT.log
parallel=4
I have started the import. But I see the below errors
ORA-39083: Object type TABLE failed to create with error:
ORA-01918: user 'AB' does not exist
Failing sql is:
CREATE TABLE
After this, import of MN has begun.
How to resolve the below error ? What is the reason for this error ? What changes are needed in parfile ?

Three errors
- You didn't look up the error messages in the online documentation.
- impdp by default imports the entire file (Full=y). You need the SCHEMAS= clause
- expdp and impdp shouldn't be run as SYS
All in all you could have found the answer very easily in the online documentation.
Please avoid asking redundant questions in the future.
Sybrand Bakker
Senior Oracle DBA

EXPDP errors

Hi,
I got error when I tried this...Please let me know as we need to backup the schema.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_02": system/******** parfile=expdp.par
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD [ESTIMATE_PHASE]
ORA-04063: package body "SYS.DBMS_METADATA" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8358
----- PL/SQL Call Stack -----
object line object
handle number name
0x7b228110 19208 package body SYS.KUPW$WORKER
0x7b228110 8385 package body SYS.KUPW$WORKER
0x7b228110 6628 package body SYS.KUPW$WORKER
0x7b228110 12605 package body SYS.KUPW$WORKER
0x7b228110 2546 package body SYS.KUPW$WORKER
0x7b228110 9054 package body SYS.KUPW$WORKER
0x7b228110 1688 package body SYS.KUPW$WORKER
0x7d909dc8 2 anonymous block
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD [ESTIMATE_PHASE]
ORA-04063: package body "SYS.DBMS_METADATA" has errors
ORA-06508: PL/SQL: could not find program unit being called: "SYS.DBMS_METADATA"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8358
----- PL/SQL Call Stack -----
object line object
handle number name
0x7b228110 19208 package body SYS.KUPW$WORKER
0x7b228110 8385 package body SYS.KUPW$WORKER
0x7b228110 6628 package body SYS.KUPW$WORKER
0x7b228110 12605 package body SYS.KUPW$WORKER
0x7b228110 2546 package body SYS.KUPW$WORKER
0x7b228110 9054 package body SYS.KUPW$WORKER
0x7b228110 1688 package body SYS.KUPW$WORKER
0x7d909dc8 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at 14:14:00
[1]+ Exit 5 expdp parfile=expdp.par
Thanks

It is impossible to not have RMAN if you have any Oracle database that has been supported in the last decade.
RMAN is built in ... RMAN is free ... RMAN is the only tool you should be using.
Worried about learning something new? Here's what is required to run RMAN.
# rman target /
RMAN> backup database;one can get a lot more detailed but this is all that is actually required.

Expdp error ORA-39095

Similar Messages

Maybe you are looking for