1

Topic: Invalid Partition Indexes

Here recently noted here such bum in basis:

SQL> set pagesize 0;
SQL> select owner, index_name, partitioned
2 from dba_indexes
3 where not status = ' VALID ' and owner in (' SYS','SYSTEM ');
SYS I_STREAMS_APPLY_SPILL_MSGS_PT1 YES
SYS SYS_IL0000008123C00008 $$ YES
SYS WRH $ _ ACTIVE_SESSION_HISTORY_PK YES
SYS WRH $ _ DB_CACHE_ADVICE_PK YES
SYS WRH $ _ DLM_MISC_PK YES
SYS WRH $ _ FILESTATXS_PK YES
SYS WRH $ _ INST_CACHE_TRANSFER_PK YES
SYS WRH $ _ LATCH_CHILDREN_PK YES
SYS WRH $ _ LATCH_MISSES_SUMMARY_PK YES
SYS WRH $ _ LATCH_PARENT_PK YES
SYS WRH $ _ LATCH_PK YES
SYS WRH $ _ OSSTAT_PK YES
SYS WRH $ _ PARAMETER_PK YES
SYS WRH $ _ ROWCACHE_SUMMARY_PK YES
SYS WRH $ _ SEG_STAT_PK YES
SYS WRH $ _ SERVICE_STAT_PK YES
SYS WRH $ _ SERVICE_WAIT_CLASS_PK YES
SYS WRH $ _ SGASTAT_U YES
SYS WRH $ _ SQLSTAT_INDEX YES
SYS WRH $ _ SQLSTAT_PK YES
SYS WRH $ _ SYSSTAT_PK YES
SYS WRH $ _ SYSTEM_EVENT_PK YES
SYS WRH $ _ SYS_TIME_MODEL_PK YES
SYS WRH $ _ TABLESPACE_STAT_PK YES
SYS WRH $ _ WAITSTAT_PK YES
SYSTEM LOGMNRC_GSII_PK YES
SYSTEM LOGMNRC_GTCS_PK YES
SYSTEM LOGMNRC_GTLO_PK YES
SYSTEM LOGMNRC_I2GTLO YES
SYSTEM LOGMNRC_I3GTLO YES
SYSTEM LOGMNR_I1ATTRCOL $ YES
SYSTEM LOGMNR_I1CCOL $ YES
SYSTEM LOGMNR_I1CDEF $ YES
SYSTEM LOGMNR_I1COL $ YES
SYSTEM LOGMNR_I1COLTYPE $ YES
SYSTEM LOGMNR_I1ICOL $ YES
SYSTEM LOGMNR_I1IND $ YES
SYSTEM LOGMNR_I1INDCOMPART $ YES
SYSTEM LOGMNR_I1INDPART $ YES
SYSTEM LOGMNR_I1INDSUBPART $ YES
SYSTEM LOGMNR_I1LOB $ YES
SYSTEM LOGMNR_I1LOBFRAG $ YES
SYSTEM LOGMNR_I1OBJ $ YES
SYSTEM LOGMNR_I1TAB $ YES
SYSTEM LOGMNR_I1TABCOMPART $ YES
SYSTEM LOGMNR_I1TABPART $ YES
SYSTEM LOGMNR_I1TABSUBPART $ YES
SYSTEM LOGMNR_I1TS $ YES
SYSTEM LOGMNR_I1TYPE $ YES
SYSTEM LOGMNR_I1USER $ YES
SYSTEM LOGMNR_I2COL $ YES
SYSTEM LOGMNR_I2IND $ YES
SYSTEM LOGMNR_I2INDPART $ YES
SYSTEM LOGMNR_I2TAB $ YES
SYSTEM LOGMNR_I2TABCOMPART $ YES
SYSTEM LOGMNR_I2TABPART $ YES
SYSTEM LOGMNR_I2TABSUBPART $ YES
57 rows selected.
SQL>

Unfortunately with  business indexes had no earlier, how much terrible situation resulted more low. Than it threatens?
Well and the most important thing how to correct a situation.
Google of anything intelligible except
[quote =]
"The ODCI interface does not allow partitioned indexes to be rebuilt. You can use replace metadata on individual partitions to, for instance, change the sync interval. But you cannot alter index rebuild for the overall index - you'll get the error ORA-14086: a partitioned index may not be rebuilt as a whole. However, we have a PL/SQL procedure which works around ODCI. Just call it with the index name and the parameters string, like this:
exec ctx_ddl.replace_index_metadata (' myidx ', ' replace metadata lexer rlex ');"

Did not find, but I am not assured about ' replace metadata lexer rlex '.
Comment  colleagues, and!?
How correctly to repair them?
alter index name rebuild partitioned in a forehead did not fulfill.