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:

impdp directory=UAT_DIR network_link=MIGRATION_DB_LINK parallel=8 full=y logfile=migration_UATDB_27nov.log exclude=SCHEMA:"in ('SCOTT','ORACLE_OCM','XS$NULL','MDDATA','DIP','APEX_PUBLIC_USER','SPATIAL_CSW_ADMIN_USR','SPATIAL_WFS_ADMIN_USR','DMSYS','DBSNMP','FLOWS_FILES','MDSYS','ORDSYS','EXFSYS','WMSYS','APPQOSSYS','APEX_030200','OWBSYS_AUDIT','ORDDATA','CTXSYS','ANONYMOUS','XDB','ORDPLUGINS','OWBSYS','SI_INFORMTN_SCHEMA','OLAPSYS','SYS','SYSTEM','OUTLN')"

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

Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
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';
commit;

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 🙂

Cheers

Regards,

Adityanath