ArcGIS Pro 2.6.8; Oracle 18c 10.7.1 EGDB:
Anyone who's worked in Catalog with enterprise geodatabase data (especially in a dev environment) knows that sometimes items get broken. There are likely multiple possible causes. It's not necessarily due to a bug; someone might have accidentally deleted the table or view from the database. (not a big deal in a dev environment)
But the bottom line is, an item appears in Catalog, but the table or view doesn't actually exist in the database. The item shows up in Catalog because there are still records in the geodatabase system tables that pertain to the item.
The database view doesn't exist in the database (SQL Developer):
Deleting the item via Catalog has no effect. The item momentarily disappears from Catalog, but then it reappears when Catalog is refreshed.
Idea:
Could that behavior be changed so that Catalog only shows items that actually exist in the database? Or give us a tool to remove broken registered items from the geodatabase system tables?
Additionally, it would be great if that error message could be improved to say something like, "The item does not exist in the database".