I am using ArcGIS Desktop 10.5.1 and Oracle Geodatabase 10.5.1. Sometimes users create a record with null geometry. This can be done by simply hitting enter when in edit mode when on the last row in the attribute editor. In this case a record with NULL geometry is created. This seems to cause issues with ST_GEOMETRY functions such as ST_ASTEXT. This is a new bug at Geodatabase 10.5.1. We were at 10.2.2 for years and this was not an issue.Aside from ST functions these NULL geometries will also cause any spatial views that use a UNION clause to fail.
In ArcMap 10.2.2 or 10.5.1 when a NULL geometry is created by the software it is assigned a LEN and AREA of NULL which logically makes sense.However the 10.5.1 geodatabase ST_* functions seem to barf when the LEN and AREA are NULL. It seems to prefer these values to be 0.
At ArcGIS Desktop 10.6 and ArcGIS Pro 2.1.3 when a NULL geometry is created it is assigned a LEN and AREA of 0. which seems to resolve the issue with the ST_* functions.
So NULL geometry created at 10.5.1 Desktop can not be used with ST_* functions in the 10.5.1 geodatabase. Also any existing NULL geometry created over the years will cause issues. Is there an update tool for this or can the geodatabase shapelib package be updated to not cause a fatal error when it encounters a NULL AREA or LEN on a record?
Thanks, Al Benvin