Today, I would like to discuss a strange issue which was experienced during schema refresh activity. Everything was normal and as expected in the environment until the April 2017 patching has been applied in the Env.

Due to the Q-PSU patching ,there were some system views which got invalid and the imports job was aborting with flood of errors ,mainly stating ORA-600

Below are the errors :

ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW00" prematurely terminated
ORA-31671: Worker process DW00 had an unhandled exception.
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-00600: internal error code, arguments: [klxpr_22], [2], [30], [36053], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.DBMS_SQL", line 1707
ORA-06512: at "SYS.KUPD$DATA", line 2495
ORA-06512: at "SYS.KUPD$DATA", line 3503
ORA-06512: at "SYS.KUPD$DATA", line 3764
ORA-06512: at "SYS.KUPW$WORKER", line 19325
ORA-06512: at "SYS.KUPW$WORKER", line 24290
ORA-06512: at "SYS.KUPW$WORKER", line 20708
ORA-06512: at "SYS.KUPW$WORKER", line 4561
ORA-06512: at "SYS.KUPW$WORKER", line 12079
ORA-06512: at "SYS.KUPW$WORKER", line 2097
ORA-06512: at line 2
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 2 with process name "DW01" prematurely terminated
ORA-31671: Worker process DW01 had an unhandled exception.
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-00600: internal error code, arguments: [klxpr_22], [2], [30], [36053], [], [], [], [], [], [], [], []
ORA-06512: at "SYS.DBMS_SQL", line 1707
ORA-06512: at "SYS.KUPD$DATA", line 2495
ORA-06512: at "SYS.KUPD$DATA", line 3503
ORA-06512: at "SYS.KUPD$DATA", line 3764
ORA-06512: at "SYS.KUPW$WORKER", line 19325
ORA-06512: at "SYS.KUPW$WORKER", line 24290
ORA-06512: at "SYS.KUPW$WORKER", line 20708
ORA-06512: at "SYS.KUPW$WORKER", line 4561
ORA-06512: at "SYS.KUPW$WORKER", line 12079
ORA-06512: at "SYS.KUPW$WORKER", line 2097
ORA-06512: at line 2

Upon further investigation, It was found that there are some SYS views which are in INVALID state due to which IMPORT operations is getting aborted.

set lines 140
col status for a9
col object_type for a20;
col owner.object for a50
select con_id, status, object_id, object_type,owner||'.'||object_name "OWNER.OBJECT" from cdb_objects where object_name like '%KU$%' and status='INVALID' order by 4,1;


OWNER OBJECT_NAME OBJECT_TYPE
---------- ------------------------------ ---------------
SYS KU$_M_VIEW_H_VIEW VIEW
SYS KU$_ZM_VIEW_H_VIEW VIEW
SYS KU$_M_VIEW_PH_VIEW VIEW
SYS KU$_ZM_VIEW_PH_VIEW VIEW
SYS KU$_M_VIEW_FH_VIEW VIEW
SYS KU$_ZM_VIEW_FH_VIEW VIEW
SYS KU$_M_VIEW_PFH_VIEW VIEW
SYS KU$_ZM_VIEW_PFH_VIEW VIEW
SYS KU$_M_VIEW_IOT_VIEW VIEW
SYS KU$_ZM_VIEW_IOT_VIEW VIEW
SYS KU$_M_VIEW_PIOT_VIEW VIEW
SYS KU$_ZM_VIEW_PIOT_VIEW VIEW
SYS KU$_M_ZONEMAP_H_VIEW VIEW
SYS KU$_M_ZONEMAP_PH_VIEW VIEW
SYS KU$_M_ZONEMAP_FH_VIEW VIEW
SYS KU$_M_ZONEMAP_PFH_VIEW VIEW
SYS KU$_M_ZONEMAP_IOT_VIEW VIEW
SYS KU$_M_ZONEMAP_PIOT_VIEW VIEW



My work around for the issue is to validate the view using ALTER which was not helpful in my case.
Upon more search in Oracle Metalink Doc ID 2289785.1its been found as
Bug 25297023 : INVALID OBJECTS AFTER UPGRADING OR APLYING DATAPATCH


And the solutions which was suggested by Oracle was :

1. alter SYSTEM set nls_length_semantics=byte
2. ORACLE_HOME/rdbms/admin/dpload.sql
3. ORACLE_HOME/rdbms/admin/utlrp.sql 

This Instinct resolve the Issue and import operation got completed with out any errors