> ## 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.

# Athena Troubleshooting Guide | OpenMetadata Support

> Resolve OpenMetadata Athena connector issues fast with our comprehensive troubleshooting guide. Fix common database connection problems and errors quickly.

## 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.

## Test Connection Fails on GetTables, Naming AWS Lake Formation

Test Connection can fail on the **GetTables** step with one of two different errors naming your catalog and pointing at AWS Lake Formation, depending on what's actually missing.

### No Schemas Available

If no databases were available to read in the catalog at all, the error reads:

```
No schemas were available to read in <your-catalog>. This usually means the configured schemaFilterPattern matches no databases, or the IAM role is missing AWS Lake Formation DESCRIBE grants. Grant Lake Formation DESCRIBE/SELECT and verify the schema filter pattern.
```

This means either the connector's `schemaFilterPattern` doesn't match any database in the catalog, or the IAM role is missing the AWS Lake Formation **Describe** grant needed to see those databases.

#### Resolution

1. Check the catalog name and the connector's `schemaFilterPattern` to make sure they aren't unintentionally excluding every database.
2. In the AWS Lake Formation console, open **Data permissions** and confirm the IAM role has **Describe** on the databases you expect to see.
3. Re-run **Test Connection**.

### No Readable Tables

If databases were listed but no tables inside them were readable, the error reads:

```
Connected and listed schemas, but no tables were readable in any of the targeted schema(s) of catalog '<your-catalog>'. AWS Lake Formation returns an empty list (instead of an error) when grants are missing, so ingestion would succeed and ingest 0 tables. Grant Lake Formation DESCRIBE/SELECT to the IAM role on the catalog and its databases/tables, then retry. If the catalog is genuinely empty (no tables yet), this failure is expected and can be ignored.
```

This means the IAM role the connector uses is missing AWS Lake Formation **Describe** and **Select** grants on the target catalog, databases, or tables. AWS Lake Formation silently filters results it can't authorize instead of raising an error, so without this check, ingestion would otherwise report success while ingesting 0 tables.

#### Resolution

1. In the AWS Lake Formation console, open **Data permissions**.
2. Grant the IAM role used by the Athena connector **Describe** and **Select** permissions on the catalog, and on each database and table it needs to ingest.
3. Re-run **Test Connection**. If the catalog genuinely has no tables yet, this failure is expected and can be ignored.