Upgrade an Oracle geodatabase after applying the Spatial Reference Consistency Patch

Summary

The Spatial Reference Consistency Patch released for ArcGIS for 10.2.1 and 10.2.2 (Desktop, Engine and Server) corrects inconsistencies between a feature class’ spatial reference and the geodatabase metadata.

After applying the Spatial Reference Consistency Patch, the geodatabase must be upgraded by the administrator and in some situations feature classes require their spatial indexes to be dropped and re-created.

This article outlines the steps for upgrading the geodatabase and identifying whether any feature classes' spatial indexes must be re-created.

Procedure

1. Determine which feature classes must have spatial indexes created.
   
   The following query returns any feature class that do not have a spatial index:
   
   

   SELECT  owner, table_name
   FROM sde.st_geometry_columns 
   WHERE (owner, table_name, column_name) NOT IN 
     (SELECT owner, table_name, column_name 
      FROM sde.st_geometry_index);

   
   The next query returns feature classes that currently have an invalid spatial index:
   
   

   SELECT owner, table_name
   FROM   all_indexes
   WHERE  status <> 'VALID' 
   AND    ityp_owner = 'SDE' 
   AND    ityp_name = 'ST_SPATIAL_INDEX';

   
   
   

   Note:
   This query does not return invalid indexes for which the user does not have privileges. It is recommended that the query be executed by a user with elevated permissions.

   
   
2. For each table returned, use ArcCatalog to drop and create the spatial index.