Fatal Error in EXPDP

Hi Exprts
i m using EXPDP to take schema level backup but i get below error
my DB Version is Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 and O/S Red Hat Enterprise Linux AS release 3 (Taroon Update 5)
please guide me
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SYSTEM"."SYS_EXPORT_SCHEMA_01": system/******** directory=dmp_exp dumpfile=stg1_2010-07-26.dmp logfile=stg1_2010-07-26.log schemas=stg1
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 357.6 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/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [SEQUENCE:"STG1"."SEQ_CUST_NO"]
ORA-04021: timeout occurred while waiting to lock object
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
0x43ded45c 14916 package body SYS.KUPW$WORKER
0x43ded45c 6300 package body SYS.KUPW$WORKER
0x43ded45c 2340 package body SYS.KUPW$WORKER
0x43ded45c 6861 package body SYS.KUPW$WORKER
0x43ded45c 1262 package body SYS.KUPW$WORKER
0x43c497b4 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_01" stopped due to fatal error at 13:00:06
Edited by: Ziram on Jul 26, 2010 1:33 AM

Seems like an unpatched oracle is the reason ,
[oracle@edhdr1p14-orcl ~]$ oerr ora 39125
39125, 00000, "Worker unexpected fatal error in %s while calling %s [%s]"
// *Cause: An unhandled exception was detected internally within the worker
//          process for the Data Pump job while calling the specified external
//          routine. This is an internal error. Additional information may be
//          supplied.
// *Action: If problem persists, contact Oracle Customer Support.So either patch it with the latest patchset and then rerun or contact support for this error.
HTH
Aman....

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 full=y shows 'fatal error '

Hi all,
       any body, please help, I tried to take a full database export using expdp, with the schema name 'x' and password 'x', it is showing error as follows,
[oracle@oracleoel5 ~]$ expdp x/x directory=dpumpdir dumpfile=ramu.dmp full=y parallel=5 nologfile=y
Export: Release 10.2.0.1.0 - Production on Tuesday, 30 July, 2013 15:40:06
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "X"."SYS_EXPORT_FULL_03": x/******** directory=dpumpdir dumpfile=ramu.dmp full=y parallel=5 nologfile=y
Estimate in progress using BLOCKS method...
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_LOB.CREATETEMPORARY []
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6235
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x4158a904     14916 package body SYS.KUPW$WORKER
0x4158a904      6300 package body SYS.KUPW$WORKER
0x4158a904      9120 package body SYS.KUPW$WORKER
0x4158a904      1880 package body SYS.KUPW$WORKER
0x4158a904      6861 package body SYS.KUPW$WORKER
0x4158a904      1262 package body SYS.KUPW$WORKER
0x414798c0         2 anonymous block
Job "X"."SYS_EXPORT_FULL_03" stopped due to fatal error at 15:40:10
Thanks & Regards,
Rajagopal S.,

Hi
One Master Table is created in the schema of the current user running the Pump Dump export or import,and it keeps tracks of detailed information.
and this table required storage which should use the default property of schema like default tablespace and default temporary tablesapce
>>whether the same 'fatal error' possible in normal export ?
No

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 fails with ORA-39125: Worker unexpected fatal error in KUPW $

Hi Friends,
Oracle 10.2.0.4.0 on Sun OS
Im trying to do metadata_only export using EXPDP
Facing the below error
ORA-39125: Worker unexpected fatal error in KUPW $ WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-31642: The following SQL statement fails:
BEGIN "SYS". "DBMS_RULE_EXP_RULES." SCHEMA_CALLOUT (1,1,1, '10 .02.00.04.00 ') END;
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_METADATA", line 907
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW $ WORKER", line 6307
PL / SQL Call Stack
object line object
handle number name
51bf5dc20 15032 package body SYS.KUPW $ WORKER
51bf5dc20 6372 package body SYS.KUPW $ WORKER
51bf5dc20 2396 package body SYS.KUPW $ WORKER
51bf5dc20 6944 package body SYS.KUPW $ WORKER
51bf5dc20 1314 package body SYS.KUPW $ WORKER
51c7e8650 2 anonymous block
====================================
Findings:
I check the status of DBMS_RULE_EXP_RULES
OWNER OBJECT_NAME OBJECT_TYPE STATUS
SYS DBMS_RULE_EXP_RULES PACKAGE BODY VALID
SYS DBMS_RULE_EXP_RULES PACKAGE VALID
PUBLIC DBMS_RULE_EXP_RULES SYNONYM VALID
DBMS_METADATA & DBMS_SYS_ERROR packages are valid.
======================================================
Error in the alert:
The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=25, OS id=6506
to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SYS', 'KUPC$C_1_20120908075037', 'KUPC$S_1_20120908075037', 0);
kupprdp: worker process DW01 started with worker id=1, pid=26, OS id=6633
to execute - SYS.KUPW$WORKER.MAIN('SYS_EXPORT_SCHEMA_01', 'SYS');
when i check the trace file, find the below error
ORA-04063: package body "SCH.COLLECTION" has errors
But when I check the status of the package, it's valid.
Thanks for your help
KSG

Hi;
Is it full exp? Of yes please review:
DataPump Export Fails With Errors ORA-39125 ORA-31642 ORA-1422 [ID 790988.1]
Full And Schema DataPump Exports Fail With Errors ORA-39125 ORA-31642 During DBMS_SCHED_EXPORT_CALLOUTS.SCHEMA_CALLOUT [ID 1109045.1]
EXPDP FAILS WITH ORA-39125 ORA-31642 DBMS_SCHED_EXPORT_CALLOUTS [ID 445291.1]
Full Database DataPump Export (EXPDP) Fails With Errors ORA-39125 ORA-4045 ORA-1031 On XDB.XDB_PI_TRIG [ID 1102434.1]
Errors ORA-39125 ORA-1801 When Running DataPump Export (EXPDP) [ID 815683.1]
Regard
Helios

Expdp unexpected fatal error

Hello Experts
I am trying do a datapump and I get the error as given below. I tried to use the EXCLUDE=STATISTICS clause, but still I get the same error. Please guide me to move forward.
Export: Release 11.2.0.1.0 - Production on Thu Nov 14 13:28:36 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Release 11.2.0.3.0 - 64bit Production
Starting "test"."SYS_EXPORT_SCHEMA_05": test/********@mydb schemas=my_schema directory=DATAPUMP dumpfile=dev_my_schema_DB_11_14_2013.dp logfile=dev_my_schema_DB_11_14_2013.log FLASHBACK_TIME=SYSTIMESTAMP
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 3.226 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/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [SEQUENCE:"my_schema"."my_schema_ID_SEQ"]
ORA-44203: timeout waiting for lock on cursor
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object      line object
handle    number name
0xf7388d08     20462 package body SYS.KUPW$WORKER
0xf7388d08      9028 package body SYS.KUPW$WORKER
0xf7388d08     10935 package body SYS.KUPW$WORKER
0xf7388d08      2728 package body SYS.KUPW$WORKER
0xf7388d08      9697 package body SYS.KUPW$WORKER
0xf7388d08      1775 package body SYS.KUPW$WORKER
0x16bd96fe8         2 anonymous block
Job "test"."SYS_EXPORT_SCHEMA_05" stopped due to fatal error at 13:35:50

I tried the following query to find uncommitted transactions and I see only 1 which is by SYSMAN and status ia INACTIVE.
select t.start_time,s.sid,s.serial#,s.username,s.status,s.schemaname,
s.osuser,s.process,s.machine,s.terminal,s.program,s.module,to_char(s.logon_time,'DD/MON/YY HH24:MI:SS') logon_time
from v$transaction t, v$session s
WHERE S.SADDR = T.SES_ADDR
order by start_time;

ORA-04030: out of process memory error for expdp utility

Hi,
I am using expdp utility to export schema objects. It was working fine for the past one year, but now I am facing this issue.
It is giving below error while exporting one schema objects.
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE:....................
ORA-04030: out of process memory when trying to allocate 4108 bytes (Typecheck,kgghteInit)
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
678894EC 14916 package body SYS.KUPW$WORKER
678894EC 6300 package body SYS.KUPW$WORKER
678894EC 2340 package body SYS.KUPW$WORKER
678894EC 6861 package body SYS.KUPW$WORKER
678894EC 1262 package body SYS.KUPW$WORKER
501F624C 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_37" stopped due to fatal error at 03:30:28
DB version: Oracle 10.2.0.1
SGA Details:
Total System Global Area 1426063360 bytes
Fixed Size 1251052 bytes
Variable Size 243271956 bytes
Database Buffers 1124073472 bytes
Redo Buffers 57466880 bytes
pga_agregate_target = 600M
OS: Windows Server 2003 R2
RAM: 3.5 GB
I tried running expdp multiple times every time I will get out of memeory error along with different oracle errors, but the common error is out of memory ora -04030.
In above case I got this error along with ORA-39125 and sometimes I will get with
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31671
I searched forums and found lot options but not for expdp utility.
Can some one please help in resolving this issue.
Thanks,
Srikanth.K

Hi;
Please investigate your issue:
Master Note for Diagnosing OS Memory Problems and ORA-4030 [ID 1088267.1]
DataPump Export (EXPDP) Terminates With Error ORA-4030 [ID 1368462.1]
Regard
Helios

KUPW$WORKER.UNLOAD_METADATA Errors with EXPDP 11G

I'm trying to do an expdp on a fairly new install of 11g. This DB has been up and running fine for about 2 weeks. It was a fresh install of 11g and then I impdp the data from our old 10R2 DB. That all went fine. Now I'm doing another fresh install of another 11g DB on another server. So I'm trying to do a expdp of the data in the 11g DB to use to then impdp into the new 11g install to get it started with data and tables. When I run exdp though I start running into the error below. Now this doesn't happen when I do 'content=DATA_ONLY' but when I do 'content=ALL' or 'content=METADATA_ONLY' it happens. Nothing has happened since the install and this was the first time I tried doing a expdp on this database. Like i said earlier i did a impdp to put data and tables into it and that ran fine. Any ideas because I have looked around and not found any information yet that helped. Thanks in advance!
(Some side info: This is running on a AMD64 server running Ubuntu Server Linux 8.04)
Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "MORENOC"."SYS_EXPORT_SCHEMA_11": morenoc/******** directory=BACKUP dumpfile=syslog.dmp schemas=SYSLOG content=METADATA_ONLY
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/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [OBJECT_GRANT:"SYSLOG"]
ORA-04063: view "SYS.KU$_CLUSTER_VIEW" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7709
----- PL/SQL Call Stack -----
object line object
handle number name
0x1ee00a600 18051 package body SYS.KUPW$WORKER
0x1ee00a600 7736 package body SYS.KUPW$WORKER
0x1ee00a600 2712 package body SYS.KUPW$WORKER
0x1ee00a600 8342 package body SYS.KUPW$WORKER
0x1ebc00ff0 1 anonymous block
0x1eb676a60 1501 package body SYS.DBMS_SQL
0x1ee00a600 8201 package body SYS.KUPW$WORKER
0x1ee00a600 1477 package body SYS.KUPW$WORKER
0x1ed141ad8 2 anonymous block

I get the following when running that.
COUNT(*) OWNER
4 PUBLIC
1 WEBDB_TEST
2 XDB
26 SYS
When I try and run @utlrp though, it started then I get the following error:
DECLARE
ERROR at line 1:
ORA-03113: end-of-file on communication channel
Process ID: 6021
Session ID: 74 Serial number: 1827
ERROR:
ORA-03114: not connected to ORACLE
Where is the place in EM 11G to see the Invalid Objects by schema?

Error in expdp - single schema

Hi,
We are exporting single schema using expdp command and getting following error while export in been taken:
Command used:
expdp impexp/********@dbname schemas=schema1 directory=DATA_PUMP_DIR dumpfile=EXPDP_schema1_PRE_231111.dmp LOGFILE=EXPDP_schema1_PRE_231111.log version=compatible content=ALL
Error
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/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
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/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/TABLE/RLS_POLICY/RLS_POLICY
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [PACKAGE:"SCHEMA1".PK_XFACE_IV_LOST_REP_REL_DTLS"]
ORA-06502: PL/SQL: numeric or value error: NULL index table key value
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
0x965e8970 19208 package body SYS.KUPW$WORKER
0x965e8970 8385 package body SYS.KUPW$WORKER
0x965e8970 2935 package body SYS.KUPW$WORKER
0x965e8970 9054 package body SYS.KUPW$WORKER
0x965e8970 1688 package body SYS.KUPW$WORKER
0x89194c60 2 anonymous block
Job "IMPEXP"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 09:31:11
Please suggest what can be done to fix this...

Thanks for the reply..
but it is really strange that how compile time errors effect the overall export and import operation... ideailly it should deploy object as it is...
any other suggestion except to fix code? jst wondering what to do in situation where DBA's are not allowed to touch source codes..

ORA-39125:Worker unexpected fatal error for different different objects...

Hi All,
I am using Oracle database 10.2.0.4 on windows 2003 server.
I want to take full bakup/schema level backup, for this I am using expdp. when I run this expdp it's getting failed with below error:=
===================================================================================
take the schema level backup: Starting "SYSTEM"."SYS_EXPORT_SCHEMA_03": system/********@TEST schemas=JISPBILCORBILLING501 directory=BACKUP_DIR dumpfile=JISPBILCORBILLING501.dmp logfile=JISPBILCORBILLING501.log
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.GET_TABLE_DATA_OBJECTS while calling DBMS_METADATA.FETCH_XML_CLOB []
ORA-01115: IO error reading block from file 5 (block # 3913)
ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TEST\JISPBILCORBILLING501.DBF'
ORA-27091: unable to queue I/O
ORA-27070: async read/write failed
OSD-04006: ReadFile() failure, unable to read from file
O/S-Error: (OS 38) Reached the end of the file.
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6307
----- PL/SQL Call Stack -----
object line object
handle number name
000007FF9ABA7AC0 15032 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 6372 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 9206 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 1936 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 6944 package body SYS.KUPW$WORKER
000007FF9ABA7AC0 1314 package body SYS.KUPW$WORKER
000007FF94192598 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 11:12:50
==================================================================================================
On the same server if I take the other database full backup then also getting similar type of error:
Starting "SYSTEM"."SYS_EXPORT_FULL_11": system/********@jisp full=y directory=BACKUP_DIR dumpfile=jispratcorbilling501_full%U.dmp filesize=3G logfile=jispratcorbilling.log
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while ca
lling DBMS_METADATA.FETCH_XML_CLOB [TYPE:"SYSMAN"."MGMT_CONTAINER_CRED_ARRAY"]
ORA-22813: operand value exceeds system limits
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 229
ORA-06512: at "SYS.KUPW$WORKER", line 889
----- PL/SQL Call Stack -----
object line object
handle number name
000007FFCB72CDB0 15032 package body SYS.KUPW$WORKER
000007FFCB72CDB0 6372 package body SYS.KUPW$WORKER
000007FFCB72CDB0 2396 package body SYS.KUPW$WORKER
000007FFCB72CDB0 6944 package body SYS.KUPW$WORKER
000007FFCB72CDB0 1314 package body SYS.KUPW$WORKER
000007FFCBAA7290 2 anonymous block
Job "SYSTEM"."SYS_EXPORT_FULL_11" stopped due to fatal error at 11:48:49
====================================================================================================
Can anyone suggest me what to look for this error?
Thanks...

I did
1. DMSYS account unlock as well change the password .
2. run this query and verify it VALID status.
select COMP_NAME,VERSION,STATUS from dba_registry where COMP_NAME='Oracle Data Mining';
is any thing else require?

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

Hi!
Running Oracle 11.1.0.7.0 on HP-UX B.11.31
Patch level:
OPatch version : 11.1.0.6.2
OUI version : 11.1.0.7.0
Interim patches
Patch 7690421
Patch 8217795
I was trying to impdp an expdp dump from an identical system (architecture and DB wise) and got into:
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TABLE:"SMS"."STQDATA"]
ORA-06502: PL/SQL: numeric or value error
LPX-00210: expected '<' instead of '
----- PL/SQL Call Stack -----
object line object
handle number name
c000000022255d98 18237 package body SYS.KUPW$WORKER
c000000022255d98 7866 package body SYS.KUPW$WORKER
c000000022255d98 15147 package body SYS.KUPW$WORKER
c000000022255d98 3792 package body SYS.KUPW$WORKER
c000000022255d98 8532 package body SYS.KUPW$WORKER
c000000022255d98 1545 package body SYS.KUPW$WORKER
c000000010cb5f10 2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TABLE:"SMS"."STQDATA"]
ORA-06502: PL/SQL: numeric or value error
LPX-00210: expected '<' instead of '
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 7839
----- PL/SQL Call Stack -----
Thought the dump could have been corrutped, so that tried to make things easier regenerating an empty DB schema with a few tables and tried to import them after exporting them out of the same DB, but with similar result.
Saw a few posts on the same error but nothing helped to fix the issue. Is there anything I could check to overcome this issue ?
Thanks,
Mike

Hi,
sorry to bother, do you happen to have the SR number, so that we could track it online for any progress ?
Could not find any option in the meantime. Somehow exp/imp still works so that we could reload our system but it would take much longer. Tried to rebuild the datapump package but no luck.
Thanks in advance!
Mike

IMPDP: The job SYS_IMPORT_FULL_01 has halted due to a fatal error

Hi,
I'm having problems importing a database whose export was successful.
The tool I'm using is expdp and impdp.
The source schema is in a tablespace different from the target schema, but in the same instance of the Oracle database.
I granted the role of EXP_FULL_DATABASE for the source user and granted the role IMP_FULL_DATABASE to the target user.
Specifically, the following happens: I can export the schema and can successfully import the first four tables to the target schema. So the impdp provides the following message:
Processing object type SCHEMA_EXPORT / TABLE / TABLE_DATA
. . imported "BDE_INEA_DES". "GPL_DECLIV_FRAGIL" 328.4 MB 668 706 lines
. . imported "BDE_INEA_DES". "GLN_CURVA_NIVEL" 336.3 MB 124 324 lines
. . imported "BDE_INEA_DES". "GPL_APP_10" 2920 lines 238.7 MB
. . imported "BDE_INEA_DES". "GLN_CURVA_NIVEL_10" 200.8 MB 15 344 lines
The job "BDE_INEA_DES". "SYS_IMPORT_SCHEMA_01" was halted due to a fatal error at 11:52:41
I've tried exporting using SYSTEM user and the user's schema source owner. I tried the same procedures with the import, but without success.
Information of my OS:
Windows Server 2008 R2 x64
Information of Oracle database:
SQL> SELECT * FROM V $ VERSION;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL / SQL Release 11.2.0.1.0 - Production
CORE 11.2.0.1.0 Production
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production

Follow these steps. You will get exactly what you are trying to find.
1) spool invalidobj_and_registry.txt
SELECT SUBSTR(comp_id,1,15) comp_id, status, SUBSTR(version,1,10)
version, SUBSTR(comp_name,1,30) comp_name
FROM dba_registry
ORDER BY 1;
SELECT status, object_id, object_type, owner||'.'||object_name "OWNER.OBJECT"
FROM dba_objects
WHERE status != 'VALID'
ORDER BY 4,2;
spool.off
2) $ sqlplus "/as sysdba"
sql>EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
sql>EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;
3) Run your import with these two extra parameters along with your parameters
CONTENT=METADATA_ONLY METRICS=Y TRACE=480300
4) As soon as impdp job started:
-- In SQL*Plus, obtain Data Pump processes info:
CONNECT / as sysdba
select to_char(sysdate,'YYYY-MM-DD HH24:MI:SS') "DATE", s.program, s.sid, s.status, s.username, d.job_name, p.spid, s.serial#, p.pid
from v$session s, v$process p, dba_datapump_sessions d
where p.addr=s.paddr and s.saddr=d.saddr;
-- Get the sid and serial# for DM00 and DW01 and execute:
exec DBMS_SYSTEM.SET_EV([SID],[SERIAL#],10046,12 ,'');
for ***both*** of them.
After hang is noticed please leave the import running for one more hour and kill it.
Please check:
- alert log
- impdp log file
- trace files generated during import time in bdump directory
++ before restarting the impdp check if there are orphan Data Pump jobs left in database. Use Note 336014.1 - "How To Cleanup Orphaned DataPump Jobs In DBA_DATAPUMP_JOBS ?

Errors with EXPDP command

we have been experiencing problems with our DataPump exports over the last few weeks, and I have been unable to determine the cause of the problem. Any help would be appreciated.
The following command is being used:
expdp system/xxxxxx@ORACLE_SID full=y directory=DUMP_DIR dumpfile=DUMPFILE.PMPlogfile=expdpDUMPFILE.log
The export will run for 30 - 40 minutes, and will then fail with the following errors:
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 1297
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 6983
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 2761
ORA-24795: Illegal ROLLBACK attempt made
ORA-24795: Illegal ROLLBACK attempt made
ORA-06512: at "SYS.KUPW$WORKER", line 10804
ORA-02354: error in exporting/importing data
ORA-01891: Datetime/Interval internal error
Job "SYSTEM"."SYS_EXPORT_FULL_56" stopped due to fatal error at 00:41:53
ORA-39014: One or more workers have prematurely exited.
The export files are generally 9-10 GB, and will work for one or two nights, and then fail for 2-3 night. The problem has been consistent, but will occasionally work. We are running Oracle 10g in a 2 server RAC environment, and the export will not work consistently on either server.
Any help or suggestions would be appreciated.
Harlyn

914215 wrote:
hey harlyn, did get any solution for this issue in datapump export...I have been facing this issue for a long time..followed many online forums but no luck...can you please share the resolution if u have..thanks in advance...post results from following SQL
SELECT * FROM V$VERSION;

Getting error in expdp....

Dear All,
My database is 11gR2 on Linux. During mid of expdp process I am getting this error:
ORA-31693: Table data object "ETISLBILLING"."SDR_TBLICPCDRSUMMARY" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLECLOSE callout
ORA-31643: unable to close dump file "/backup/exp_backup/etislbilling_27062013.dmp"
ORA-19510: failed to set size of 7417868 blocks for file "/backup/exp_backup/etislbilling_27062013.dmp" (block size=4096)
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9
ORA-39095: Dump file space has been exhausted: Unable to allocate 8192 bytes
Job "ETISLBILLING"."SYS_EXPORT_SCHEMA_14" stopped due to fatal error at 13:50:17
Any idea why this error is being raised and how to resolve it. On the same location and for the same database data pump is successful for another schema.
Regards, Imran

When you say the export works for another schema in the same database are you using the same syntax and would the export file sizes be near enough the same?
Have you seen this metalink note?
DataPump Export (EXPDP) Error ORA-39095 Dump File Space Has Been Exhausted [ID 559692.1]
It could also possibly be a ulimit setting or filesystem space issue.

Fatal Error while sending a fax

Hello
I'm having this problem with one of my users the company.
we have a fax server that is working almost fine for everyone but one specific user, whenever she tries to send a fax from her client computer, after dialing and when it says Transmitting...a Fatal Error comes up,, Event
ID 32028
I did all the suggested actions by Microsoft and other people in the forum, no luck
today i tried something else, send a fax with same user on another client computer...same error
so this is a user problem..i checked all the permissions and FAX USERS group, it is the same like others
please help!!

Hi,
For Event ID 32028, please refer to following article and check if can help you to troubleshoot this issue.
Event ID 32028 — Sent Fax Status
Meanwhile, please open Registry Editor and follow the path:
HKEY_CURRENT_USER\Software\Microsoft\Fax folder when the problematic user account logon, then compare with other user accounts which can be used to send fax as normal. Any difference?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Fatal Error in EXPDP

Similar Messages

Maybe you are looking for