Query error reasons
Table or column not found
A table or column that the query reads is not in your warehouse.
Reason in E1005 | Diagnostic code | Who can fix it | Does a retry help? |
|---|---|---|---|
SCHEMA_TABLE_NOT_FOUND | DBN-QRY-002 | Your admin | No |
What this means
A table or column that the query reads is not in your warehouse. The table or column was renamed or dropped, or the Databrain user cannot see it. Some warehouses give the same answer for “missing” and “no access”. When only a column is missing, the error has details.missingObject set to column and its own message.
What people see
| Who | Message | Next step |
|---|---|---|
| Admin or API caller (table) | A table or column this query reads was not found. | Ask your admin to check that it exists and that the Databrain user can read it, then run Sync Schema. |
| Admin or API caller (column) | A column this query reads was not found. | Check that the column still exists in the table, run Sync Schema, then update the metric. |
| Embed viewer | This chart has a data setup problem. | Contact your admin. |
| Metric builder | This field can’t be combined with the others. | Pick another field. |
How to fix it
- Check that the table and the column still exist in the warehouse.
- Check that the Databrain user can read them.
- In Datasources, select Sync schema on the datasource.
- Update the metric if a name changed.
Warehouse codes behind it
| Warehouse | Codes |
|---|---|
| MySQL, SingleStore | 1146, 1054 |
| PostgreSQL, Redshift, CockroachDB | SQLSTATE 42P01, 42703 |
| ClickHouse | 60 (UNKNOWN_TABLE), 47 (UNKNOWN_IDENTIFIER) |
| SQL Server, Microsoft Fabric | 208, 207 |
| Databricks | TABLE_OR_VIEW_NOT_FOUND, SCHEMA_NOT_FOUND, CATALOG_NOT_FOUND, UNRESOLVED_ROUTINE |
| BigQuery | notFound |
| Trino | TABLE_NOT_FOUND, COLUMN_NOT_FOUND, SCHEMA_NOT_FOUND, CATALOG_NOT_FOUND |
| Elasticsearch | index_not_found_exception |
Ask for help
Every error has a six-character ref, for example Ref A1B2C3. API callers find it in
details.ref. Search for the ref in Settings > Diagnostics > Logs to see the full log line, or
send the ref and the time of the error to support.