Encountered a problem exporting features from an Oracle SDE geodatabase feature class. The feature class contained an erroneous SHAPE field, field type long integer, entirely NULL values. The feature class geometry was stored in SHAPE_1. When selecting and exporting features to a file geodatabase feature class, ArcGIS Pro 2.9.3 appeared to pull the NULL values from SHAPE (long) and returned a table with NULL geometries.
ArcMap 10.8.2 is able to recognize the correct geometry field and the same extraction was completed successfully.
Obviously, an erroneous SHAPE field is bad data management, but this appears to be a bug.
Thanks!
Hope you can back tracking what processes that data has gone through and find out how the two similar fields were introduced in likely non-standard way.