BUG-000181387: Spatial indexes become invalid after upgrading an enterprise geodatabase in Oracle to a newer release

Description

After upgrading an enterprise geodatabase in Oracle to a newer release, you may notice that some spatial indexes are marked as invalid.  This is documented in software defect BUG-000181387.

A fix for this behavior is planned for the ArcGIS Q2 2026 release of ArcGIS Pro and ArcGIS Enterprise, and it is scheduled for inclusion in upcoming ArcGIS Pro and ArcGIS Server patches. Use the following SQL query to determine if some of your feature classes have invalid spatial indexes (run as the SYS user):

col owner for a14
col index_name for a12
col column_name for a12
col table_name for a30
col ityp_owner for a10
col ityp_name for a18

SELECT  ai.owner,
        ai.index_name,
        aic.column_name,
        aic.table_name,
        ai.ityp_owner,
        ai.ityp_name
FROM    all_indexes     ai,
        all_ind_columns aic
WHERE   ai.index_name = aic.index_name
 AND   (domidx_status   != 'VALID'
 OR     domidx_opstatus != 'VALID')
ORDER BY 1,2;

Solution or Workaround

Use Oracle’s UTL_RECOMP Package to fix invalid spatial indexes.

exec UTL_RECOMP.RECOMP_SERIAL('<SCHEMA_NAME>');  -- recompile all objects for a specific schema (sequentially)
exec UTL_RECOMP.RECOMP_SERIAL();                 -- recompile all objects in the entire database (sequentially)

exec UTL_RECOMP.RECOMP_PARALLEL(2,'<SCHEMA_NAME>');  -- recompile all objects (in parallel) for a specific schema
exec UTL_RECOMP.RECOMP_PARALLEL(2);   -- recompile all objects in the entire database (in parallel)