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?

Similar Messages

  • 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;

  • 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;

  • JPA error with Jdev 11g and 3.6 server

    I am testing a sample JPA demo I found on OTN and I am running into an issue when I start a coherence instance in a command window and run the sample code within jdev. If I run this example in Jdev with out starting the extra instance it will run correctly. The error I get is shown below, ideas???
    (Wrapped: Missing or inaccessible constructor "com.tangosol.coherence.jpa.JpaCacheStore(String,String,String)"
    <class-scheme>
    <class-name>com.tangosol.coherence.jpa.JpaCacheStore</class-name>
    <init-params>
    <!--
    This param is the entity name
    This param is the fully qualified entity class
    This param should match the value of the
    persistence unit name in persistence.xml
    -->
    <init-param>
    <param-type>java.lang.String</param-type>
    <param-value>Employees</param-value>
    </init-param>
    <init-param>
    <param-type>java.lang.String</param-type>
    <param-value>jpacoherence.Employees</param-value>
    </init-param>
    <init-param>
    <param-type>java.lang.String</param-type>
    <param-value>JPACoherence</param-value>
    </init-param>
    </init-params>
    </class-scheme>) java.lang.reflect.InvocationTargetException
    at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
    at com.tangosol.run.xml.XmlHelper.createInstance(XmlHelper.java:2487)

    As an updtate, I set local storage = false and that made things work, but I a not sure why. So I stll need and some help in understanding why.

  • Connection pool error with oracle 11g and weblogic 10

    Hi,
    my code is:
    public Connection getConnection() {
              properties = new Properties();
              properties.put(Context.INITIAL_CONTEXT_FACTORY,
                        "weblogic.jndi.T3InitialContextFactory");
              //properties.put(Context.SECURITY_PRINCIPAL, "weblogic");
              //properties.put(Context.SECURITY_CREDENTIALS, "weblogic");
              properties.put(Context.PROVIDER_URL, "t3://172.23.61.214:7001/");
              try {
                   initialContext = new InitialContext(properties);
                   datasource = (DataSource) initialContext.lookup("sample_jndi");
                   try {
                        connection = datasource.getConnection();
                   } catch (SQLException e) {
                        e.printStackTrace();
              } catch (NamingException e) {
                   e.printStackTrace();
              return connection;
    it is giving Exception at line " connection = datasource.getConnection(); "
    Exception is:
    javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.io.EOFException]
         at weblogic.jrmp.Context.lookup(Context.java:189)
         at weblogic.jrmp.Context.lookup(Context.java:195)
         at javax.naming.InitialContext.lookup(Unknown Source)
         at com.code.sample.connectionDB.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:35)
         at com.code.sample.connectionDB.JDBCConnectionPool.main(JDBCConnectionPool.java:52)
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.io.EOFException
         at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
         at sun.rmi.server.UnicastRef.newCall(Unknown Source)
         at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
         at weblogic.jrmp.Context.lookup(Context.java:185)
         ... 4 more
    Caused by: java.io.EOFException
         at java.io.DataInputStream.readByte(Unknown Source)
         ... 9 more
    Please Advice.... Thanks

    I removed the "/" and tried..
    But the exception is same:
    javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.io.EOFException]
         at weblogic.jrmp.Context.lookup(Context.java:189)
         at weblogic.jrmp.Context.lookup(Context.java:195)
         at javax.naming.InitialContext.lookup(Unknown Source)
         at com.code.sample.connectionDB.JDBCConnectionPool.getConnection(JDBCConnectionPool.java:35)
         at com.code.sample.connectionDB.JDBCConnectionPool.main(JDBCConnectionPool.java:52)
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.io.EOFException
         at sun.rmi.transport.tcp.TCPChannel.createConnection(Unknown Source)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(Unknown Source)
         at sun.rmi.server.UnicastRef.newCall(Unknown Source)
         at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
         at weblogic.jrmp.Context.lookup(Context.java:185)
         ... 4 more
    Caused by: java.io.EOFException
         at java.io.DataInputStream.readByte(Unknown Source)
         ... 9 more

  • 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 when exporting with expdp

    Hi there,
    I'm getting a crash on 11g 11.1.0.7 when exporting a schema using expdp:
    expdp
    Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Estimate in progress using BLOCKS method...
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    Total estimation using BLOCKS method: 3.096 GB
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [TABLE_DATA:"NSNPL"."SYS_EXPORT_SCHEMA_02"]
    ORA-22813: operand value exceeds system limits
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPW$WORKER", line 7839
    ----- PL/SQL Call Stack -----
      object      line  object
      handle    number  name
    0x14d81a160     18237  package body SYS.KUPW$WORKER
    0x14d81a160      7866  package body SYS.KUPW$WORKER
    0x14d81a160      2744  package body SYS.KUPW$WORKER
    0x14d81a160      8504  package body SYS.KUPW$WORKER
    0x14d81a160      1545  package body SYS.KUPW$WORKER
    0x14d81db88         2  anonymous block
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA []
    ORA-22813: operand value exceeds system limits
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
    ORA-06512: at "SYS.KUPW$WORKER", line 7834
    ----- PL/SQL Call Stack -----
      object      line  object
      handle    number  name
    0x14d81a160     18237  package body SYS.KUPW$WORKER
    0x14d81a160      7866  package body SYS.KUPW$WORKER
    0x14d81a160      2744  package body SYS.KUPW$WORKER
    0x14d81a160      8504  package body SYS.KUPW$WORKER
    0x14d81a160      1545  package body SYS.KUPW$WORKER
    0x14d81db88         2  anonymous block
    Job "NSNPL"."SYS_EXPORT_SCHEMA_03" stopped due to fatal error at 00:57:23
    This look awfully similar to bug 6991626 (cf ID 737618.1), however the database has already been successfully patched (and in fact even repatched) for this bug:
    $ORACLE_HOME/OPatch/opatch lsinventory
    Invoking OPatch 11.1.0.6.2
    Oracle Interim Patch Installer version 11.1.0.6.2
    Copyright (c) 2007, Oracle Corporation.  All rights reserved.
    Oracle Home       : /opt/oracle/db11g
    Central Inventory : /opt/oracle/inventory
       from           : /etc/oraInst.loc
    OPatch version    : 11.1.0.6.2
    OUI version       : 11.1.0.7.0
    OUI location      : /opt/oracle/db11g/oui
    Log file location : /opt/oracle/db11g/cfgtoollogs/opatch/opatch2010-06-02_08-23-53AM.log
    Lsinventory Output file location : /opt/oracle/db11g/cfgtoollogs/opatch/lsinv/lsinventory2010-06-02_08-23-53AM.txt
    Installed Top-level Products (2):
    Oracle Database 11g                                                  11.1.0.6.0
    Oracle Database 11g Patch Set 1                                      11.1.0.7.0
    There are 2 products installed in this Oracle Home.
    Interim patches (6) :
    Patch  6991626      : applied on Tue Jun 01 22:35:32 WET 2010
       Created on 14 Oct 2008, 23:25:07 hrs PST8PDT
       Bugs fixed:
         6991626
    [...]Does anyone have an idea on what might be the culprit here?
    Thanks for your help,
    Chris

    Hi Prathmesh,
    in fact I saw this very thread before and I made sure that both solutions were applied. Moreover as I said patch 6991626 had already been applied earlier, precisley to fix this problem, and I've had been able to successfully export other albeit somewhat smaller schemas (500M instead of 3GB) in the last few months. This is why I was so puzzled to see that exact bug raise its ugly head again. As far as I can tell I didn't do any modification to the DB since that last patch in nov. 2009. In fact the DB has been running pretty much untouched since then.
    I even tried yestereday to reinstalled the patch again; opatch does the operation gracefully, first rolling back the patch then reapplying it again, with only a warning about the patch being already present. However the pb does not get fixed any better.
    Thanks a lot for your help,
    Chris

  • 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

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

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

  • 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

  • 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

  • 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

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

Maybe you are looking for

  • How to create Custom error message in SharePoint 2013

    Hi, I have created one document library.On uploading the same file SharePoint throws error as"server error.The same file exit". But my requirement is not to show the SharePoint default message.I wanted to create custom message and show the pop up for

  • Navigation between the portals

    Hi Gurus, I have a unique requirement. I have a obiee 10g portal with LDAP authentication. In one of the nagivation links, I have to go to OBIEE 11g page with the same username and password. When I go to OBIEE 11g, it should not ask me the username/p

  • Error when installing drivers & software for Photosmart C410a

    Hi - I have a Photosmart C410a that I am trying to use with a 64-bit Windows 7 SP1 laptop, with an Intel i5-2520M CPU.  The printer was working with this laptop a while ago (back in March), but I applied a Windows update sometime in March, and since

  • HT201266 I updated my Visa card in is decline I need help please

    When I try to update my apps it said that I have a billing problem for a previous purcharse I never purchase anything that is not free,my visa card expired I try yo change to my updated card and said is decline

  • Does An Ipod Touch 5g need protection from scratches?

    Hi there, I've recently been pondering whether my ipod touch 5g needs a screen protector. I like using the ipod with just a silicone case over it, so basically it's just a black soft gel back.  There is no front facing protection, so I am using the s