Was the spatial index built in SQL developer? In SQL developer, does the geometry metadata etc line-up with your projection and extent?
Can you read the table in SQL dev and ArcCatalog? and can you preview the geography in Catalog?
What's the history behind this feature, is it a new import, update, have you done something to it recently etc?
If you export the feature to a local FGDB as a FC does it work ok?
We are not a built-in SQL developer.
We can read the table in SQL dev and ArcCatalog. We cannot preview the geography in Catalog.
This feature was copied or import from the local file geodatabase and we have checked in FGDB that the feature is opening in ArcMap with geometry in local.
Yes, it does work when we export the feature to a local FGDB as it was seen in local.
We have 86 layers, out of which 3 are having the same issue (ArcMap Layers, we deleted from sde and again imported, the same issue.
Also, the coordinate system/projection is as below.
What is the Geometry type (SDO_Geometry, ST_Geometry, etc.) being used in the feature classes with issues?
Is there multiple geometry types (point / line / poly) in the same table?
How are you importing the data into the Oracle Geodatabase?