As of April 20th, 2026, BigLake is now called Lakehouse. BigLake metastore is now called the Lakehouse runtime catalog. Lakehouse APIs, client libraries, CLI commands, and IAM names remain unchanged and still reference BigLake.

Troubleshoot borderless Lakehouse for Databricks Unity Catalog

This page shows you how to resolve common issues when querying remote data in Databricks Unity Catalog with borderless Lakehouse. For general borderless Lakehouse troubleshooting (including connectivity and routing over private interconnects), see Troubleshoot borderless Lakehouse issues.

Tables are empty or not discovered during refresh

If the catalog background metadata refresh indicates success (such as Refresh successfully completed), but tables in the federated catalog do not appear or listing tables returns 0 items, check the following:

  • EXTERNAL USE SCHEMA privilege: Verify that the Databricks Service Principal has been granted the EXTERNAL USE SCHEMA privilege on the target schemas or catalog in Unity Catalog. Without this privilege, background metadata refresh and credential vending for queries will fail.
  • External data access setting: Verify that External data access is enabled on the Databricks Unity Catalog metastore.
  • External location: Verify that the Databricks Unity Catalog and tables use an external storage location (such as Cloud Storage or Amazon S3) rather than default storage.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026年08月27日 UTC.