How to remove domains that look corrupted

[JoseSanchez]

Hi all

We have domaisn in our sde dataabse that are not associated with feature classes but when deleting them they look they are used by a feature.

Is there a way to remove them when ArcCatalog does not allow it

[VinceAngelo]

What database are you using?

What version and service pack of ArcSDE are you using?

What version and service pack of ArcGIS are you using?

Is the domain referenced by a table in the GDB metadata?

Does that table still exist?

- V

[JoseSanchez]

Oracle 10G

ArcSDE 9.3

ArcCatalog 9.3.1 last package available

The domain is not referenced by a feature in the database

Features have been deleted

[VinceAngelo]

Does an GDB_OBJECTCLASSES row that corresponds to the dropped table exist?
Is there an entry in GDB_DOMAINS which corresponds to the object class ID?

The easiest way to uncorrupt the geodatabase registry is to create a table with
the name of the dropped table via SQL, then use Catalog to delete it.

- V

[JoseSanchez]

How can I check if a GDB_OBJECTCLASSES row corresponds to the dropped feature class?

How can I check if any entry in GDB_DOMAINS corresponds to the object class ID?

All features and tables were deleted in the sde instance..

What we need is a way to fix the problem.  What do you suggest?

Does an GDB_OBJECTCLASSES row that corresponds to the dropped table exist?
Is there an entry in GDB_DOMAINS which corresponds to the object class ID?

The easiest way to uncorrupt the geodatabase registry is to create a table with
the name of the dropped table via SQL, then use Catalog to delete it.

- V

[VinceAngelo]

If all tables registered with ArcSDE have been dropped *AND* there are no
tables using ST_GEOMETRY in the instance, then the easiest way to fix your
ArcSDE instance is to "DROP USER sde CASCADE" and reinstall. 

Note that if you *DO* have outstanding tables with ST_GEOMETRY columns,
then dropping SDE will corrupt your Oracle instance to the point that it too will
need to be dropped and recreated.

If you are uncomfortable doing SQL queries against the SDE metadata tables
to assess the status of your instance, then you should probably log an incident
and have a Tech Support analyst walk you through the necessary steps.

- V