> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/denodo.md).

# Denodo

This article outlines the integration with the Denodo connector, enabling streamlined metadata management through crawling, profiling, data preview, data quality, querying, relationships, and lineage building (Auto & Manual), while ensuring secure authentication via Credential Manager.

<figure><img src="/files/8zzgFhzH0oy4xygmv6iD" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                         | RDBMS                |
| -------------------------------------------------------------------------- | -------------------- |
| OvalEdge Release Supported                                                 | Release6.x and later |
| <p>Connectivity</p><p>\[How the connection is established with Denodo]</p> | JDBC                 |
| Verified Denodo Version                                                    | 8                    |

{% hint style="info" %}
The Denodo connector validates with the listed “Verified Denodo Version” and supports other compatible Denodo versions. If there are any issues with validation or metadata crawling, please submit a support ticket for investigation and feedback.
{% endhint %}

Connectivity to the Denodo connector is established using a JDBC driver. The supported driver version is listed below:

| Driver Details | Version |
| -------------- | ------- |
| JDBC driver    | 9.0     |

### Connector Features

| Feature                                      |                                                                       Availability                                                                      |
| -------------------------------------------- | :-----------------------------------------------------------------------------------------------------------------------------------------------------: |
| Crawling                                     |                                                                            ✅                                                                            |
| Delta Crawling                               |                                                                            NA                                                                           |
| Profiling                                    |                                                                            ✅                                                                            |
| Query Sheet                                  |                                                                            ✅                                                                            |
| Data Preview                                 |                                                                            ✅                                                                            |
| Auto Lineage                                 | <p>✅<br>To learn more, click <a href="https://docs.ovaledge.com/release8.1/connectors/connector-repositories/rdbms/denodo/denodo-lineage">here</a>.</p> |
| Manual Lineage                               |                                                                            ✅                                                                            |
| Secure Authentication via Credential Manager |                                                                            ✅                                                                            |
| Data Quality                                 |                                                                            ✅                                                                            |
| DAM (Data Access Management)                 |                                                                            NA                                                                           |
| Bridge                                       |                                                                            ✅                                                                            |

{% hint style="info" %}
'NA' indicates that the respective feature is 'Not Applicable.'
{% endhint %}

### Metadata Mapping

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

<table><thead><tr><th width="143.666748046875">Denodo Object</th><th width="161.6666259765625">Denodo Attribute</th><th width="173.6666259765625">OvalEdge Attribute</th><th width="175.3333740234375">OvalEdge Category</th><th width="145.3333740234375">OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>Name</td><td>Schema</td><td>Schemas</td><td>Schema</td></tr><tr><td>Table</td><td>Table Name</td><td>Table</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Table Type</td><td>Table</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Table Comments</td><td>Source Description</td><td>Descriptions</td><td>Source Description</td></tr><tr><td>Columns</td><td>Column Name</td><td>Column</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Data Type</td><td>Column Type</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Description</td><td>Source Description</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Ordinal Position</td><td>Column Position</td><td>Table Columns</td><td>-</td></tr><tr><td>Columns</td><td>Length</td><td>Data Type Size</td><td>Table Columns</td><td>-</td></tr><tr><td>Views</td><td>View Name</td><td>View</td><td>Tables</td><td>View</td></tr><tr><td>Views</td><td>Text</td><td>View Query</td><td>Views</td><td>View</td></tr><tr><td>Procedures</td><td>Routine_Name</td><td>Name</td><td>Procedures</td><td>-</td></tr><tr><td>Procedures</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr><tr><td>Procedures</td><td>Routine_Definition</td><td>Procedure</td><td>Procedures</td><td>-</td></tr><tr><td>Functions</td><td>Routine_Name</td><td>Name</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>Routine_Definition</td><td>Function</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>Description</td><td>Source Description</td><td>Descriptions</td><td>-</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

### **Whitelisting Ports**

Whitelist the inbound port 9999 to allow OvalEdge to connect to the Denodo Server database.

{% hint style="warning" %}
Denodo uses port 9999 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 Denodo 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 Denodo administrator grants these permissions, as standard accounts may not have the required access to assign them independently.
{% endhint %}

| Objects       | System Tables/Objects | Access Permission |
| ------------- | --------------------- | ----------------- |
| Schema        | List Databases        | Select            |
| Tables        | Get\_Views()          | Select            |
| Columns       | Get\_View\_Columns()  | Select            |
| Views         | Get\_Views()          | Select            |
| Relationships | Get\_Associations()   | References        |

### 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 **Denodo**, 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="220.666748046875">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "Denodo" is displayed as the selected connector type.</td></tr><tr><td>SSL Enabled*</td><td>Set to True when the Denodo server is configured to accept SSL connections. Set it to False when the server does not use SSL.</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><br></p><ul><li>Select the Auto Lineage Add-On checkbox to automatically build data lineage.</li><li>Select the Data Quality Add-On checkbox to identify data quality issues using data quality rules and anomaly detection.</li></ul></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the Denodo connection              </p><p>(Example: "Denodo_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 server's IP address where Denodo is hosted.</td></tr><tr><td>Port*</td><td>Denodo uses port 9999 by default. The port number can be modified as needed.</td></tr><tr><td>Database*</td><td>Enter the name of the target Denodo database to establish the connection. </td></tr><tr><td>Driver*</td><td>By default, Denodo uses ‘com.denodo.vdp.jdbc.Driver.’ This field is not editable.</td></tr><tr><td>Username* </td><td>Enter the Username for the  Denodo server.</td></tr><tr><td>Password* </td><td>Enter the Password associated with the Denodo Username.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the Denodo 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 Denodo host or IP address.</li><li>{sid} refers to the Denodo database (Virtual Database).</li></ul><p>Authentication Plugins:<br>jdbc:vdb://{server}:9999/{sid}?publishCatalogsAsSchemas=true&#x26;ssl=false</p><p>This is the default authentication string used for connecting to Denodo.</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="220.6666259765625"></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="220.6666259765625"></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>

**No of Archive Objects**

<table data-header-hidden><thead><tr><th width="220.6666259765625"></th><th></th></tr></thead><tbody><tr><td>No 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="220.666748046875"></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:
   1. Click **Validate** to verify the connection.
   2. Click **Save** to store the connection for future use.
   3. 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.
4. 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 Databases, Tables, Table Columns, and Codes.&#x20;

**Nine Dots Menu Options:**

To view, edit, validate, configure, build lineage, 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.
  * **Anomaly Detection Settings**: Configure anomaly detection preferences at the connector level.
  * **Connection Pooling**: Allows configuring parameters such as maximum pool size, idle time, and timeouts directly within the application.
  * **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="84.55548095703125">S.No.</th><th width="239.4444580078125">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Error while validating HDFS connection Error occured while validating the HDFS connection : Can't get Kerberos realm</td><td><p>Error Description: The HDFS connection validation failed because Kerberos authentication could not be established. This issue can occur due to an incorrect or missing Kerberos configuration (krb5.conf), an invalid or mismatched keytab file, incorrect principal details, system time differences between the application server and Hadoop cluster, network connectivity issues, or an RPC Protection setting mismatch between the connector and the Hadoop environment.<br>Resolution: </p><ul><li>Verify that the krb5.conf file contains the correct Kerberos realm and KDC details.</li><li>Ensure the keytab file is valid, corresponds to the configured principal, and is placed in the correct location.</li><li>Confirm that the principal configured in the connector matches the principal associated with the keytab file.</li><li>Validate network connectivity between the application server and the Hadoop cluster using ping, telnet, or similar connectivity tests.</li><li>Ensure the required Hadoop hostnames are resolvable and correctly configured in DNS or the /etc/hosts file.</li><li>Verify that the system time and time zone are synchronized between the application server and the Hadoop cluster.</li><li>Confirm that the Hadoop RPC Protection setting configured in the connector matches the setting required by the Hadoop cluster. If secure communication is enforced, configure the RPC Protection type as Privacy.</li><li>Retry the connection validation after applying the required configuration updates.<br><br></li></ul></td></tr><tr><td>2</td><td>Access Denied while attempting to list files in the specified HDFS folder.</td><td><p>Error Description: The HDFS connector cannot access the specified folder because the configured user lacks sufficient permissions to view or list files in that location.<br>Resolution: </p><ul><li>Verify that the configured HDFS user has the required read and execute permissions on the target folder.</li><li>Confirm that the folder path specified in the connector configuration is correct.</li><li>Check HDFS Access Control Lists (ACLs) and file system permissions for the affected directory.</li><li>Ensure that Kerberos authentication is configured correctly if the HDFS cluster is secured.</li><li>Validate that the user principal or service account has access to the target HDFS path.</li><li>Review HDFS NameNode and audit logs for additional permission-related details.</li><li>Retry the operation after updating the required permissions.</li></ul></td></tr><tr><td>3</td><td>Error while uploading file to HDFS: Destination path does not exist.</td><td><p>Error Description: The file upload to HDFS fails because the specified destination directory does not exist in the HDFS environment. As a result, the system cannot locate the target path where the file needs to be uploaded<br>Resolution: </p><ul><li>Verify that the destination HDFS path specified in the connector or upload configuration is correct.</li><li>Ensure that the target directory exists in HDFS before initiating the file upload.</li><li>Create the required directory in HDFS if it does not already exist.</li><li>Confirm that the configured user has sufficient permissions to access and write to the destination path.</li><li>Validate the HDFS URL and path format to ensure they match the actual HDFS directory structure.</li><li>Retry the file upload after correcting the destination path configuration.</li></ul></td></tr><tr><td>4</td><td>Error while validating HDFS connection: Kerberos authentication failed due to keytab file issues.</td><td><p>Error Description: The HDFS connection validation fails because Kerberos authentication cannot be completed using the configured keytab file. This may occur if the keytab file is missing, corrupted, inaccessible, or does not contain the correct principal information.<br>Resolution: </p><ul><li>Verify that the keytab file exists at the configured location.</li><li>Ensure that the application has the required permissions to access the keytab file.</li><li>Confirm that the keytab file contains the correct Kerberos principal.</li><li>Validate that the principal configured in the connector matches the principal stored in the keytab file.</li><li>Check that the keytab file is not corrupted and has been generated correctly.</li><li>Verify that the Kerberos realm and KDC details are configured correctly.</li><li>Ensure that system time is synchronized across the client and Kerberos server.</li><li>Retry the connection validation after correcting the keytab and Kerberos configuration.</li></ul></td></tr><tr><td>5</td><td>Kerberos principal authentication failed.</td><td><p>Error Description: The HDFS connection failed because the Kerberos principal could not be authenticated. This usually occurs when the configured principal name, keytab file, or Kerberos settings are incorrect, expired, or inaccessible.<br>Resolution: </p><ul><li>Verify that the Kerberos principal name is configured correctly in the connector.</li><li>Ensure that the associated keytab file exists and is accessible to the application.</li><li>Confirm that the principal is active and has not expired or been disabled in the Kerberos server.</li><li>Validate that the Kerberos realm and KDC details are correctly configured in the krb5.conf file.</li><li>Check that the system time is synchronized with the Kerberos server, as time differences can cause authentication failures.</li><li>Verify network connectivity between the application server and the Kerberos KDC server.</li><li>Renew or regenerate Kerberos credentials if they have expired.</li><li>Retry the connection after validating the Kerberos configuration and credentials.</li></ul></td></tr><tr><td>6</td><td>Timeout error while connecting to HDFS.</td><td><p>Error Description: The HDFS connection attempt timed out because the application could not establish communication with the HDFS cluster within the expected time. This issue is commonly caused by network connectivity problems, incorrect host or port configuration, unavailable HDFS services, or firewall restrictions. </p><p>Resolution: </p><ul><li>Verify that the HDFS NameNode hostname and port number are correct.</li><li>Ensure that the HDFS cluster services are running and accessible.</li><li>Test network connectivity between the application server and the HDFS environment.</li><li>Check for firewall, proxy, or security rules that may be blocking the connection.</li><li>Confirm that the configured user has the required access permissions.</li><li>Validate DNS resolution if host names are used in the connection configuration.</li><li>Increase the connection timeout setting if the HDFS environment has high network latency.</li><li>Retry the connection after resolving the connectivity or configuration issues.</li></ul></td></tr><tr><td>7</td><td>Errors encountered due to special characters in folder names.</td><td><p>Error Description: The HDFS crawl or metadata retrieval operation fails because one or more folder names contain special characters that are not supported by the connector or underlying file system processing. As a result, the connector is unable to access or process the affected folders. </p><p>Resolution: </p><ul><li>Identify the folders containing special characters in their names.</li><li>Rename the affected folders using supported alphanumeric characters and standard naming conventions.</li><li>Avoid using special characters that may not be supported by HDFS, operating systems, or connector processing.</li><li>Verify that folder paths are accessible and correctly configured in the connector.</li><li>Re-run the crawl or metadata extraction process after updating the folder names.</li><li>If renaming is not possible, exclude the affected folders from the crawl scope where applicable.</li></ul></td></tr><tr><td>8</td><td>Connection additional attributes cannot be null.</td><td><p>Error Description: The HDFS connector validation fails because one or more required additional connection attributes are missing or empty. The connector requires these attributes to establish a successful connection to the HDFS environment. </p><p>Resolution: </p><ul><li>Verify that all mandatory connection attributes are configured in the connector settings.</li><li>Ensure that no required additional attribute fields are left blank or contain null values.</li><li>Validate the format and values of the configured HDFS connection properties.</li><li>Review the connector configuration against the HDFS environment requirements.</li><li>Save the updated configuration and retry the connection validation.</li><li>If the issue persists, review the application logs to identify the specific missing attribute.</li></ul></td></tr><tr><td>9</td><td>Error related to file extensions encountered while processing files.</td><td><p>Error Description: The HDFS connector encountered files with unsupported, invalid, or unrecognized file extensions during processing. As a result, the connector could not successfully read or process the affected files. </p><p>Resolution: </p><ul><li>Verify that the files in the HDFS location have valid and supported file extensions.</li><li>Ensure that the file format matches the file extension being used.</li><li>Check for files with missing, incorrect, or corrupted extensions and update them as required.</li><li>Remove or exclude unsupported file types from the crawl path.</li><li>Confirm that the files are not corrupted and can be opened using the appropriate application.</li><li>Re-run the crawl or profiling job after correcting the file extensions and file formats.</li></ul></td></tr><tr><td>10</td><td>An authentication attribute is required.</td><td><p>Error Description: HDFS connector validation fails due to a required authentication setting being missing. The connector cannot establish a connection to the HDFS environment without the necessary authentication information. </p><p>Resolution: </p><ul><li>Verify that all required authentication fields are configured in the connector.</li><li>Ensure that the appropriate authentication method (for example, Kerberos or Simple Authentication) is selected.</li><li>Confirm that all mandatory credentials and authentication properties are provided.</li><li>Validate that any required configuration files, such as krb5.conf or keytab files, are correctly specified and accessible.</li><li>Review the connector configuration for any missing or invalid authentication parameters.</li><li>Retry the connection validation after updating the authentication settings.</li></ul></td></tr><tr><td>11</td><td>Connection errors encountered while attempting to connect to the HDFS cluster; unable to determine whether the issue is related to configuration settings or the HDFS environment.</td><td><p>Error Description: The HDFS connection attempt failed, but the exact cause could not be determined. The issue may be related to incorrect connector settings, network connectivity problems, authentication failures, or an issue within the HDFS cluster environment. </p><p>Resolution: </p><ul><li>Verify that the HDFS URL, hostname, and port number are correctly configured.</li><li>Ensure that the HDFS cluster is running and accessible from the application environment.</li><li>Validate network connectivity between the application and the HDFS cluster.</li><li>Confirm that the configured authentication settings (Kerberos, user credentials, or certificates) are correct.</li><li>Check whether other users or applications can successfully connect to the same HDFS cluster.</li><li>Review HDFS NameNode and DataNode logs for any cluster-side errors.</li><li>Verify that the configured user has the required permissions to access HDFS resources.</li><li>Retry the connection after validating the configuration and cluster availability.</li></ul></td></tr></tbody></table>

### FAQs

<details>

<summary><strong>What's the difference between a database and a schema in Denodo?</strong></summary>

In Denodo, databases serve as top-level containers that organize views and other associated objects. The connection follows the format: jdbc:vdb://\<server>:\<port>/{database}?publishCatalogsAsSchemas=true\&ssl={sslenable}, where the database name is provided in the SID field. Each database can include views (logical tables), stored procedures, and other resources. To list available databases, use the command LIST DATABASES;. Denodo primarily relies on views as its core data objects rather than traditional physical tables.

</details>

<details>

<summary>Why does my connection string keep changing?</summary>

The system automatically generates the connection string based on the provided inputs. Ensure that the Server, Port, Database (SID), and SSL Enabled fields are correctly configured, as the connection string is formatted in the pattern:jdbc:vdb://\<server>:\<port>/{sid}?publishCatalogsAsSchemas=true\&ssl={sslenable}. If manual edits are made, confirm that the string follows the expected structure. After modifying any field, review the connection string to ensure it is accurate before saving. The publishCatalogsAsSchemas parameter is included by default.

</details>

<details>

<summary>Why can't I see any databases when trying to crawl? </summary>

This issue is related to insufficient permissions. Verify that the user has the required privileges to list databases, as the system executes the LIST DATABASES; command. Review Denodo error logs for any permission-related messages and confirm that the user can run LIST DATABASES; directly in Denodo. Additionally, ensure that the Denodo server is accessible and operational, and that the connection is successfully established.

</details>

<details>

<summary>Why are only some databases visible while others do not appear?</summary>

The system retrieves available databases using the LIST DATABASES command, which returns only the databases the user is permitted to access. Missing databases may indicate that the connected user lacks the necessary privileges or that Denodo security policies restrict specific databases. Access may be limited to databases the user owns or to which the user has been explicitly granted permissions. Confirm with the Denodo administrator that the required privileges are assigned, and use LIST DATABASES; to verify which databases the user can access.

</details>

<details>

<summary>What permissions are needed to view database objects when views appear in one database but not in others?</summary>

To view the list of views in a Denodo database, the user must have database access privileges and SELECT privileges on the views. Viewing view metadata also requires access to the GET\_VIEWS() function. The system retrieves view information using the query: SELECT name, description FROM GET\_VIEWS() WHERE input\_database\_name = ?. You can verify access by running:\
SELECT name FROM GET\_VIEWS() WHERE input\_database\_name = '\<database\_name>';\
Ensure that the required privileges are granted on the target Denodo database.

</details>

<details>

<summary>Why do connection pool errors occur?</summary>

Connection pool issues may arise when the number of concurrent connections exceeds configured limits, when connections are not properly closed, or when network timeouts leave stale connections in the pool. The system uses a BasicDataSource connection pool for Denodo, so review the pool configuration to ensure appropriate sizing. Monitor active connections to identify potential leaks and adjust pool settings as needed. Restarting the application can help clear stale connections. Additionally, verify that the pool size does not exceed the connection limits enforced by the Denodo server.

</details>

<details>

<summary>How can the configuration be switched from using direct database credentials to using the credential manager?</summary>

To use the credential manager, select the appropriate type from the dropdown (e.g., AWS Secrets Manager or HashiCorp Vault), then provide the secret name or path where the credentials are stored. The system retrieves the username, password, and connection details directly from the configured credential manager. Ensure the credential manager is configured correctly and accessible. After switching to credential-based authentication, test the connection to confirm successful credential retrieval.

</details>

***

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.ovaledge.com/release8.2/connectors/connector-repositories/rdbms/denodo.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.