| Previous | Next |
| DB_E_INDEXINUSE | DB_E_CONCURRENCYVIOLATION |
DB_E_NOTABLE
Meaning
Windows documents DB_E_NOTABLE as “Table does not exist”. Here, an OLE DB table-open, metadata or definition operation names a table that does not exist in the current data source scope.
Relevant OLE DB contract
This result must be interpreted against this contract: OLE DB data-definition interfaces operate on provider-scoped table and index DBIDs; existence, identifier validity and active use are separate outcomes, and schema changes must account for open rowsets and transactions.
Start with the session performing the definition operation and the table or index identity resolved by that session when investigating this result.
Specific conditions that produce the result
- Cause 1: the table was never created or was dropped.
- Cause 2: the DBID resolves in a different catalog or schema.
- Cause 3: identifier case or qualification differs from provider rules.
Evidence to collect before changing the system
- Evidence 1: the requested table DBID, catalog and schema.
- Evidence 2: current table metadata from the same session.
- Evidence 3: recent deployment, rename and transaction events.
Corrective actions
- Action 1: qualify the table using provider-reported identifiers.
- Action 2: refresh metadata after migrations.
- Action 3: treat an optional missing table separately from malformed identifiers.
Retry and recovery policy
Retry rule: retry after creating the table or correcting its catalog, schema or identifier.
Practical incident
A service validates a table in one catalog and later opens it through a session whose default catalog changed; using a fully qualified DBID removes it.
Difference from related HRESULT values
DB_E_BADTABLEID means the table identifier itself is invalid, while DB_E_NOTABLE means a valid-looking identifier resolves to no table.
Official Microsoft references
Looking for a different code? Search another status or error code.