Remove detached objects (feature classes) from a geodatabase

Summary

In the event of data or users being removed from a back-end database, geodatabase objects are sometimes detached. The most likely causes for this are:

• The objects were unintentionally dropped by a user with a SQL command.
• During database migration, the geodatabase objects were lost.

Procedure

The instructions provided describe how to remove a detached object from a geodatabase. Before proceeding with the following workflow, ensure a recent verified and tested backup has been completed.

1. In the back-end database, use SQL to create a table with the same name as the detached object.

   CREATE TABLE <detached_table_name>
   (
   column_name1 data_type,
   column_name2 data_type,
   column_name3 data_type,
   ....
   )

2. Use ArcCatalog to delete <detached_table_name>.
3. To add the feature class back in to the geodatabase, create the feature class in ArcCatalog with the same name.