What causes CATALOG_NOT_FOUND?

The catalog name in the query is misspelled or uses the wrong case. The catalog was created in a different Databricks metastore than the one attached to the current workspace. The service principal or user does not have USE CATALOG privilege on the catalog. The catalog was deleted or detached from the metastore

How do I fix CATALOG_NOT_FOUND?

Step 1: Run SHOW CATALOGS in a Databricks SQL warehouse to list catalogs accessible in the current metastore.. Step 2: Verify the catalog name in the failing query matches exactly (Unity Catalog names are case-insensitive but the catalog must exist).. Step 3: Grant USE CATALOG privilege if the catalog exists but the user or principal lacks access.. Step 4: If the catalog is in a different metastore, check workspace-metastore assignments in the Databricks account console.. Step 5: Recreate the catalog if it was accidentally dropped, then reassign privileges.

High severityconfiguration

Power BI Refresh Error:
CATALOG_NOT_FOUND

What does this error mean?

A query or job referenced a Unity Catalog catalog name that does not exist or is not accessible in the current metastore.

Common causes

1The catalog name in the query is misspelled or uses the wrong case
2The catalog was created in a different Databricks metastore than the one attached to the current workspace
3The service principal or user does not have USE CATALOG privilege on the catalog
4The catalog was deleted or detached from the metastore

How to fix it

1Step 1: Run SHOW CATALOGS in a Databricks SQL warehouse to list catalogs accessible in the current metastore.
2Step 2: Verify the catalog name in the failing query matches exactly (Unity Catalog names are case-insensitive but the catalog must exist).
3Step 3: Grant USE CATALOG privilege if the catalog exists but the user or principal lacks access.
4Step 4: If the catalog is in a different metastore, check workspace-metastore assignments in the Databricks account console.
5Step 5: Recreate the catalog if it was accidentally dropped, then reassign privileges.

Frequently asked questions

Is Unity Catalog catalog name lookup case-sensitive?

Catalog, schema, and table names in Unity Catalog are stored and matched case-insensitively, but they must still be spelled correctly.

Can I use the hive_metastore catalog after migrating to Unity Catalog?

Yes — hive_metastore remains accessible as a catalog name in Unity Catalog-enabled workspaces, pointing to the legacy per-workspace Hive metastore.