By: Daniel Geringer, Senior Development Manager, Oracle Spatial and Graph
One of the things users can run into when using Esri with Oracle Spatial can be problems with data validation when loading data using Esri utilities into Oracle Spatial data types. From my experience, the solution is a relatively straightforward change in the workflow used to load data.
Here is an excerpt from a user problem where it sounds like Esri is calling Oracle's validation on load (not Esri's validation).
I don't believe Esri's validation would be sensitive to the database version.
This sounds more like a workflow defined by Esri than differences in validation. I think the issue is once Esri encounters an invalid geometry, it stops loading the rest (even if they are valid). I believe Esri chooses this workflow to ensure all geometries in a layer are valid. I agree the outcome is optimal, and what Oracle recommends too. A deficiency in the workflow is:
1. It prevents valid geometries from being loaded after an invalid one is encountered
2. Not loading the invalid geometry does not provide a way to inspect it
From a product perspective, a change in the Esri workflow would have to be implemented by Esri. (Maybe the default behavior can remain the same, but enable a switch that populates invalid geometries into a different table for inspection at a later time. This is just one suggestion. There may be other options.)
Currently, the best way to circumvent this is to do what this customer did, and load data with Oracle or third party tools like FME. Once the data is loaded, Oracle also recommends validation, and removing/isolating invalid geometries until they can be fixed. I discuss a strategy to do this in a best practices presentation.
One thing I keep hearing is the claim that Esri and Oracle validate differently.