Hi there,
our data is stored in an Oracle-SDE database. I created a table in Oracle directly (joining tables as CTAS). As result of the join some feature may or may not have a geometry.
The table shows up in ArcCatalog or in "Add Data" in ArcMap (10.7.1) immediatley.
When added to ArcMap no issues / error messages occur. Features are shown as expected.
If I register the table first in the geodatabase (through ArcCatalog), and add the table to ArcMap no features will be drawn and the error message Underlying DBMS error [ORA-01722] appears.
To me it looks like the error message is caused by the fact that some feature do not have a geometry (ArcMap displays the error message in full - the query in question also contains a WHERE clause with "SDE.ST_EnvIntersects(ELE_VM_KABEL_WO.SHAPE,:1,:2,:3,:4) = 1" - I think the bind variables :1-:4 have invalid values (but not <null> - <null> seems to work if used as values) and cause the error message)).
My questions are:
- can someone confirm this or is something else causing the error message?
- if a table/view is not registered - do ArcMap/ArcGISServer not use a spatial filter at all or do they use a spatial filter in a different way so that a non-existing geometry is not causing any trouble?
Reading through the docs I'm not sure if there is a performance advantage using a registered view/table over a non-registered table/view?
I know that I could filter out features without geometry but it's not a good solution as they won't show up in a search then.
Thank you, Rob
