An ORA-39126 error occurred while exporting through a database chain

This error occurs when you export or import tables in the 10.2.0.3 database using NETWORK_LINK in Oracle 11.2.0.2.

The detailed error is as follows:

[Oracle @ Oracle112 dmp] $ impdp system/password noLOGFILE = y tables = xyyzone. logs, xyyzone. logs, xyyzone. TAB_COMM_DISCOVERY_CONSUMER, xyyzone. painetwork_link = dblink2_pai_107;

Import: Release 11.2.0.2.0-Production on Wed Mar 16 04:44:36 2011

Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0-64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM ". "SYS_IMPORT_TABLE_01": system/******** noLOGFILE = y tables = xyyzone. TAB_COMM_DISCOVERY_QAHISTORY, xyyzone. TAB_COMM_DISCOVERY_VOTEHISTORY, xyyzone. TAB_COMM_DISCOVERY_CONSUMER, xyyzone. TAB_COMM_DISCOVERY_SHOPPING network_link = dblink2_assist_107
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-39126: Worker unexpected fatal error in KUPW $ WORKER. GET_TABLE_DATA_OBJECTS []
ORA-00920: invalid relational operator
ORA-06512: at "SYS. DBMS_METADATA", line 1546
ORA-06512: at "SYS. DBMS_METADATA", line 1583
ORA-06512: at "SYS. DBMS_METADATA", line 1891
ORA-06512: at "SYS. DBMS_METADATA", line 3956

ORA-06512: at "SYS. DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS. KUPW $ WORKER", line 8353

----- PL/SQL Call Stack -----
Object line object
Handle number name
0x136b50808 19208 package body SYS. KUPW $ WORKER
0x136b50808 8385 package body SYS. KUPW $ WORKER
0x136b50808 12748 package body SYS. KUPW $ WORKER
0x136b50808 4742 package body SYS. KUPW $ WORKER
0x136b50808 9110 package body SYS. KUPW $ WORKER
0x136b50808 1688 package body SYS. KUPW $ WORKER
0x137e37d68 2 anonymous block

Job "SYSTEM". "SYS_IMPORT_TABLE_01" stopped due to fatal error at 04:44:38

[Oracle @ Oracle112 dmp] $ expdp system/password directory = dmp dumpfile = export noLOGFILE = y tables = xyyzone. Large, xyyzone. Large network_link = dblink2_1__107

Export: Release 11.2.0.2.0-Production on Wed Mar 16 04:46:21 2011

Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0-64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM ". "SYS_EXPORT_TABLE_01": system/******** directory = dmp dumpfile = xyyzone_table_1102.16.dp noLOGFILE = y tables = xyyzone. TAB_COMM_DISCOVERY_QAHISTORY, xyyzone. TAB_COMM_DISCOVERY_VOTEHISTORY, xyyzone. TAB_COMM_DISCOVERY_CONSUMER, xyyzone. TAB_COMM_DISCOVERY_SHOPPING network_link = dblink2_assist_107
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 11.56 MB
ORA-39126: Worker unexpected fatal error in KUPW $ WORKER. UNLOAD_METADATA [TABLE_DATA: "XYYZONE". "TAB_COMM_POINTS_HISTORY": "YMAX"]
ORA-00920: invalid relational operator
ORA-06512: at "SYS. DBMS_METADATA", line 1546
ORA-06512: at "SYS. DBMS_METADATA", line 1583
ORA-06512: at "SYS. DBMS_METADATA", line 1891
ORA-06512: at "SYS. DBMS_METADATA", line 3956

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
0x136b50808 19208 package body SYS. KUPW $ WORKER
0x136b50808 8385 package body SYS. KUPW $ WORKER
0x136b50808 2935 package body SYS. KUPW $ WORKER
0x136b50808 9054 package body SYS. KUPW $ WORKER
0x136b50808 1688 package body SYS. KUPW $ WORKER
0x1358a19a0 2 anonymous block

Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 11.56 MB
ORA-39126: Worker unexpected fatal error in KUPW $ WORKER. UNLOAD_METADATA [TABLE_DATA: "XYYZONE". "TAB_COMM_POINTS_HISTORY": "YMAX"]
ORA-00920: invalid relational operator
ORA-06512: at "SYS. DBMS_METADATA", line 1546
ORA-06512: at "SYS. DBMS_METADATA", line 1583
ORA-06512: at "SYS. DBMS_METADATA", line 1891
ORA-06512: at "SYS. DBMS_METADATA", line 3956

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
0x136b50808 19208 package body SYS. KUPW $ WORKER
0x136b50808 8385 package body SYS. KUPW $ WORKER
0x136b50808 2935 package body SYS. KUPW $ WORKER
0x136b50808 9054 package body SYS. KUPW $ WORKER
0x136b50808 1688 package body SYS. KUPW $ WORKER
0x1358a19a0 2 anonymous block

Job "SYSTEM". "SYS_EXPORT_TABLE_01" stopped due to fatal error at 04:46:52

[Oracle @ Oracle112 dmp] $ expdp system/password directory = dmp dumpfile = xyyzone_table_1102.16.dp noLOGFILE = y tables = xyyzone. TAB_COMM_DISCOVERY_QAHISTORY, xyyzone. TAB_COMM_DISCOVERY_VOTEHISTORY, xyyzone. TAB_COMM_DISCOVERY_CONSUMER, xyyzone. TAB_COMM_DISCOVERY_SHOPPING network_link = dblink2_assist_107 version = 10.2.0.3

Export: Release 11.2.0.2.0-Production on Wed Mar 16 04:52:55 2011

Copyright (c) 1982,200 9, Oracle and/or its affiliates. All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0-64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SYSTEM ". "SYS_EXPORT_TABLE_02": system/******** directory = dmp dumpfile = xyyzone_table_1102.16.dp noLOGFILE = y tables = xyyzone. TAB_COMM_DISCOVERY_QAHISTORY, xyyzone. TAB_COMM_DISCOVERY_VOTEHISTORY, xyyzone. TAB_COMM_DISCOVERY_CONSUMER, xyyzone. TAB_COMM_DISCOVERY_SHOPPING network_link = dblink2_assist_107 version = 10.2.0.3
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 11.56 MB
ORA-39126: Worker unexpected fatal error in KUPW $ WORKER. UNLOAD_METADATA [TABLE_DATA: "XYYZONE". "TAB_COMM_POINTS_HISTORY": "YMAX"]
ORA-00920: invalid relational operator
ORA-06512: at "SYS. DBMS_METADATA", line 1546
ORA-06512: at "SYS. DBMS_METADATA", line 1583
ORA-06512: at "SYS. DBMS_METADATA", line 1891
ORA-06512: at "SYS. DBMS_METADATA", line 3956

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
0x136b50808 19208 package body SYS. KUPW $ WORKER
0x136b50808 8385 package body SYS. KUPW $ WORKER
0x136b50808 2935 package body SYS. KUPW $ WORKER
0x136b50808 9054 package body SYS. KUPW $ WORKER
0x136b50808 1688 package body SYS. KUPW $ WORKER
0x15b980c98 2 anonymous block

Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 11.56 MB
ORA-39126: Worker unexpected fatal error in KUPW $ WORKER. UNLOAD_METADATA [TABLE_DATA: "XYYZONE". "TAB_COMM_POINTS_HISTORY": "YMAX"]
ORA-00920: invalid relational operator
ORA-06512: at "SYS. DBMS_METADATA", line 1546
ORA-06512: at "SYS. DBMS_METADATA", line 1583
ORA-06512: at "SYS. DBMS_METADATA", line 1891
ORA-06512: at "SYS. DBMS_METADATA", line 3956

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
0x136b50808 19208 package body SYS. KUPW $ WORKER
0x136b50808 8385 package body SYS. KUPW $ WORKER
0x136b50808 2935 package body SYS. KUPW $ WORKER
0x136b50808 9054 package body SYS. KUPW $ WORKER
0x136b50808 1688 package body SYS. KUPW $ WORKER
0x15b980c98 2 anonymous block

Job "SYSTEM". "SYS_EXPORT_TABLE_02" stopped due to fatal error at 04:53:25

As you can see, whether you try IMPDP direct import, or try to use EXPDP for remote export, will encounter ORA-39126 and ORA-920 errors. The version 10.2.0.3 is specified during the export attempt. the problem persists.

Check metalink and confirm it is Bug 10115400. When NETWORK_LINK is used to import or export data, if the remote database version is 10.2 and multiple TABLES are specified through the TABLES parameter, this problem occurs. This problem may occur in versions 11.2. Oracle plans to solve this problem in 12.1.

This error has little impact, but it is a little troublesome. You need to export the corresponding table in the source database, ftp to the local, and then import it through impdp.