IMPDP with network_link option fails with ORA-39126, ORA-06502, ORA-39127, ORA-44002

Some day before while performing import operation using IMPDP using network_link parameter, I came across this issue.

My IMPDP command was as given below:


I got following error, before it got terminated due to fatal error:

ORA-39127: unexpected error from call to "SYS"."DBMS_CUBE_EXP"."INSTANCE_EXTENDED_INFO_EXP"
ORA-44002: invalid object name
ORA-06512: at "SYS.DBMS_ASSERT", line 316
ORA-06512: at "SYS.DBMS_METADATA", line 9114
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [PROCACT_SCHEMA:"XXDBA"]
ORA-06502: PL/SQL: numeric or value error: invalid LOB locator specified: ORA-22275
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
 object line object
 handle number name
5408b1e60 20462 package body SYS.KUPW$WORKER
5408b1e60 9028 package body SYS.KUPW$WORKER
5408b1e60 10935 package body SYS.KUPW$WORKER
5408b1e60 2728 package body SYS.KUPW$WORKER
5408b1e60 9697 package body SYS.KUPW$WORKER
5408b1e60 1775 package body SYS.KUPW$WORKER
54eda2e28 2 anonymous block
Job "SYSTEM"."SYS_IMPORT_FULL_02" stopped due to fatal error at 17:10:20

Tried excluding schema XXDBA …. but same issue 😦

After searching on MOS, I got number for notes regarding same error, in which this note was explaining exact scenario which I got : DataPump Export (EXPDP) Errors ORA-39127 SYS.DBMS_CUBE_EXP.INSTANCE_EXTENDED_INFO_EXP ORA-44002 After Upgrade (Doc ID 1353491.1)

This note has given following solution:

The issue directs to an incomplete OLAP installation issue or orphan OLAP objects. If the OLAP option is not used, then delete DBMS_CUBE_EXP OLAP package from the export view as follows:
connect / as sysdba
create table exppkgact$_bck as select * from sys.exppkgact$;
delete from sys.exppkgact$ where package = 'DBMS_CUBE_EXP' and schema = 'SYS';

This solution resolved my issue 🙂

Though my issue was resolved, I was curious about table SYS.EXPPKGACT$ , for which I got following info:

EXPPKGACT$ is the table, which is the datapump handler table that contains all the packages that should be executed to complete the export.

So in my case, the OLAP Deinstallation, although successful, left behind a couple of references to OLAP in the EXPPKGACT$ table, which was causing the issue.

Hope so u will find this post very useful 🙂




12 replies

  1. That helped though my problem was not exactly the same, thanks!
    For those who removed JAVA and got this error on export:

    ORA-39127: unexpected error from call to “SYS”.”DBMS_JVM_EXP_PERMS”.”GRANT_SYSPRIVS_EXP”
    ORA-44002: invalid object name
    ORA-06512: at “SYS.DBMS_ASSERT”, line 316
    ORA-06512: at “SYS.DBMS_METADATA”, line 8613

    that will solve your problem:
    sqlplus / as sysdba
    delete * from sys.exppkgobj$ where package like ‘%JVM%’;

  2. I am glad to be one of several visitants on this great web site (:, regards for putting up.

  3. Quality content is the crucial to attract the users to visit the
    web page, that’s what this site is providing.

  4. Thank you for every other wonderful post. Where else may just anybody
    get that kind of information in such a perfect manner
    of writing? I have a presentation subsequent week, and I am at the look for such information.

  5. I really like what you guys are up too. Such clever work and coverage!
    Keep up the awesome works guys I’ve included you guys to my

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s