Impdp error ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDL

Hi,
I am trying to generate sql script form the dmp file.
but getting this error.
C:\Documents and Settings\satish.HTSS>impdp egift/egift@local directory=DIR1 dum
pfile=exp.dmp sqlfile=create.sql
Import: Release 10.2.0.1.0 - Production on Saturday, 24 May, 2008 0:16:07
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Master table "EGIFT"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "EGIFT"."SYS_SQL_FILE_FULL_01": egift/********@local directory=DIR1 du
mpfile=exp.dmp sqlfile=create.sql
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
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/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
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/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling D
BMS_METADATA.CONVERT []
ORA-06502: PL/SQL: numeric or value error
LPX-00007: unexpected end-of-file encountered
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
20B135F8     14916 package body SYS.KUPW$WORKER
20B135F8      6300 package body SYS.KUPW$WORKER
20B135F8     12279 package body SYS.KUPW$WORKER
20B135F8      3279 package body SYS.KUPW$WORKER
20B135F8      3956 package body SYS.KUPW$WORKER
20B135F8      6931 package body SYS.KUPW$WORKER
20B135F8      1262 package body SYS.KUPW$WORKER
18E96684         2 anonymous block
Job "EGIFT"."SYS_SQL_FILE_FULL_01" stopped due to fatal error at 00:16:31and this error always comes when it turns to generate sql for the triggers.
i am facing this error continuously.
thanks

Hi,
Its an unpatched db.So you must patch it first.Here is what is mentioned about this error
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 the better part is to contact Support.See if this thread can help you.Its not having much but still ,
Error ORA-39125 and ORA-04063 during export for transportable tablespace
Aman....

Similar Messages

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

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?

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

Hi,
I am trying to refresh my local DB and getting this error.
I have recreated(drop and create) the SR user and tried importing the fresh copy.
Import is working fine on the new Database i.e Deleting and creating the database.
pl. help me finding the solution.
version : 10.1.0.2.0
_____________________import statment_____________________________
impdp SR/SR@db SCHEMAS=SR DIRECTORY=DUMP_FILES_DIR DUMPFILE=DUMPFILE_0313_%U.dmp PARALLEL=4
LOGFILE=imp_0313.LOG EXCLUDE=GRANT TRANSFORM=SEGMENT_ATTRIBUTES:n
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [INDEX:"SR
"."XPKEMP_SAL_FND"]
SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position,
:2), dump_length, dump_allocation, grantor, object_row, object_schema, object_lo
ng_name, processing_status, processing_state, base_object_type, base_object_sche
ma, base_object_name, property, in_progress FROM "SR"."SYS_IMPORT_SCHEMA_01" WHE
RE process_order between :3 AND :4 AND processing_state <> :5 AND duplicate = 0
ORDER BY process_order
ORA-01555: snapshot too old: rollback segment number 2 with name "_SYSSMU2$" too
small
----- PL/SQL Call Stack -----
object line object
handle number name
172874A8 13460 package body SYS.KUPW$WORKER
172874A8 5810 package body SYS.KUPW$WORKER
172874A8 3080 package body SYS.KUPW$WORKER
172874A8 6353 package body SYS.KUPW$WORKER
172874A8 1208 package body SYS.KUPW$WORKER
17AF3BA0 2 anonymous block
Job "SR"."SYS_IMPORT_SCHEMA_01" stopped due to fatal error at 14:41

ORA-01555: snapshot too old: rollback segment number 2 with name "_SYSSMU2$" too
small
Looks like you are hitting snapshot too old error, Fix this one first, look for undo sizes, undo_retention.. This should resolve your problem
if it is still not resolved, refer to this document if you are hitting a bug related to oracle workspace manager.
Note:273267.1

Impdp Worker unexpected fatal error KUPW$WORKER.PUT_DDLS

I`m trying to import IMPDP, dump from (linux oracle 10.02.00.01.00) to oracle 11
and i get :
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"SKASUJMNIE"."ADD_BS_CM"] ]
ORA-06502: PL/SQL: numeric or value error
LPX-00225: end-element tag "COLS_ITEM" does not match start-element tag "BODY"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8164
----- PL/SQL Call Stack -----
object line object
handle number name
0x112977a48 19028 package body SYS.KUPW$WORKER
0x112977a48 8191 package body SYS.KUPW$WORKER
0x112977a48 15631 package body SYS.KUPW$WORKER
0x112977a48 3944 package body SYS.KUPW$WORKER
0x112977a48 8874 package body SYS.KUPW$WORKER
0x112977a48 1651 package body SYS.KUPW$WORKER
0x11f7bee10 2 anonymous block
it happens only where i import triggers ( include=triggers )
file copy was made by scp (so i guess it binary mode ) , i think it occurs in metalink and it problem requires install patch.
Is that any other way to read this trigger pl sql code from dmp file, using pl sql package or program such as awk or sed ?
Kamila

This looks like a corrupted dumpfile.
From what I see in the text that you listed, DataPump import is trying to convert an xml document to ddl and LPX was looking for <BODY> and it got <COLS_ITEM>.
LPX-00225: end-element tag "COLS_ITEM" does not match start-element tag "BODY"
I'm not familiar with scp, but you can try this on the source.
run the same impdp command with this:
sqfile=my_objects.sql
If it works then the dumpfile on the source is good. If not, then the dumpfile on the source is bad.
Looking in the dumpfile will not help much. What you will see in there is xml and you would have to find the right xml document for the object you are looking for and then try to figure out how to convert it to ddl.
Dean

ORA-39126: Worker unexpected fatal error

Hi,
when importing from a full export file by following commande line :
impdp system/***@orcl DUMPFILE=EXP_FUL_H9DEV.DMP LOGFILE=MYLOG.log
I recieved :
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDL [VIEW:"H9DEV"."PS_AEAPPL_VW"]
ORA-44001: invalid schema
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6273
Any idea ?
Thanks for help.

thank for answer. Here the rest of information :
----- PL/SQL Call Stack -----
object line object
handle number name
6FD3C3CC 14916 package body SYS.KUPW$WORKER
6FD3C3CC 6300 package body SYS.KUPW$WORKER
6FD3C3CC 12689 package body SYS.KUPW$WORKER
6FD3C3CC 11968 package body SYS.KUPW$WORKER
6FD3C3CC 3279 package body SYS.KUPW$WORKER
6FD3C3CC 6889 package body SYS.KUPW$WORKER
6FD3C3CC 1262 package body SYS.KUPW$WORKER
6FE88CDC 2 anonymous block
Job "SYSTEM"."SYS_IMPORT_FULL_01" stopped due to fatal error at 01:02:03
And also :
SQL> desc PS_AEAPPL_VW
ERROR:
ORA-04043: object PS_AEAPPL_VW does not exist
SQL> select object_name from dba_objects where object_name like '%PS_AEAPPL_VW%';
no rows selected

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

Any suggestions for error below
the comp_name from dba_registry are all VALID
OS : Windows 2008 R2
database version 11.2.0.1.0
Import: Release 11.2.0.1.0 - Production on Fri Sep 21 23:15:33 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_FULL_08" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_08": system/******** directory=ORADUMP dumpfile=essex.dmp logfile=essex-import.log remap_schema=CONFIRM:CON_ESSEX,SBS:SBS_ESSEX REMAP_TABLESPACE=CONFIRM:CON_ESSEX exclude=statistics
Processing object type SCHEMA_EXPORT/USER
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, NVL(value_n, 0), grantor, object_row, object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, base_object_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_level, object_int_oid FROM "SYSTEM"."SYS_IMPORT_FULL_08" WHERE process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_order]
ORA-39183: internal error -19 ocurred during decompression phase 2
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
000007FFBC220BC0 18990 package body SYS.KUPW$WORKER
000007FFBC220BC0 8192 package body SYS.KUPW$WORKER
000007FFBC220BC0 4173 package body SYS.KUPW$WORKER
000007FFBC220BC0 8875 package body SYS.KUPW$WORKER
000007FFBC220BC0 1649 package body SYS.KUPW$WORKER
000007FFA2F9E3D8 2 anonymous block
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOAD_METADATA [SELECT process_order, flags, xml_clob, NVL(dump_fileid, :1), NVL(dump_position, :2), dump_length, dump_allocation, NVL(value_n, 0), grantor, object_row, object_schema, object_long_name, partition_name, subpartition_name, processing_status, processing_state, base_object_type, base_object_schema, base_object_name, base_process_order, property, size_estimate, in_progress, original_object_schema, original_object_name, creation_level, object_int_oid FROM "SYSTEM"."SYS_IMPORT_FULL_08" WHERE process_order between :3 AND :4 AND duplicate = 0 AND processing_state NOT IN (:5, :6, :7) ORDER BY process_order]
ORA-39183: internal error -19 ocurred during decompression phase 2
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
000007FFBC220BC0 18990 package body SYS.KUPW$WORKER
000007FFBC220BC0 8192 package body SYS.KUPW$WORKER
000007FFBC220BC0 4173 package body SYS.KUPW$WORKER
000007FFBC220BC0 8875 package body SYS.KUPW$WORKER
000007FFBC220BC0 1649 package body SYS.KUPW$WORKER
000007FFA2F9E3D8 2 anonymous block
Job "SYSTEM"."SYS_IMPORT_FULL_08" stopped due to fatal error at 23:15:41

I have ran the impdp command on same database before and they have worked fine
we have 11.2.0.1.0 version both on source and target database
nothing has changed on the db as the target database has been up and running
i have also logged to metalink
dont want to upgrade to 11.2.0.3.0 at this point if there is a work around for this
Edited by: 912919 on 21-Sep-2012 15:47

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

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

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

Greetings All
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 - ProductionI have 4 installations of Oracle as described above(prod01,prod02, stage01, local), each on separate boxes/servers. Except for memory allocations, all are configured the same (parms).
I have a user (CM_MASTER) on each instance, again all configured the exact same except the instance installed locally on my laptop. The instance installed on my laptop has only a USERS tablespace, where as the 3 others have a 2nd tablespace established for CM_MASTER.
CM_MASTER has:
unlimited space quotas on both tablespaces (where applicable).
Has execute privilege on DBMS_DATAPUMP
Read and Write privileges on the BACKUP directory.
I am able to successfully export the CM_MASTER schema from the stage01, and my local instances.
However to the other 2 (prod01 and prod02) I am getting the following errors:
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [REF_CONSTRAINT:"CM_MASTER"."CGP_SPE_FK3"]
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
0000001DFE3849E8     18990 package body SYS.KUPW$WORKER
0000001DFE3849E8      8192 package body SYS.KUPW$WORKER
0000001DFE3849E8      2823 package body SYS.KUPW$WORKER
0000001DFE3849E8      8847 package body SYS.KUPW$WORKER
0000001DFE3849E8      1649 package body SYS.KUPW$WORKER
0000001DEDB9C890         2 anonymous block
Job "CM_MASTER"."EXPCM_USER11" stopped due to fatal error at 15:09:17Please note that the INVALID package body is invalid on all 4 instances.
I can get the export on my local and stage01 instances to fail similarly if I grant CM_MASTER the privilege IMP_FULL_DATABASE. And then after revoking the same privilege the exports are good again.
However the error still occurs on the prod01 and prod02 instances whether or not CM_MASTER has the IMP_FULL_DATABASE privilege.
I have already tried the drop_database_statistics and then gather_database_statistics routine proposed on several other posts.
Any suggestions will be appreciated.
Thanks,
Bob

execute on DBMS_SQL must be given to public;

Error data pump import: Worker unexpected fatal error in KUPW$WORKER.MAIN

Hello.
I try to import dump
impdp DIRECTORY=data_pump_dir DUMPFILE=04-2013.dmp TRANSFORM=OID:n LOGFILE=04-2013.dmp.log
(user - system (tried with sys) , (also with parallel=1 (or 2, or 8))and have following error:
Import: Release 11.2.0.1.0 - Production on Fri May 31 12:55:42 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-39079: unable to enqueue message RQ
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPC$QUE_INT", line 965
ORA-00931: missing identifier
ORA-06512: at "SYS.KUPW$WORKER", line 16746
ORA-06512: at "SYS.KUPW$WORKER", line 19035
ORA-06512: at "SYS.KUPW$WORKER", line 8191
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.MAIN []
ORA-06512: at "SYS.KUPW$WORKER", line 1705
ORA-44002: invalid object name
ORA-06512: at line 2
How can I fix it?
Alert_log
Fri May 31 14:26:21 2013
DM00 started with pid=32, OS id=36385, job SYSTEM.SYS_IMPORT_FULL_03
Fri May 31 14:26:22 2013
DW00 started with pid=33, OS id=36387, wid=1, job SYSTEM.SYS_IMPORT_FULL_03
DW00 terminating with fatal err=39079, pid=33, wid=1, job SYSTEM.Also there is some invalid objects in SYS:
SYS.DBMS_SQLTUNE_INTERNAL
SYS.DBMS_SQLTUNE
SYS.DBMS_WRR_INTERNAL
SYS.DBMS_WORKLOAD_REPLAY
SYS.PRVT_SQLPA
SYS.DBMS_SMB_INTERNAL
WMSYS.LTUTIL
WMSYS.LTADM
WMSYS.UD_TRIGS
WMSYS.OWM_DDL_PKG
WMSYS.OWM_MIG_PKG
EXFSYS.DBMS_EXPFIL_DR
EXFSYS.DBMS_EXPFIL
EXFSYS.ADM_EXPFIL_SYSTRIG
CTXSYS.DRVDDL
XDB.DBMS_XDBZ0
XDB.DBMS_XSLPROCESSOR
XDB.DBMS_XDBUTIL_INT
XDB.DBMS_CSX_ADMIN
EXFSYS.DBMS_RLMGR_UTL
EXFSYS.DBMS_RLMGR_IR
EXFSYS.DBMS_RLMGR_IRPK
EXFSYS.DBMS_RLMGR_DEPASEXP
MDSYS.SDO_CS
SYSMAN.EMD_MAINTENANCE
SYSMAN.MGMT_ADMIN_DATA

here are trace files [http://files.mail.ru/B05EBC4402A342D0AE1E88BFB04191DB|http://files.mail.ru/B05EBC4402A342D0AE1E88BFB04191DB]
error here:
KUPM:12:47:19.571: Error detected by MCP
KUPM:12:47:19.572: ORA-39014: One or more workers have prematurely exited.
KUPM:12:47:19.572: ORA-39029: worker 1 with process name "DW00" prematurely terminated
KUPM:12:47:19.572: ORA-31671: Worker process DW00 had an unhandled exception.
ORA-39079: unable to enqueue message RQ
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPC$QUE_INT", line 965
ORA-00931: missing identifier
ORA-06512: at "SYS.KUPW$WORKER", line 16746
ORA-06512: at "SYS.KUPW$WORKER", line 19035
ORA-06512: at "SYS.KUPW$WORKER", line 8191
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.MAIN []
ORA-06512: at "SYS.KUPW$WORKER", line 1705
ORA-44002: invalid object name
ORA-06512: at line 2
KUPM:12:47:19.577: In restart_worker for worker 1...
KUPM:12:47:19.577: Error being processed is: -26457
KUPM:12:47:19.577: worker id is:
KUPM:12:47:19.577: Worker error is: 0
KUPM:12:47:19.577: Exited main loop...
KUPM:12:47:19.577: Returned to MAIN
KUPV:12:47:19.577: Update request for job: SYSTEM.SYS_IMPORT_FULL_03, func: 1
KUPM:12:47:19.578: Entered state: UNDEFINED
KUPM:12:47:19.578: In RESPOND_TO_START
KUPC:12:47:19.578: Before ENQ: Sending Type: 2041 ID:
KUPC:12:47:19.578: RP,KUPC$C_1_20130603124648,MCP,KUPC$A_1_20130603124649,10,Y
kwqberlst !retval block
kwqberlst rqan->lagno_kwqiia 5
kwqberlst rqan->lascn_kwqiia > 0 block
kwqberlst rqan->lascn_kwqiia 5
kwqberlst ascn 2375213 lascn 22
KUPM:12:47:19.579: In check_workers...
KUPM:12:47:19.579: Live worker count is: 0
KUPM:12:47:19.579: worker id is:
KUPM:12:47:19.579: Worker error is: 0
KUPM:12:47:19.579: Job is completing

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

Error ORA-39125 and ORA-04063 during export for transportable tablespace

I'm using the Oracle Enterprise Manager (browser is IE) to create a tablespace transport file. Maintenance...Transport Tablespaces uses the wizard to walk me through each step. The job gets created and submitted.
The 'Prepare' and 'Convert Datafile(s)' job steps complete successfully. The Export step fails with the following error. Can anyone shed some light on this for me?
Thank you in advance!
=======================================================
Output Log
Export: Release 10.2.0.2.0 - Production on Sunday, 03 September, 2006 19:31:34
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Username:
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
With the Partitioning, OLAP and Data Mining options
Starting "SYS"."GENERATETTS000024": SYS/******** AS SYSDBA dumpfile=EXPDAT_GENERATETTS000024.DMP directory=EM_TTS_DIR_OBJECT transport_tablespaces=SIEBEL job_name=GENERATETTS000024 logfile=EXPDAT.LOG
Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
Processing object type TRANSPORTABLE_EXPORT/TABLE
Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA while calling DBMS_METADATA.FETCH_XML_CLOB [TABLE_STATISTICS]
ORA-04063: view "SYS.KU$_IOTABLE_VIEW" has errors
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
2CF48130 14916 package body SYS.KUPW$WORKER
2CF48130 6300 package body SYS.KUPW$WORKER
2CF48130 2340 package body SYS.KUPW$WORKER
2CF48130 6861 package body SYS.KUPW$WORKER
2CF48130 1262 package body SYS.KUPW$WORKER
2CF0850C 2 anonymous block
Job "SYS"."GENERATETTS000024" stopped due to fatal error at 19:31:44

More information:
Using SQL Developer, I checked the view SYS.KU$_IOTABLE_VIEW referred to in the error message, and it does indeed report a problem with that view. The following code is the definition of that view. I have no idea what it's supposed to be doing, because it was part of the default installation. I certainly didn't write it. I did, however, execute the 'Test Syntax' button (on the Edit View screen), and the result was this error message:
=======================================================
The SQL syntax is valid, however the query is invalid or uses functionality that is not supported.
Unknown error(s) parsing SQL: oracle.javatools.parser.plsql.syntax.ParserException: Unexpected token
=======================================================
The SQL for the view looks like this:
REM SYS KU$_IOTABLE_VIEW
CREATE OR REPLACE FORCE VIEW "SYS"."KU$_IOTABLE_VIEW" OF "SYS"."KU$_IOTABLE_T"
WITH OBJECT IDENTIFIER (obj_num) AS
select '2','3',
t.obj#,
value(o),
-- if this is a secondary table, get base obj and ancestor obj
decode(bitand(o.flags, 16), 16,
(select value(oo) from ku$_schemaobj_view oo, secobj$ s
where o.obj_num=s.secobj#
and oo.obj_num=s.obj#),
null),
decode(bitand(o.flags, 16), 16,
(select value(oo) from ku$_schemaobj_view oo, ind$ i, secobj$ s
where o.obj_num=s.secobj#
and i.obj#=s.obj#
and oo.obj_num=i.bo#),
null),
(select value(s) from ku$_storage_view s
where i.file# = s.file_num
and i.block# = s.block_num
and i.ts# = s.ts_num),
ts.name, ts.blocksize,
i.dataobj#, t.bobj#, t.tab#, t.cols,
t.clucols, i.pctfree$, i.initrans, i.maxtrans,
mod(i.pctthres$,256), i.spare2, t.flags,
t.audit$, t.rowcnt, t.blkcnt, t.empcnt, t.avgspc, t.chncnt, t.avgrln,
t.avgspc_flb, t.flbcnt, t.analyzetime, t.samplesize, t.degree,
t.instances, t.intcols, t.kernelcols, t.property, 'N', t.trigflag,
t.spare1, t.spare2, t.spare3, t.spare4, t.spare5, t.spare6,
decode(bitand(t.trigflag, 65536), 65536,
(select e.encalg from sys.enc$ e where e.obj#=t.obj#),
null),
decode(bitand(t.trigflag, 65536), 65536,
(select e.intalg from sys.enc$ e where e.obj#=t.obj#),
null),
(select c.name from col$ c
where c.obj# = t.obj#
and c.col# = i.trunccnt and i.trunccnt != 0
and bitand(c.property,1)=0),
cast( multiset(select * from ku$_column_view c
where c.obj_num = t.obj#
order by c.col_num, c.intcol_num
) as ku$_column_list_t
(select value(nt) from ku$_nt_parent_view nt
where nt.obj_num = t.obj#),
cast( multiset(select * from ku$_constraint0_view con
where con.obj_num = t.obj#
and con.contype not in (7,11)
) as ku$_constraint0_list_t
cast( multiset(select * from ku$_constraint1_view con
where con.obj_num = t.obj#
) as ku$_constraint1_list_t
cast( multiset(select * from ku$_constraint2_view con
where con.obj_num = t.obj#
) as ku$_constraint2_list_t
cast( multiset(select * from ku$_pkref_constraint_view con
where con.obj_num = t.obj#
) as ku$_pkref_constraint_list_t
(select value(ov) from ku$_ov_table_view ov
where ov.bobj_num = t.obj#
and bitand(t.property, 128) = 128), -- IOT has overflow
(select value(etv) from ku$_exttab_view etv
where etv.obj_num = o.obj_num)
from ku$_schemaobj_view o, tab$ t, ind$ i, ts$ ts
where t.obj# = o.obj_num
and t.pctused$ = i.obj# -- For IOTs, pctused has index obj#
and bitand(t.property, 32+64+512) = 64 -- IOT but not overflow
-- or partitioned (32)
and i.ts# = ts.ts#
AND (SYS_CONTEXT('USERENV','CURRENT_USERID') IN (o.owner_num, 0) OR
EXISTS ( SELECT * FROM session_roles
WHERE role='SELECT_CATALOG_ROLE' ));
GRANT SELECT ON "SYS"."KU$_IOTABLE_VIEW" TO PUBLIC;

Expdp gives error ORA-39125 ,ORA-31642 DBMS_RULE_EXP_RULES

DB version=10.2.0.4 64bit
os =linux OEL 64bit
When i execute expdp it gives the following errors and exit :
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-31642: the following SQL statement fails:
BEGIN "SYS"."DBMS_RULE_EXP_RULES".SCHEMA_CALLOUT(:1,0,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-08103: object no longer exists
what is the problem?! i searched in metalink and could not find any solution.

Pl post the complete expdp command used. Can you reproduce this issue consistently ?
OERR: ORA-8103 "object no longer exists" / Troubleshooting, Diagnostic and Solution [ID 8103.1]
HTH
Srini

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;

Impdp error ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDL

Similar Messages

Maybe you are looking for