Hello Everyone,
Sorry after some weekend research I have a follow-up question to INVALID Domain indexes. Perhaps helpful to others in the Geodatabase community.
Current environment:
Geodatabase 10.7.1
ArcGIS Pro 2.9.4
Oracle 18.6.0.0
ST_GEOMETRY
Windows
Upgrade Environment:
Geodatabase 11.1
ArcGIS Pro 3.1.0
Oracle 19.16.0.0
ST_GEOMETRY
Linux
Steps:
Windows / Oracle 18.6.0.0 / Geodatabase 10.7.
SELECT * FROM DBA_OBJECTS WHERE STATUS!= 'VALID' ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
NO INVALID OBJECTS
Copied database instance to Linux Server
Linux / Oracle 18.6.0.0 / Geodatabase 10.7.1
SELECT * FROM DBA_OBJECTS WHERE STATUS!= 'VALID' ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
NO INVALID OBJECTS
Upgraded Oracle
Linux / Oracle 19.16.0.0 / Geodatabase 10.7.1
SELECT * FROM DBA_OBJECTS WHERE STATUS!= 'VALID' ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
NO INVALID OBJECTS
Installed the latest Linux st_geometry libraries
CREATE or REPLACE LIBRARY ST_SHAPELIB AS 'oracle\libst_shapelib.so';
ALTER PACKAGE sde.st_geometry_shapelib_pkg COMPILE REUSE SETTINGS;
EXEC dbms_utility.compile_schema( 'SDE', compile_all => FALSE );
SELECT * FROM DBA_OBJECTS WHERE STATUS!= 'VALID' ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
NO INVALID OBJECTS
Upgrade Geodatabase geoprocessing tool
Linux / Oracle 19.16.0.0 / Geodatabase 11.1.0
SELECT * FROM DBA_OBJECTS WHERE STATUS!= 'VALID' ORDER BY OWNER, OBJECT_TYPE, OBJECT_NAME;
ALL Axxx_IX1 indexes INVALID
I have read the ESRI / Oracle documentation on Domain Indexes and helpful feedback from Marcelo Marques (Esri) after data migration between two Oracle Instances and issues with domain Indexes and ROW_IDS.
However, my question for clarification - why did the Invalid Indexes only present themselves only after using the Upgrade Geodatabase geoprocessing tool? I thought they would already be present after we copied the data from one instance to the new one.
Feedback appreciated.
