# Exasol

This article outlines the integration with the Apache Kafka connector, enabling streamlined metadata management through crawling, profiling, data preview, and lineage building (Auto & Manual). It also ensures secure authentication via Credential Manager.

<figure><img src="/files/37DNqxSmaTkfuopIvsXl" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                         | RDBMS                    |
| -------------------------------------------------------------------------- | ------------------------ |
| OvalEdge Release Supported                                                 | Release6.3 to Release7.2 |
| <p>Connectivity</p><p>\[How the connection is established with Exasol]</p> | JDBC                     |

### Connector Features

| Feature                                      | Availability |
| -------------------------------------------- | :----------: |
| Crawling                                     |       ✅      |
| Delta Crawling                               |       ❌      |
| Profiling                                    |       ✅      |
| Query Sheet                                  |       ✅      |
| Data Preview                                 |       ✅      |
| Auto Lineage                                 |       ✅      |
| Manual Lineage                               |       ✅      |
| Secure Authentication via Credential Manager |       ✅      |
| Data Quality                                 |       ✅      |
| DAM (Data Access Management)                 |       ❌      |
| Bridge                                       |       ✅      |

### Metadata Mapping

The following objects are crawled from the Exasol and mapped to the corresponding UI assets.

| Exasol Object | Exasol Attribute    | OvalEdge Attribute | OvalEdge Category | OvalEdge Type      |
| ------------- | ------------------- | ------------------ | ----------------- | ------------------ |
| Table         | Table Name          | Table              | Tables            | Table              |
| Table         | Table Type          | Type               | Tables            | Table              |
| Table         | Table Comments      | Source Description | Descriptions      | Source Description |
| Columns       | Column Name         | Column             | Table Columns     | Columns            |
| Columns       | Data Type           | Column Type        | Table Columns     | Columns            |
| Columns       | Description         | Source Description | Table Columns     | Columns            |
| Columns       | Ordinal Position    | Column Position    | Table Columns     | Columns            |
| Columns       | Length              | Data Type Size     | Table Columns     | Columns            |
| Views         | View Name           | View               | Tables            | Views              |
| Views         | Text                | View Query         | Views             | Views              |
| Procedures    | Routine\_Name       | Name               | Procedures        | Procedures         |
| Procedures    | Description         | Source Description | Descriptions      | Procedures         |
| Procedures    | Routine\_Definition | Procedure          | Procedures        | Procedures         |
| Functions     | Routine\_Name       | Name               | Functions         | Functions          |
| Functions     | Routine\_Definition | Function           | Functions         | Functions          |
| Functions     | Description         | Source Description | Descriptions      | Functions          |
| Triggers      | Trigger Name        | Name               | Triggers          | Triggers           |
| Triggers      | Trigger Definition  | Trigger Data       | Triggers          | Triggers           |
| Triggers      | Trigger Type        | Type               | Triggers          | Triggers           |

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

### **Whitelisting Ports**

Whitelist the inbound port 8563 to allow OvalEdge to connect to the Exasol Server database.

{% hint style="warning" %}
Exasol uses port 8563 by default. When a different port is configured, specify the updated port number during connection setup, whitelist the port, and establish proper communication between the system and the Exasol Server.
{% endhint %}

### Service Account User Permissions

{% hint style="warning" %}
Use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.
{% endhint %}

{% hint style="info" %}
**👨‍💻 Who can provide these permissions?** The Exasol administrator grants these permissions, as standard accounts may not have the required access to assign them independently.
{% endhint %}

<table><thead><tr><th width="198">Objects</th><th width="328">System Tables</th><th>Access Permission</th></tr></thead><tbody><tr><td>Schema</td><td><ul><li>sys.schema</li><li>extended_properties</li></ul></td><td>Select</td></tr><tr><td>Tables</td><td><ul><li>Information_Schema.Tables</li><li>fn_listextendedproperty</li></ul></td><td>Select</td></tr></tbody></table>

### Connection Configuration Steps

{% hint style="warning" %}
Users must have the Connector Creator role to configure a new connection.
{% endhint %}

1. Log in to OvalEdge, go to Administration > Connectors, click + **(New Connector)**, search for **Exasol**, and complete the required parameters.

{% hint style="info" %}
Fields marked with an asterisk (\*) are mandatory for establishing a connection.
{% endhint %}

<table><thead><tr><th width="221">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Exasol" is displayed as the selected connector type.</td></tr><tr><td>Credential Manager*</td><td><p>Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection.</p><p>Supported Credential Managers:</p><ul><li>Database</li><li>HashiCorp</li><li>AWS Secrets Manager</li><li>Azure Key Vault</li></ul></td></tr><tr><td>License Add-On</td><td><p></p><p></p><ul><li>Select the Auto Lineage Add-On checkbox to automatically build data lineage.</li></ul></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Exasol connection              </p><p>(Example: "Exasol_Prod").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.</td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Server*</td><td>Enter the IP address of the server where Exasol is hosted.</td></tr><tr><td>Port*</td><td>Exasol uses port 8563 by default. The port number can be modified as needed.</td></tr><tr><td>Database*</td><td><p>The ‘Database’ field defines the default schema that the connector uses to connect to the Exasol server.</p><p>Example: If the target database is sales_db, enter sales_db to connect directly instead of the default schema.</p></td></tr><tr><td>Driver*</td><td>By default, Exasol uses ‘com.exasol.jdbc.jdbc41.EXADriver.’ This field is not editable.</td></tr><tr><td>Username* </td><td>Enter the Username for the  Exasol server.</td></tr><tr><td>Password* </td><td>Enter the Password associated with the Exasol Username.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Exasol server:</p><ul><li>Automatic Mode: The system generates a connection string based on the provided credentials.</li><li>Manual Mode: Enter a valid connection string manually.</li></ul><p>Replace placeholders with actual server details:</p><ul><li>{server} refers to the Exasol host or IP address.</li><li>{sid} refers to the database name (schema).<br></li></ul><p>Authentication Plugins:<br>jdbc:exa:{server}:8563;schema={sid}</p><p></p><p>This is the default JDBC connection string used for connecting to Exasol. The schema parameter specifies the default schema to use after the connection is established.</p></td></tr><tr><td>Plugin Server</td><td>Enter the server name when running as a plugin server.</td></tr><tr><td>Plugin Port</td><td>Enter the port number on which the plugin is running.</td></tr></tbody></table>

**Default Governance Roles**

<table data-header-hidden><thead><tr><th width="221"></th><th></th></tr></thead><tbody><tr><td>Default Governance Roles*</td><td>Select the appropriate users or teams for each governance role from the drop-down list. All users and teams configured in OvalEdge Security are displayed for selection.</td></tr></tbody></table>

**Admin Roles**

<table data-header-hidden><thead><tr><th width="221"></th><th></th></tr></thead><tbody><tr><td>Admin Roles*</td><td>Select one or more users from the dropdown list for Integration Admin and Security &#x26; Governance Admin. All users configured in OvalEdge Security are available for selection.</td></tr></tbody></table>

**Number of Archive Objects**

<table data-header-hidden><thead><tr><th width="220"></th><th></th></tr></thead><tbody><tr><td>Number of Archive Objects*</td><td><p>This shows the number of recent metadata changes to a dataset at the source. By default, it is off. To enable it, toggle the Archive button and specify the number of objects to archive.</p><p>Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.</p></td></tr></tbody></table>

**Bridge**

<table data-header-hidden><thead><tr><th width="221"></th><th></th></tr></thead><tbody><tr><td>Select Bridge*</td><td><p>If applicable, select the bridge from the drop-down list.</p><p>The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.</p></td></tr></tbody></table>

2. After entering all connection details, the following actions can be performed:
   * Click **Validate** to verify the connection.
   * Click **Save** to store the connection for future use.
   * Click **Save & Configure** to apply additional settings before saving.
3. The saved connection will appear on the Connectors home page.

## Manage Connector Operations

### Crawl/Profile

{% hint style="warning" %}
To perform crawl and profile operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling and profiling.&#x20;

1. Navigate to the Connectors page and click **Crawl/Profile**.
2. Select the schemas to crawl.
3. The **Crawl** option is selected by default. Click the **Crawl & Profile** radio button to enable both operations.
4. Click **Run** to collect metadata from the connected source and load it into the **Data Catalog**.
5. After a successful crawl, the information appears in the **Data Catalog > Databases** tab.

The **Schedule** checkbox allows automated crawling and profiling at defined intervals, from a minute to a year.

1. Click the **Schedule** checkbox to enable the **Select Period** drop-down.
2. Select a time period for the operation from the drop-down menu.
3. Click **Schedule** to initiate metadata collection from the connected source.

The system will automatically execute the selected operation (**Crawl** or **Crawl & Profile**) at the scheduled time.

### Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors, including their health status.

**Managing connectors includes:**

* **Connectors Health**: Displays the current status of each connector, with a green icon for active connections and a red icon for inactive connections, helping monitor connectivity to data sources.
* **Viewing**: Click the **Eye** icon next to the connector name to view connector details, including Tables, Views, and Columns.&#x20;

**Nine Dots Menu Options:**

To view, edit, validate, configure, or delete connectors, click on the **Nine Dots** menu.

* **Edit Connector**: Update and revalidate the data source.
* **Validate Connector**: Check the integrity of the connection.
* **Settings**: Modify connector settings.
  * **Crawler**: Configure data extraction.
  * **Profiler**: Customize data profiling rules and methods.
  * **Access Instructions**: Add notes on how data can be accessed.
  * **Business Glossary Settings**: Manage term associations at the connector level.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

### Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

<table><thead><tr><th width="85.11114501953125">S.No.</th><th width="225.22216796875">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Error while validating EXASOL connection | Root cause: Connect timed out</td><td><p><strong>Error Description</strong>: The EXASOL connection validation failed because the system could not establish a connection within the defined timeout period.<br></p><p><strong>Resolution</strong>: Verify the EXASOL server’s network connectivity, firewall settings, and port configuration, then retry the connection to ensure proper connectivity.</p></td></tr></tbody></table>

***

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ovaledge.com/release8.1/connectors/connector-repositories/rdbms/exasol.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.