Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

Qlik Databricks Connector error: Provided catalog name does not exist

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Jack_Guo
Support
Support

Qlik Databricks Connector error: Provided catalog name does not exist

Last Update:

Jun 10, 2024 4:15:43 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jun 10, 2024 4:15:43 AM

Creating a Databricks database connection using the Qlik Databricks connector may fail with:

Provided catalog name does not exist

This is frequently caused by the Databricks catalog field in the connection dialog is empty.

Resolution

When unity catalogs are enabled in your Databricks environment, identify the catalog name that must be specified in the connection dialog. Refer to The default catalog configuration when Unity Catalog is enabled for details.

When unity catalogs are disabled in your Databricks environment, use hive_metastore as the default catalog name.

 

Cause

The Databricks catalog field in the connection dialog cannot be empty when unity catalogs are enabled. But we have seen a scenario where default catalog value is set to hive_metastore even in workspaces where unity catalog is not enabled. In this case, in the connection dialog, the user needs to mention hive_metastore as the catalog name. Then the connection succeeds.

 

Related Content 

For checking if unity catalog is enabled or not in your Databricks environment, refer to: Confirm that your workspace is enabled for Unity Catalog

 

Internal Investigation ID(s) 

HLP-16213

 

Environment

  • Qlik Databricks connector with Qlik Cloud environment
  • Qlik Databricks connector with Qlik Sense server environment
Labels (1)
Version history
Last update:
‎2024-06-10 04:15 AM
Updated by: