Howto work around CC fatal error

Hi,
I am getting the following error - which seems to me to be a bug...:
postopt: assertion failed: at line 352 in file "../src/generic/infrastructure/exception_handler.cc"
postopt: Invalid symbol referenced in exception relocation entry
CC: Fatal error in postopt: Abort (core dumped)
does anybody hava an idea how it might be possible to find out, what causes this error?
System information:
Workshop 8 with patches 112763-02 113823-02
$ CC -V
CC: Sun C++ 5.5 2003/03/12
$ uname -a
SunOS anduril 5.8 Generic_108528-21 sun4u sparc SUNW,Sun-Blade-1000

you are right - the link-optimizer causes the problem
but now, as I turned it off, I am getting an unresolved symbol called .Lx422 which isn't in my source code at all
when I switch to -xipo=0 this undefined symbol goes away
I tried to generate a test pattern, but it's actually not easy to find out the reason for a problem, when the compiler doesn't give you any hint why it is in trouble...
Anyway - thank you very much,
Tom

Similar Messages

Another tip for working around iDVD encoding errors: Use internal drive

I've had several projects that produced the encoding error while rendering the menus, I've also seen a number of tips in this discussion area, e.g., have 20 GB of free space, delete iDVD preferences, delete encoded assets, and make sure your chapter markers are not near a transition or end of a clip (good luck with that using iDVD to set your chapters). Neither of these tips alone allowed me to burn a disk image to disk, but I'm confident they contribute to a more stable iDVD performance overall.
In my case, the only way I've managed to make the projects to work is to copy the iMovie project over to my internal drive, create the iDVD project on the internal drive and to save the disk image to the internal drive.
If you're low on internal disk space, as I am, easy to move assets is another advantage of using iMovie 6 over iMovie 8, i.e., you can create the iMovie project on the external drive and then drag a temporary copy over to the internal drive, then you can launch iDVD from within iMovie 6 without the annoying step of exporting to the Media Browser. When you're done, delete the temporary movie to free up space for your next project. The iDVD projects can also be moved to a backup drive or deleted.

You'll always get better results on the startup volume / internal HD (as opposed to an ext. HD) provided you also have at least 20GB's of available HD space remaining. Anything less is often problematic at best.
My suggestion in this situation is to find a way to clear more HD space. You can clear video files already burned to DVD-R media, burn your iPhoto Library to DVD to clear more space , or even consider clearing languages you won't need on your system with an app like Monolingual. No problems will be created by removing unneeded language files (however it's highly recommend you avoid removing architectures on any intel mac).
http://monolingual.sourceforge.net/
The following may interest you as well:
http://discussions.apple.com/thread.jspa?threadID=1102377&tstart=0

DVDSP4 build to Primo DVD-will it work around layer break error ?

I tried to create layer breaks because under the build option automatic won't burn and manual breaks are greyed out. so i can't burn and i need to get this done before sunday. the build to my hard drive works perfectly and if i test the DVD video folder using DVD player, it works great. If I move the Video & Audio DVD folders to my PC and use Primo DVD and burn a DL disc, will the layer break errors in DVD Studio Pro cause problems during the playback of a disc burned with Primo DVD? Basically, will these DVDSP4 errors carry over no matter what burning program I use; Toast, Primo, Record Now??

http://discussions.apple.com/thread.jspa?messageID=4078067&#4078067
(I also mentioned this just now in the other thread just in case)
Anyway you will need a proper break point, not sure (have not used) Primo so do not know if it will throw a break point in somehow or not, but if you go to the above thread works through the issues for you

How do I work around a msaccess_utilities error

The msaccess query has rows
Booking.[Lecture Date],
Year([Lecture Date]) AS [Year],
Month([Lecture Date]) AS [Month],
SQL Dveloper quick migration translates this as:
Booking.Lecture_Date,
msaccess_utilities.datepart('YEAR', Lecture_Date) YEAR,
msaccess_utilities.datepart('MONTH', Lecture_Date) MONTH,
But the package definition does not have a datepart function so the migration dies at this point.
The package definition is
CREATE OR REPLACE PACKAGE msaccess_utilities AS
FUNCTION month(datetime_expr VARCHAR2) RETURN NUMBER;
FUNCTION year(datetime_expr VARCHAR2) RETURN NUMBER;
END msaccess_utilities;
I assume that it should have a datepart function, or the column definitions should call the year and month functions.
Is there any way to get the migration assistant to generate code that will handle these columns correctly?
Secondly, if I fix and run the SQL manually, how do I get the migration to re-start at the data load step?
thanks
~trevor

Hi Trevor,
The Migrate Data option will remain greyed out if you don't have an open connection to a Migration Repository. I would recommend that you review the steps outlined in the accompanying Help, specifically the section Before You Start Migrating: General Information in the chapter titled Migrating Third-Party Databases, available via the Help > Table of Contents menu item. Once you have created a connection to a Migration Repository, all of the menu items under "Migration" show be active. Some supplementary documentation is available for download from OTN - http://download.oracle.com/docs/cd/E10405_01/doc/nav/portal_booklist.htm.
Note: in order to use the Migrate Data option, you will also need to create a connection to the MS Access MDB file that you are migrating. This Access connection will then be used during the data migration process.
I hope this helps.
Regards,
Hilary

Problems installing photosmart b110a on Windows 7 64-bit - FATAL ERROR in driver installation!

Hello,
maybe that you can also help my with the installation of the driver software for my B110a on my Windows 7 64-bit Enterprise Edition Laptop. I downloaded the driver software from:
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=mp-82451-1&cc=de&dlc=de&lc=de&...
I tried it several times, including the HP Installation Error - Windows 7.hta guidance. Actually I've already installed a lot of printers on PC's in my family - i've never experienced such a problem...
I always ended up with a "fatal error" :
1. fatal error:
2. error information send to HP:
3. details / error situation code:
Any help is highly welcome and appreciated since I am quite desparate in the meantime - after trial & error for more that 3 hours... ;-(
Many thanks in advance & best regards from Switzerland, Dominic
Dominic Rihm
[Personal Information Removed]
This question was solved.
View Solution.

The fatal error you got with the B110a is caused by an .msi error. The document below should walk you through that.
Fatal Error 'Error 1603. A fatal error occurred during installation' (MSI Error 1603) Displays Durin...
The fatal error you got with the B109a might have a different fix. It would depend on the exact error code you received. The document below should help you find the error code and work through the fatal error.
A 'Fatal Error' (MSI error) Displays on the Computer During HP Software Installation in Windows
-------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

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

HT1751 On an old Mac I got this message while trying to burn a CD for the car: "The attempt to burn a disc failed. The burn failed because of a medium write error." What does this mean? And how do I work around it?

On an older Mac I got this message while trying to burn a CD for the car: "The attempt to burn a disc failed. The burn failed because of a medium write error." What does this mean? And how do I work around it?

I had been getting this all morning and checked other messages from the community. THe one which worked was trying a different brand of disc.
I had been using Verbatim which had copied the music fine off the Real Player on my PC at school, but wouldn't work with I Tunes. Tried a Staples and an Office Depot CD-R , both of which did the job.

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

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

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

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?

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;

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....

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

Howto work around CC fatal error

Similar Messages

Maybe you are looking for