ORA-39126 during an export of a partition via dbms_datapump

Hi ,
i did export using datapump in command line everything went fine but while exporting via dbms_datapump i got this:
ORA-39126 during an export of a partition via dbms_datapump
ORA-00920
'SELECT FROM DUAL WHERE :1' P20060401
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6228
the procedure is:
PROCEDURE pr_depura_bitacora
IS
l_job_handle NUMBER;
l_job_state VARCHAR2(30);
l_partition VARCHAR2(30);
v_sql VARCHAR2(2000);
BEGIN
-- Create a user-named Data Pump job to do a "table:partition-level" export
-- Local
select 'P'|| to_char((select min(STP_LOG_DATE) from SAI_AUDITBITACORA),'YYYYMM')||'01'
into l_partition
from user_tab_partitions
where table_name = 'SAI_AUDITBITACORA'
and rownum = 1;
l_partition := rtrim (l_partition,' ');
l_job_handle:= DBMS_DATAPUMP.OPEN
operation=>'EXPORT',
job_mode =>'TABLE',
job_name =>'EXPORT_ORACLENSSA'
-- Schema filter
DBMS_DATAPUMP.METADATA_FILTER
handle => l_job_handle,
name => 'SCHEMA_EXPR',
value => 'IN (''ORACLENSSA'')'
DBMS_OUTPUT.PUT_LINE('Added filter for schema list');
-- Table filter
DBMS_DATAPUMP.METADATA_FILTER
handle => l_job_handle,
name => 'NAME_EXPR',
value => '=''SAI_AUDITBITACORA'''
DBMS_OUTPUT.PUT_LINE('Added filter for table expression');
-- Partition filter
DBMS_DATAPUMP.DATA_FILTER
handle => l_job_handle,
name => 'PARTITION_EXPR',
value => l_partition,
table_name => 'SAI_AUDITBITACORA'
DBMS_OUTPUT.PUT_LINE('Partition filter for schema list');
DBMS_DATAPUMP.ADD_FILE
handle => l_job_handle,
filename => 'EXP'||l_partition||'.DMP',
directory => 'EXP_DATA_PUMP',
filetype => 1
DBMS_DATAPUMP.ADD_FILE
handle => l_job_handle,
filename => 'EXP'||l_partition||'.LOG',
directory => 'EXP_DATA_PUMP',
filetype => 3
DBMS_DATAPUMP.START_JOB
handle => l_job_handle,
skip_current => 0
DBMS_DATAPUMP.WAIT_FOR_JOB
handle => l_job_handle,
job_state => l_job_state
DBMS_OUTPUT.PUT_LINE('Job completed - job state = '||l_job_state);
DBMS_DATAPUMP.DETACH(handle=>l_job_handle);
END;
I've already drop and recreate the directory, granted read, write to public and to user, grant create session, create table, create procedure, exp_full_database to user, restart the database and the listener with the var LD_LIBRARY pointing first to $ORACLE_HOME/lib, and add more space to temporary tablespace.

The basic problem is:
Error: ORA 920
Text: invalid relational operator
Cause: A search condition was entered with an invalid or missing relational
operator.
Action: Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=
, ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT]
LIKE in the condition.
Obviously this refers to the invalid statement 'SELECT FROM DUAL ...'. I also recommend, you should contact Oracle Support, because it happens inside an Oracle provided package.
Werner

Similar Messages

  • 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

  • How to desactivate error ORA-39181 during expdp schema export.

    Hi all,
    Is it possible to NOT have ORA-39181 in log file during expdp export?
    In my case, I have a lot of ORA-39181 errors, and these errors can easily mask other errors...
    Tahnsk for your help,
    Regards,
    Elodie

    From oerr:
    $ oerr ora 39181
    39181, 0000, "Only partial table data may be exported due to fine grain access control on %s"
    // *Cause:  An unprivileged user has tried to export a table that has fine
    //          grain access control. The table owner is subjected to access
    //          control and may not be able to export all rows in the table.
    //          Only the rows that can be seen by that user will be exported. In
    //          order to preserve integrity of the table, the user importing the
    //          table should have enough privilege to recreate the table with the
    //          security policies at import time.
    // *Action: It is strongly recommended that the database administrator handle
    //          exporting of this table.HTH
    Amardeep Sidhu
    http://amardeepsidhu.com/blog

  • ORA-04031 during export on CTX-index

    Hi !
    I get ORA-04031 during export when an interMedia CTX-Index should get exported. The exact error message is:
    unable to allocate 4072 bytes of shared memory ("shared pool", "DBMS_SYS_SQL", "PL/SQL MPCODE", "BAMIMA: BAM Buffer")
    followed by
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: in "SYS.DBMS_SQL", line 9
    ORA-06512: in "SYS.DBMS_EXPORT_EXTENSION", line 244
    Any hints for me what I could do?
    TIA,
    Stefan

    Interesting.  You should open a  thread with a more relevant title about views with pk / fk constraints.
    I don't have a way to solve your problem --- to identify such views.
    Hemant K Chitale

  • Ora-1555 during exports and imports. possible causes. ?

    From my understanding : I know that this error will occur due to a undo retention being smaller sizer. or rather I should put it that increasing this parameter should help fix the issue.
    Whats not clear is below :
    Qn. Is it possible that ORA-1555 errors can occur during 'import' even if no other sessions are connected and performing any transaction/dmls ?
    Qn. Also why does a ORA-1555 occur during a 'export' ? Is the same reasons ie. there could be possible DMLs occuring ?

    Hello,
    About your first question:
    Qn. Is it possible that ORA-1555 errors can occur during 'import' even if no other sessions are connected and performing any transaction/dmls ?I've never got this error during import but, I always care to get enough place on the UNDO Tablespace.
    With classical import you have a commit after each Table's import (by default) and a commit after each row's import if COMMIT=Y so as to use less space in the Rollback Segment.
    With Datapump, I often decrease the undo_retention parameter before importing so as to use less space on the UNDO Tablespace.
    About the second question:
    Qn. Also why does a ORA-1555 occur during a 'export' ? Is the same reasons ie. there could be possible DMLs occuring ?To get a consistent image of the exported data with the classical export you may use the parameter CONSISTENT=Y. While you may use the FLASHBACK_TIME parameter with Datapump (so it means that the undo_retention should be large enough when exporting).
    Both use the Undo entries, so I imagine that's possible to get some error (may be ORA-01555) if you don't have enough place on your UNDO Tablespace.
    It's possible (thank to the Rollback Segments) to have concurrent DML on the database while exporting.
    Anyway, from my point of view, while exporting or importing if you have enough space on your UNDO tablespace and a correct undo_retention setting (not too large when importing not too small when exporting) it should be fine.
    Hope this help.
    Best regards,
    Jean-Valentin

  • ORA-29540 during full database export

    Hi,
    Anyone encounter this error ORA-29540 during full database export. Have check out the web site for solution. Have check that the init file compatible is set to 8.1.0, the public synonym dba_java is been removed. However after the above remedies, the problem still occured. My database version is 8.1.5. Please let me know if there is other solution to this problem.
    Thank You ...
    regards,
    lbs

    Hi,
    Thanks...Any idea how to check whether the installation for the initjvm.sql is successful. cos I just took over from the previous DBA and he too have no idea...
    Thank You..

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

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

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

  • Expdp fail with ORA-39126 error

    When i trying to export partition table it throws following error. I have tried it with newly created table also. but still it gets fail. My DB version is: 11.1.0.6.0 (RAC)
    [oracle@db2 ORADATA8]$
    [oracle@db2 ORADATA8]$
    [oracle@db2 ORADATA8]$ ls -l
    total 8
    drwxr-xr-x 2 oracle oinstall 8192 Jul 1 11:16 CRESTELDATA
    drwxr-xr-x 2 oracle oinstall 3896 Jul 3 11:21 DATAPUMP
    drwxr-xr-x 2 oracle oinstall 3896 Feb 18 11:23 lost+found
    [oracle@db2 ORADATA8]$
    [oracle@db2 ORADATA8]$
    [oracle@db2 ORADATA8]$ expdp CRESTELMEDIATIONPRD501/CRESTELMEDIATIONPRD501 tables=TBLINVALIDCDR:PSINVALIDCDR18APR2010 DIRECTORY=ORADATA8 PARALLEL=5 COMPRESSION=ALL DUMPFILE=INVALIDCDR_%U.dmp LOGFILE=expdpINVALIDCDR.log
    Export: Release 11.1.0.6.0 - 64bit Production on Saturday, 03 July, 2010 11:24:34
    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Connected to: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, Real Application Clusters, OLAP, Data Mining
    and Real Application Testing options
    Starting "CRESTELMEDIATIONPRD501"."SYS_EXPORT_TABLE_03": CRESTELMEDIATIONPRD501/******** tables=TBLINVALIDCDR:PSINVALIDCDR18APR2010 DIRECTORY=ORADATA8 PARALLEL=5 COMPRESSION=ALL DUMPFILE=INVALIDCDR_%U.dmp LOGFILE=expdpINVALIDCDR.log
    Estimate in progress using BLOCKS method...
    Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
    Total estimation using BLOCKS method: 3.917 GB
    Processing object type TABLE_EXPORT/TABLE/TABLE
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CREATE_OBJECT_ROWS [TABLE:"CRESTELMEDIATIONPRD501"."TBLINVALIDCDR"]
    ORA-01114: IO error writing block to file 6 (block # 79240)
    ORA-29701: unable to connect to Cluster Manager
    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
    0x21ac5fc60 18051 package body SYS.KUPW$WORKER
    0x21ac5fc60 7736 package body SYS.KUPW$WORKER
    0x21ac5fc60 6945 package body SYS.KUPW$WORKER
    0x21ac5fc60 2519 package body SYS.KUPW$WORKER
    0x21ac5fc60 8342 package body SYS.KUPW$WORKER
    0x217190f58 1 anonymous block
    0x217687e98 1501 package body SYS.DBMS_SQL
    0x21ac5fc60 8201 package body SYS.KUPW$WORKER
    0x21ac5fc60 1477 package body SYS.KUPW$WORKER
    0x21ac60350 2 anonymous block
    Processing object type TABLE_EXPORT/TABLE/TABLE
    Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX
    Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
    Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
    . . exported "CRESTELMEDIATIONPRD501"."TBLINVALIDCDR":"PSINVALIDCDR18APR2010"."TER418APR2010" 36.27 MB 723142 rows
    . . exported "CRESTELMEDIATIONPRD501"."TBLINVALIDCDR":"PSINVALIDCDR18APR2010"."TER218APR2010" 16.13 MB 325123 rows
    . . exported "CRESTELMEDIATIONPRD501"."TBLINVALIDCDR":"PSINVALIDCDR18APR2010"."TER318APR2010" 512.3 KB 10467 rows
    . . exported "CRESTELMEDIATIONPRD501"."TBLINVALIDCDR":"PSINVALIDCDR18APR2010"."TER118APR2010" 556.2 MB 12261974 rows
    Master table "CRESTELMEDIATIONPRD501"."SYS_EXPORT_TABLE_03" successfully loaded/unloaded
    Dump file set for CRESTELMEDIATIONPRD501.SYS_EXPORT_TABLE_03 is:
    /ORADATA8/DATAPUMP/INVALIDCDR_01.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_02.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_03.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_04.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_05.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_06.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_07.dmp
    /ORADATA8/DATAPUMP/INVALIDCDR_08.dmp
    Job "CRESTELMEDIATIONPRD501"."SYS_EXPORT_TABLE_03" completed with 3 error(s) at 11:26:36
    Please - reply
    Edited by: Yuvraj on Jul 3, 2010 1:13 PM

    Hi,
    It seems that you have got a problematic disk there. There might be a problem with the disk that the datafile resides on since you are receiving I/O errors. Moreoever, there might be a problem with the CSS. check that all the process of cluster are running.
    regards

  • 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-39779 during import of types

    Hi ,
    I have executed an export with the following parameters:
    DIRECTORY=DATAPUMP_DIR
    DUMPFILE=exportdp_FULL_%U.dmp
    LOGFILE=exportdp_FULL.log
    FLASHBACK_SCN=6070655498233
    FULL=yes
    CONTENT=ALL
    FILESIZE=2G
    PARALLEL=2
    The source database is of release 10.2.0.4.0 and installed on a HP-UX (HP-UX 11.23) environment.
    The target database is of release 10.2.0.5.0 and installed on Red Hat Linux (Red Hat Enterprise Linux Server release 5.8 ) environment.
    The parameterfile for the import has the following parameters:
    DUMPFILE=exportdp_FULL_%U.dmp
    LOGFILE=importdp_FULL.log
    SCHEMAS=schema_a, schema_b, schema_c, schema_d
    REMAP_TABLESPACE=DEFAULTUSER:DEFAULT_USER
    PARALLEL=4
    METRICS=yes
    During the import the following errors get raised:
    ORA-31693: Table data object "SCHEMA_A"."TEST" failed to load/unload and is being skipped due to error:
    ORA-02354: error in exporting/importing data
    ORA-39779: type "SCHEMA_A"."OT_TEST" not found or conversion to latest version is not possible
    Going through MOS and several forums none of the offered solutions (e.g. TRANSFORM=oid:n) solved this issue.
    Currently I really don't have idea how to solve this issue - it's not clear to me what causes the problem. Running the query
    SELECT o.oid$
    , t.hashcode
    , o.name
    FROM sys.obj$ o
    , sys.user$ u
    , sys.type$ t
    WHERE o.owner# = u.user#
    AND o.oid$ = t.toid
    AND o.name = 'OT_TEST';
    gives different results on source- and target-database (oid and hashcode do both differ).
    Any help will truly appreciated.
    Rgds
    Jan

    Hi ,
    expdp command:
    expdp sys_admin parfile=exportdp_FULL.param;
    first 15 lines of exportdp_FULL.log:
    Export: Release 10.2.0.4.0 - 64bit Production on Mittwoch, 06 Februar, 2013 7:35:52
    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    Starting "SYS_ADMIN"."SYS_EXPORT_FULL_01": sys_admin/******** parfile=exportdp_FULL.param
    Estimate in progress using BLOCKS method...
    Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
    Total estimation using BLOCKS method: 199.2 GB
    Processing object type DATABASE_EXPORT/TABLESPACE
    Processing object type DATABASE_EXPORT/PROFILE
    Processing object type DATABASE_EXPORT/SYS_USER/USER
    Processing object type DATABASE_EXPORT/SCHEMA/USER
    Processing object type DATABASE_EXPORT/ROLE
    Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
    Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
    Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
    Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
    Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
    impdp command:
    impdp sys_admin parfile=importdp_FULL.param;
    first 15 lines of importdp_FULL.log:
    Import: Release 10.2.0.5.0 - 64bit Production on Thursday, 07 February, 2013 12:53:58
    Copyright (c) 2003, 2007, Oracle. All rights reserved.
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
    With the Partitioning, Real Application Clusters, OLAP, Data Mining
    and Real Application Testing options
    Master table "SYS_ADMIN"."SYS_IMPORT_SCHEMA_02" successfully loaded/unloaded
    Starting "SYS_ADMIN"."SYS_IMPORT_SCHEMA_02": sys_admin/******** parfile=importdp_FULL.param
    Processing object type DATABASE_EXPORT/SCHEMA/USER
    Failing sql is:
    CREATE USER "SCHEMA_A" IDENTIFIED BY VALUES 'A3E66F1F8E9EFE4E' DEFAULT TABLESPACE "DATA" TEMPORARY TABLESPACE "TEMP" PROFILE "SCHEMA_OWNER"
    ORA-31684: Object type USER:"SCHEMA_A" already exists
    ORA-31684: Object type USER:"SCHEMA_B" already exists
    ORA-39083: Object type USER failed to create with error:
    ORA-02380: profile TECHNICAL_USER does not exist
    The errors of the import are due to the fact that I have created all users before...
    Rgds
    Jan

  • Unable to retrieve nametab info for logic table BSEG during Database Export

    Hi,
    Our aim is to Migrate to New hardware and do the Database Export of the existing System(Unicode) and Import the same in the new Hardware
    I am doing Database Export on SAP 4.7 SR1,HP-UX ,Oracle 9i(Unicode System) and during Database Export "Post Load Processing phase" got the error as mentioned in SAPCLUST.log
    more SAPCLUST.log
    /sapmnt/BIA/exe/R3load: START OF LOG: 20090216174944
    /sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
    $ SAP
    /sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 13 2007 16:20:31
    /sapmnt/BIA/exe/R3load -ctf E /nas/biaexp2/DATA/SAPCLUST.STR /nas/biaexp2/DB/DDLORA.T
    PL /SAPinst_DIR/SAPCLUST.TSK ORA -l /SAPinst_DIR/SAPCLUST.log
    /sapmnt/BIA/exe/R3load: job completed
    /sapmnt/BIA/exe/R3load: END OF LOG: 20090216174944
    /sapmnt/BIA/exe/R3load: START OF LOG: 20090216182102
    /sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
    $ SAP
    /sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 13 2007 16:20:31
    /sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
    R/SAPCLUST.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "BIA20071101021156                                                                               
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "tinsp041                                                    
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "tinsp041"
    (GSI) INFO: release  = "B.11.11"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "9000/800"
    (GSI) INFO: instno   = "0020293063"
    (EXP) TABLE: "AABLG"
    (EXP) TABLE: "CDCLS"
    (EXP) TABLE: "CLU4"
    (EXP) TABLE: "CLUTAB"
    (EXP) TABLE: "CVEP1"
    (EXP) TABLE: "CVEP2"
    (EXP) TABLE: "CVER1"
    (EXP) TABLE: "CVER2"
    (EXP) TABLE: "CVER3"
    (EXP) TABLE: "CVER4"
    (EXP) TABLE: "CVER5"
    (EXP) TABLE: "DOKCL"
    (EXP) TABLE: "DSYO1"
    (EXP) TABLE: "DSYO2"
    (EXP) TABLE: "DSYO3"
    (EXP) TABLE: "EDI30C"
    (EXP) TABLE: "EDI40"
    (EXP) TABLE: "EDIDOC"
    (EXP) TABLE: "EPIDXB"
    (EXP) TABLE: "EPIDXC"
    (EXP) TABLE: "GLS2CLUS"
    (EXP) TABLE: "IMPREDOC"
    (EXP) TABLE: "KOCLU"
    (EXP) TABLE: "PCDCLS"
    (EXP) TABLE: "REGUC"
    myCluster (55.16.Exp): 1557: inconsistent field count detected.
    myCluster (55.16.Exp): 1558: nametab says field count (TDESCR) is 305.
    myCluster (55.16.Exp): 1561: alternate nametab says field count (TDESCR) is 304.
    myCluster (55.16.Exp): 1250: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 8033: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 2624: failed to convert cluster data of cluster item.
    myCluster: RFBLG      *003**IN07**0001100000**2007*
    myCluster (55.16.Exp): 318: error during conversion of cluster item.
    myCluster (55.16.Exp): 319: affected physical table is RFBLG.
    (CNV) ERROR: data conversion failed.  rc = 2
    (RSCP) WARN: env I18N_NAMETAB_TIMESTAMPS = IGNORE
    (DB) INFO: disconnected from DB
    /sapmnt/BIA/exe/R3load: job finished with 1 error(s)
    /sapmnt/BIA/exe/R3load: END OF LOG: 20090216182145
    /sapmnt/BIA/exe/R3load: START OF LOG: 20090217115935
    /sapmnt/BIA/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#20
    $ SAP
    /sapmnt/BIA/exe/R3load: version R6.40/V1.4 [UNICODE]
    Compiled Aug 13 2007 16:20:31
    /sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
    R/SAPCLUST.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
    (GSI) INFO: dbname   = "BIA20071101021156                                                                               
    (GSI) INFO: vname    = "ORACLE                          "
    (GSI) INFO: hostname = "tinsp041                                                    
    (GSI) INFO: sysname  = "HP-UX"
    (GSI) INFO: nodename = "tinsp041"
    (GSI) INFO: release  = "B.11.11"
    (GSI) INFO: version  = "U"
    (GSI) INFO: machine  = "9000/800"
    (GSI) INFO: instno   = "0020293063"
    myCluster (55.16.Exp): 1557: inconsistent field count detected.
    myCluster (55.16.Exp): 1558: nametab says field count (TDESCR) is 305.
    myCluster (55.16.Exp): 1561: alternate nametab says field count (TDESCR) is 304.
    myCluster (55.16.Exp): 1250: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 8033: unable to retrieve nametab info for logic table BSEG   
    myCluster (55.16.Exp): 2624: failed to convert cluster data of cluster item.
    myCluster: RFBLG      *003**IN07**0001100000**2007*
    myCluster (55.16.Exp): 318: error during conversion of cluster item.
    myCluster (55.16.Exp): 319: affected physical table is RFBLG.
    (CNV) ERROR: data conversion failed.  rc = 2
    (RSCP) WARN: env I18N_NAMETAB_TIMESTAMPS = IGNORE
    (DB) INFO: disconnected from DB
    SAPCLUST.l/sapmnt/BIA/exe/R3load: job finished with 1 error(s)
    /sapmnt/BIA/exe/R3load: END OF LOG: 20090217115937
    og (97%)
    The main eror is "unable to retrieve nametab info for logic table BSEG "  
    Your reply to this issue is highly appreciated
    Thanks
    Sunil

    Hello,
    acording to this output:
    /sapmnt/BIA/exe/R3load -datacodepage 1100 -e /SAPinst_DIR/SAPCLUST.cmd -l /SAPinst_DI
    R/SAPCLUST.log -stop_on_error
    you are doing the export with a non-unicode SAP codepage. The codepage has to be 4102/4103 (see note #552464 for details). There is a screen in the sapinst dialogues that allows the change of the codepage. 1100 is the default in some sapinst versions.
    Best Regards,
    Michael

  • EXP-00008 + ORA-06544 + ORA-06553 + ORA-06508 error while exporting schema

    HI,
    i am exporting schema defnition from database;
    bash-2.05$ exp userid=pin/pin file=pin.dmp log=pin.log owner=pin rows=no
    i am getting this error:
    Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production
    With the Partitioning option
    JServer Release 8.1.7.0.0 - 64bit Production
    Export done in US7ASCII character set and UTF8 NCHAR character set
    server uses UTF8 character set (possible charset conversion)
    Note: table data (rows) will not be exported
    About to export specified users ...
    . exporting pre-schema procedural objects and actions
    EXP-00008: ORACLE error 6544 encountered
    ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [56319]
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
    . exporting foreign function library names for user PIN
    . exporting object type definitions for user PIN
    About to export PIN's objects ...
    . exporting database links
    . exporting sequence numbers
    . exporting cluster definitions
    . about to export PIN's tables via Conventional Path ...
    . . exporting table 109_31OCT2008
    . . exporting table 109_gl_juntooct2008
    . . exporting table ACCOUNT_BALANCES_BACKUP_T
    . . exporting table ACCOUNT_BALANCES_T
    . . exporting table ACCOUNT_BALANCES_THRESHOLDS_T
    . . exporting table ACCOUNT_BALANCES_T_06NOV01
    . . exporting table ACCOUNT_BALANCES_T_31MAR07
    . . exporting table ACCOUNT_EXEMPTIONS_T
    . . exporting table ACCOUNT_INTERNAL_NOTES_BUF
    :. exporting synonyms
    . exporting views
    . exporting stored procedures
    . exporting operators
    . exporting referential integrity constraints
    . exporting triggers
    . exporting indextypes
    . exporting bitmap, functional and extensible indexes
    . exporting posttables actions
    . exporting snapshots
    . exporting snapshot logs
    . exporting job queues
    . exporting refresh groups and children
    . exporting dimensions
    . exporting post-schema procedural objects and actions
    EXP-00008: ORACLE error 6544 encountered
    ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [56319]
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
    . exporting statistics
    Export terminated successfully with warnings.
    please could any body guide me what is the exact problem.
    Thanks
    Prakash

    Hi,
    bash-2.05$ exp pin/pin file=mypinfile.dmp log=mypinfile.log rows=N
    Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - 64bit Production
    With the Partitioning option
    JServer Release 8.1.7.0.0 - 64bit Production
    Export done in US7ASCII character set and UTF8 NCHAR character set
    server uses UTF8 character set (possible charset conversion)
    Note: table data (rows) will not be exported
    About to export specified users ...
    . exporting pre-schema procedural objects and actions
    EXP-00008: ORACLE error 6544 encountered
    ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [56319]
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
    . exporting foreign function library names for user PIN
    . exporting object type definitions for user PIN
    About to export PIN's objects ...
    . exporting database links
    . exporting sequence numbers
    . exporting cluster definitions
    . about to export PIN's tables via Conventional Path ...
    . . exporting table 109_31OCT2008
    . . exporting table 109_gl_juntooct2008
    . . exporting table ACCOUNT_BALANCES_BACKUP_T
    . . exporting table ACCOUNT_BALANCES_T
    . . exporting table ACCOUNT_BALANCES_THRESHOLDS_T
    . . exporting table ACCOUNT_BALANCES_T_06NOV01
    .. . exporting table YOU_VRC_TRANS_DETAILS_T
    . . exporting table YOU_VRC_TRANS_T
    . . exporting table ZONEMAP_DATA_DERIVED_T
    . . exporting table ZONEMAP_DATA_RAW_T
    . . exporting table ZONEMAP_T
    . . exporting table cust_balance19
    . . exporting table cust_balance_ason_19June12AM
    . exporting synonyms
    . exporting views
    . exporting stored procedures
    . exporting operators
    . exporting referential integrity constraints
    . exporting triggers
    . exporting indextypes
    . exporting bitmap, functional and extensible indexes
    . exporting posttables actions
    . exporting snapshots
    . exporting snapshot logs
    . exporting job queues
    . exporting refresh groups and children
    . exporting dimensions
    . exporting post-schema procedural objects and actions
    EXP-00008: ORACLE error 6544 encountered
    ORA-06544: PL/SQL: internal error, arguments: [56319], [], [], [], [], [], [], []
    ORA-06553: PLS-801: internal error [56319]
    ORA-06508: PL/SQL: could not find program unit being called
    ORA-06512: at line 1
    EXP-00083: The previous problem occurred when calling SYS.DBMS_REPCAT_RGT_EXP.schema_info_exp
    . exporting statistics
    Export terminated successfully with warnings.
    i think it some problem with SYS.DBMS_REPCAT_RGT_EXP package
    SQL> select status, object_type, LAST_DDL_TIME from dba_objects where object_name='DBMS_REPCAT_RGT_EXP';
    STATUS OBJECT_TYPE LAST_DDL_
    VALID PACKAGE 25-DEC-08
    INVALID PACKAGE BODY 02-SEP-01
    Thanks
    Prakash
    T

  • ORA-3113 while running export (first run ok, second run fails)

    Hi,
    I'm running 10g (10.1.0.2.0) on gentoo Linux.
    After a restart of the database I can do an EXP for any user without errors. But when I repeat the same command after the export I get the following error:
    . . exporting table WEB_SESSION_DATA 0 rows exported
    . exporting synonyms
    EXP-00008: ORACLE error 3113 encountered
    ORA-03113: end-of-file on communication channel
    EXP-00000: Export terminated unsuccessfully
    It's always the same error on the same task (exporting synonyms) but always just for the second and any later export, while the first one is ok.
    I read through some forums and found, that ORA-3113 is a standard error which just hides the real error. So I look into the trace files and found:
    ksedmp: internal or fatal error
    ORA-07445: exception encountered: core dump [jox_lookup_known_object()+413] [SIGSEGV] [Address not mapped to object] [0x1AD14034] [] []
    Current SQL statement for this session:
    SELECT SYNNAM, DBMS_JAVA.LONGNAME(SYNNAM), DBMS_JAVA.LONGNAME(SYNTAB), TABOWN, TABNODE, PUBLIC$, SYNOWN, SYNOWNID, TABOWNID, SYNOBJNO FROM SYS.EXU9SYN WHERE SYNOWNID = :1 ORDER BY SYNTIME
    If I call this SQL from sqlplus I get the same ORA-3113, so this seems to be the cause for the export failure.
    When I remove the DBMS_JAVA.LONGNAME calls from the statement, it runs fine. It also runs fine, when I add a "and 1=0" to the EXU9SYN view. But this will not really solve the problem, because then all synonyms don't get exported.
    I also checked all the synonyms and they are valid, the referenced tables exist and can be queried.
    Because we use JavaStoredProcedures I cannot remove the Java Features in Oracle. But I reinstalled it (rmjvm.sql and initjvm.sql) but this did not help.
    Does anyone have an idea what's happening here?
    Especially the "first run ok, second run fails" seems to be very strange, because DB objects including DBMS_JAVA should be ok, if the first export can be done. So what changes in the database during or after the first run?

    Maybe description for bug 3953108 (ORA-7445 AND ORA-3113 DURING DIRECT FULL DATABASE EXPORT OF PUBLIC SYNONYMS) is helpful.
    Werner

  • Getting an ORA-39126 when importing

    When i am doing
    Connected to: Oracle Database 10g Release 10.2.0.3.0 - Production
    Master table "SYSTEM"."SYS_IMPORT_SCHEMA_02" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_SCHEMA_02":  system/********@o10g directory=my_imp_dir CONTENT=ALL TABLE_EXISTS_ACTION=REPLACE dumpfile=*****.dmp logfile=my_log_dir:imp.log schemas=e5_database REMAP_TABLESPACE=******:ERGO_USR REMAP_TABLESPACE=*****:ERGO_INDX
    Processing object type DATABASE_EXPORT/SCHEMA/USER
    i get the following error.
    +ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDL [FUNCTION:"E5_DA+
    TABASE"."GET_DB_VERSION"]
    ORA-44001: invalid schema
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPW$WORKER", line 6266
    ----- PL/SQL Call Stack -----
    object      line  object
    handle    number  name
    +22BD2830 14916 package body SYS.KUPW$WORKER+
    +22BD2830 6293 package body SYS.KUPW$WORKER+
    +22BD2830 12689 package body SYS.KUPW$WORKER+
    +22BD2830 11969 package body SYS.KUPW$WORKER+
    +22BD2830 3278 package body SYS.KUPW$WORKER+
    +22BD2830 6882 package body SYS.KUPW$WORKER+
    +22BD2830 1259 package body SYS.KUPW$WORKER+
    +229C03C4 2 anonymous block+
    Job "SYSTEM"."SYS_IMPORT_SCHEMA_02" stopped due to fatal error at 15:00:52
    how can i fix this?
    is it possible that the export was done on a different version and that causes the problems ?

    Welcome to the forums !
    You may be running into a bug mentioned in MOS Doc 742343.1 (Ora-39126: Worker Unexpected Fatal Error In Kupw$Worker.Put_ddl and ORA-44001)
    HTH
    Srini

  • ORA-39126 when attempting expdp with network_link

    I'm trying to use expdp to get a dump of a db on another box so I can duplicate it on my dev machine.
    I created a network link using :
    create public database link preprodlink connect to "TESTUSER" identified by "testpass" using '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=my.machine.eu)(PORT=1521)))(CONNECT_DATA=(SID=PREPRODSID)))';
    I have verified that this seems ok by doing :
    select * from dual@preprodlink;
    which runs successfully.
    I then created a local user to match the schema with :
    create user TESTUSER identified by testpass;
    grant all privileges to TESTUSER;
    I then attempt to do the actual export using
    expdp TESTUSER/testpass directory=oratmp network_link=preprodlink dumpfile=TESTUSER.dmp schemas=TESTUSER exclude=statistics
    But I get error ORA-39126 and PLS-00201.
    I can't figure out what the problem is.
    Full export log is below :
    Export: Release 11.2.0.2.0 - Production on Wed Sep 12 04:08:58 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    Connected to: Oracle Database 11g Express Edition Release 11.2.0.2.0 - Production
    Starting "TESTUSER"."SYS_EXPORT_SCHEMA_02": TESTUSER/******** directory=oratmp network_link=preprodlink dumpfile=TESTUSER.dmp schemas=TESTUSER exclude=statistics
    Estimate in progress using BLOCKS method...
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD [ESTIMATE_PHASE]
    ORA-06550: line 1, column 13:
    PLS-00201: identifier 'DBMS_METADATA.NETWORK_OPEN@PREPRODLINK' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    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
    4B5C9DC0 19208 package body SYS.KUPW$WORKER
    4B5C9DC0 8385 package body SYS.KUPW$WORKER
    4B5C9DC0 6628 package body SYS.KUPW$WORKER
    4B5C9DC0 12605 package body SYS.KUPW$WORKER
    4B5C9DC0 2546 package body SYS.KUPW$WORKER
    4B5C9DC0 9054 package body SYS.KUPW$WORKER
    4B5C9DC0 1688 package body SYS.KUPW$WORKER
    5113DAC8 2 anonymous block
    Estimate in progress using BLOCKS method...
    Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.CONFIGURE_METADATA_UNLOAD [ESTIMATE_PHASE]
    ORA-06550: line 1, column 13:
    PLS-00201: identifier 'DBMS_METADATA.NETWORK_OPEN@PREPRODLINK' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    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
    4B5C9DC0 19208 package body SYS.KUPW$WORKER
    4B5C9DC0 8385 package body SYS.KUPW$WORKER
    4B5C9DC0 6628 package body SYS.KUPW$WORKER
    4B5C9DC0 12605 package body SYS.KUPW$WORKER
    4B5C9DC0 2546 package body SYS.KUPW$WORKER
    4B5C9DC0 9054 package body SYS.KUPW$WORKER
    4B5C9DC0 1688 package body SYS.KUPW$WORKER
    5113DAC8 2 anonymous block
    Job "TESTUSER"."SYS_EXPORT_SCHEMA_02" stopped due to fatal error at 04:09:13

    Oh well,
    SQL> desc dbms_metadata
    FUNCTION ADD_TRANSFORM RETURNS NUMBER
    ....Other than that, the point was what Dean says; check remote db (invalid packages, etc.). Involve remote db's dba. Is it possible to run export db locally on the remote db?
    For invalid objects, try something like
    select object_name, object_type from dba_objects where status != 'VALID';
    edit:
    forum ate not equal
    Edited by: orafad on Sep 13, 2012 3:49 PM
    Edited by: orafad on Sep 13, 2012 7:38 PM

Maybe you are looking for