Is This Content Helpful?
We're glad to know this article was helpful.
What happens during the geodatabase upgrade if an underlying table is missing?
This issue is the result of a record being present in either the GDB_ObjectClasses or GDB_FeatureClasses table for a table that does not exist in the underlying database. When this situation is encountered, the geodatabase upgrade logs a warning and continues with the upgrade. The warning appears as the following:
"Table (Fittings) was found in GDB_ObjectClasses, but does not exist in the database. Skipping."
There may be other error messages included with the warning.