> ## Documentation Index
> Fetch the complete documentation index at: https://docs.open-metadata.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Databend Troubleshooting | OpenMetadata Connector

> Troubleshoot common Databend connector issues in OpenMetadata, including connection failures, permission errors, and ingestion problems.

## Troubleshooting

## Workflow Deployment Error

If there were any errors during the workflow deployment process, the
Ingestion Pipeline Entity will still be created, but no workflow will be
present in the Ingestion container.

* You can then Edit the Ingestion Pipeline and **Deploy** it again.
* From the Connection tab, you can also Edit the Service if needed.

## Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in OpenMetadata. Below are some of the most frequently observed troubleshooting scenarios.

## How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in OpenMetadata:

1. **Navigate to Services**
   Go to **Settings > Services > Service Type** (e.g., Database) in the OpenMetadata UI.

2. **Select a Service**
   Choose the specific service for which you want to enable debug logging.

3. **Access Agents Tab**
   Go to the **Agents tab** and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.

4. **Enable Debug Logging**
   In the configuration dialog, enable the **Debug Log** option and click **Next**.

5. **Schedule and Submit**
   Configure the schedule if needed and click **Submit** to apply the changes.

## Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

## Databend-Specific Issues

The following issues are specific to the Databend connector.

### Test Connection Fails Against a Non-TLS Endpoint

The default self-hosted Databend port `8000` serves plain HTTP. If the connection test fails, open **Advanced Config**, add `sslmode` under **Connection Options**, and set it to `disable`. For a TLS endpoint, set `sslmode` to `enable`.

### Test Connection Fails on a Specific Step

The test runs these steps: **CheckAccess**, **GetDatabases**, **GetSchemas**, and **GetTables** are required, and **GetViews** is optional.

* **CheckAccess**: OpenMetadata can't reach or authenticate with Databend. Confirm **Host and Port**, **Username**, and **Password**.
* **GetDatabases**: OpenMetadata can't access the Databend `default` catalog.
* **GetSchemas**: The user can't list Databend databases.
* **GetTables**: The user can't list tables in a Databend database. Confirm the user can read `information_schema` metadata.

### No Schemas or Tables Are Ingested

OpenMetadata excludes the `information_schema`, `system`, and `system_history` databases by default. Leave **Database Schema** blank to scan all other accessible databases, or set it to restrict ingestion to a single database. Review your filter rules in the **What to Ingest** step, and confirm the user can read the databases you expect to ingest.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.