Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
The process is terminated as follows when running expdp in 12C databases.
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [ORA-04063: view “SYS.KU$_RADM_FPTM_VIEW” has errors
The problem is that the view named SYS.KU $ _RADM_FPTM_VIEW is invalid. Recompiling this view is not solve the error.
If the error in the view is like the below, you can follow the steps below to solve the problem.
“ORA-00932: inconsistent datatypes: expected NCHAR got NCHAR”
The error received during expdp is as follows.
1 2 3 4 5 6 7 8 9 10 11 12 | ORA-39126: Worker unexpected fatal error in KUPW$WORKER.FETCH_XML_OBJECTS [ORA-04063: view "SYS.KU$_RADM_FPTM_VIEW" has errors ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: at "SYS.KUPW$WORKER", line 12098 ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105 ORA-06512: at "SYS.DBMS_METADATA", line 9039 ORA-06512: at "SYS.DBMS_METADATA", line 2792 ORA-06512: at "SYS.DBMS_METADATA", line 3423 ORA-06512: at "SYS.DBMS_METADATA", line 4760 ORA-06512: at "SYS.DBMS_METADATA", line 5079 ORA-06512: at "SYS.DBMS_METADATA", line 9020 ORA-06512: at "SYS.KUPW$WORKER", line 14367 |
The error in the corresponding view is as follows.
1 2 3 4 5 6 | SQL> show errors view SYS.KU$_RADM_FPTM_VIEW; Errors for VIEW SYS.KU$_RADM_FPTM_VIEW: LINE/COL ERROR -------- ----------------------------------------------------------------- 0/0 ORA-00932: inconsistent datatypes: expected NCHAR got NCHAR |
Even if the SYS.KU $ _RADM_FPTM_VIEW view is recompiled, this does not fix the error.
1 2 3 4 5 6 7 8 9 10 11 12 13 | [oracle@orcldb ~]$ sqlplus / as sysdba SQL*Plus: Release 12.2.0.1.0 Production on Thu May 24 11:17:32 2018 Copyright (c) 1982, 2016, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL> alter view SYS.KU$_RADM_FPTM_VIEW compile; Warning: View altered with compilation errors. |
The main reason for the problem is that the character set of the radm_fptm$ table is incompatible with the character set of the type called $k_rm_fptm$_t.
When the type ku$_radm_fptm$_t is compiled as follows, the view named SYS.KU$_RADM_FPTM_VIEW can be compiled without any problems and then the export process will be completed succesfully.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 | [oracle@orcldb ~]$ sqlplus / as sysdba SQL*Plus: Release 12.2.0.1.0 Production on Thu May 24 11:17:32 2018 Copyright (c) 1982, 2016, Oracle. All rights reserved. Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production SQL> alter type ku$_radm_fptm_t compile reuse settings; Type altered. SQL> alter view SYS.KU$_RADM_FPTM_VIEW compile; View altered. SQL> show errors view SYS.KU$_RADM_FPTM_VIEW; No errors. |
Assume! Fixed my issue