Unable to delete a feature class from the enterprise geodatabase

[anbinh]

Hi Community,

ArcGIS Pro returns the following error when trying to delete this feature class from the Enterprise Geodatabase. We have confirmed that there is no other active connections or locks.

It only happens with this single feature class in the EGDB. We can delete all the other feature classes we want to delete. 

This feature class was once archiving enabled, but for some reason in history (we don't know), the archiving columns [GDB_FROM_DATE, GDB_TO_DATE, GDB_ARCHIVE_OID] do not exist in this feature class anymore. If we try to disable archiving from ArcGIS Pro, an error would occur saying "Attribute column not found [42522:[Microsoft][ODBC Driver 17 for SQL Server][SQL Server] Invalid column name 'GDB_TO_DATE'.]"

Any suggestions what we can do to get this feature class deleted from the EGDB?

Update:

Reading this Unable to delete a feature class that had archivin... - Esri Community, I feel like we are in a very similar this situation that the feature class has been corrupted as ArcGIS Pro still think it is archiving enabled while the archiving columns do not exist anymore. We cannot either disable the archiving properly or delete this feature class. 

Any help would be appreciated. 

Many thanks,

AB

[Laura]

When I get that error I simply just need to disconnect all users from accessing the database and then can successfully delete. Have you removed all active connections and then try deleting? 

[anbinh]

Hey Laura,

Yes I have removed all active connections and locks. Seems like the error message is inaccurate.

Regards,

[anbinh]

Reading this Unable to delete a feature class that had archivin... - Esri Community, I feel like the feature class has been corrupted and ArcGIS Pro still think it is archiving enabled, and we cannot either disable the archiving properly or delete this feature class. 

Any help would be appreciated. 

[anbinh · Accepted solution]

The feature class was finally able to be deleted after an ArcGIS Server service restart. Although we then had an issue when copying the feature class with the same name to this database as it will automatically add a suffix "_1" to the newly created feature class, we removed the reference from SDE_TABLE_REGISTRY, then everything works fine from there.