SDE Invalid Column Data Type Error

[MichaelVolz]

I am trying to edit a linear SDE feature class that is part of a geometric network in a feature dataset that has not been edited in quite some time (probably not for 2 SDE upgrades). The linear SDE feature class is stored in an Oracle 11.2.0.3 (AIX 64-bit platform) database and I am working with ArcGIS for Desktop v10.3.1. When I try to make an edit (e.g. delete 2 line segments) after starting an edit session, Desktop throws an error "The features could not be deleted.  Invalid column data type.".  Then if I try to the delete a feature after that I get the initial error, I then get a different error "The features could not be deleted.  FDO error: -2147216071".

If I recreate the geometric network and feature dataset inside a new file gdb, I am able to successfully delete the line segments without the errors I am encountering in SDE.

This layer is used widely across my organization's enterprise environment in 100s of mxds so it is imperative that it is fixed without the renaming of the data which would create many broken links.

Has anyone encountered this type of error before?  If so, how did you solve the problem?

Any help or hints are greatly appreciated.

[Asrujit_SenGupta]

The "describe tablename" was suggested to compare the Schemas(Field Structure). You won't be expecting an error on just doing a "describe tablename". 

Michael Volz wrote:

With your statement "Esri supports Oracle 11.2.0.3 at ArcGIS 10.3.1, but recommends upgrade to 10.2.0.4 (ArcGIS 10.4 and 10.5 only support 10.2.0.4 and higher)."

Did you mean to say but recommends upgrade to 11.2.0.4 (ArcGIS 10.4 and 10.5 only support 11.2.0.4 and higher)?

I ask because my original post talked about 11.2.0.3 and I never mentioned the Oracle 10.2.0.x

Yes, he meant 11.2.0.4. Oracle 10g R2 is not supported at 10.4.x or 10.5. Also the link he provided mentions the below:

Oracle 11g R2 (11.2.0.x) requirements

Note:

• Oracle 11.2.0.3 is the base supported version for 11g. However, there are several issues customers are encountering in 11.2.0.3. Therefore, Esri recommends moving to 11.2.0.4. The issues are detailed in this Esri technical article.

[arahman_mdmajid]

This issue can be resolved by reducing the database name.

Explained here: https://support.esri.com/en/technical-article/000005892