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.

Overview

Connector Details

Connector Category	RDBMS
Connector Version	Release7.1
Releases Supported (Available from)	Release6.0
Connectivity [How the connection is established with Denodo]	JDBC
Verified Denodo Version	8

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.

Connector Features

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

'NA' indicates that the respective feature is 'Not Applicable.'

Metadata Mapping

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

Denodo Object	Denodo Attribute	OvalEdge Attribute	OvalEdge Category	OvalEdge Type
Schema	Name	Schema	Schemas	Schema
Table	Table Name	Table	Tables	Table
Table	Table Type	Table	Tables	Table
Table	Table Comments	Source Description	Descriptions	Source Description
Columns	Column Name	Column	Table Columns	-
Columns	Data Type	Column Type	Table Columns	-
Columns	Description	Source Description	Table Columns	-
Columns	Ordinal Position	Column Position	Table Columns	-
Columns	Length	Data Type Size	Table Columns	-
Views	View Name	View	Tables	View
Views	Text	View Query	Views	View
Procedures	Routine_Name	Name	Procedures	-
Procedures	Description	Source Description	Descriptions	-
Procedures	Routine_Definition	Procedure	Procedures	-
Functions	Routine_Name	Name	Functions	-
Functions	Routine_Definition	Function	Functions	-
Functions	Description	Source Description	Descriptions	-

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.

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.

Service Account User Permissions

Use a dedicated service account to establish the connection to the data source, configured with the following minimum set of permissions.

👨‍💻 Who can provide these permissions? The Denodo administrator grants these permissions, as standard accounts may not have the required access to assign them independently.

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

Users must have the Connector Creator role to configure a new connection.

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

Fields marked with an asterisk (*) are mandatory for establishing a connection.

Field Name	Description
Connector Type	By default, "Denodo" is displayed as the selected connector type.
SSL Enabled*	Set to True when the Denodo server is configured to accept SSL connections. Set it to False when the server does not use SSL.
Credential Manager*	Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on the selection. Supported Credential Managers: Database HashiCorp AWS Secrets Manager Azure Key Vault
License Add-On	Select the Auto Lineage Add-On checkbox to automatically build data lineage. Select the Data Quality Add-On checkbox to identify data quality issues using data quality rules and anomaly detection.
Connector Name*	Enter a unique name for the Denodo connection (Example: "Denodo_Prod").
Connector Environment	Select the environment (Example: PROD, STG) configured for the connector.
Connector Description	Enter the description related to the connector.
Server*	Enter the server's IP address where Denodo is hosted.
Port*	Denodo uses port 9999 by default. The port number can be modified as needed.
Database*	Enter the name of the target Denodo database to establish the connection.
Driver*	By default, Denodo uses ‘com.denodo.vdp.jdbc.Driver.’ This field is not editable.
Username*	Enter the Username for the Denodo server.
Password*	Enter the Password associated with the Denodo Username.
Connection String	Configure the connection string for the Denodo server: Automatic Mode: The system generates a connection string based on the provided credentials. Manual Mode: Enter a valid connection string manually. Replace placeholders with actual server details: {server} refers to the Denodo host or IP address. {sid} refers to the Denodo database (Virtual Database). Authentication Plugins: jdbc:vdb://{server}:9999/{sid}?publishCatalogsAsSchemas=true&ssl=false This is the default authentication string used for connecting to Denodo.
Plugin Server	Enter the server name when running as a plugin server.
Plugin Port	Enter the port number on which the plugin is running.

Default Governance Roles

Default Governance Roles*	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.

Admin Roles

Admin Roles*	Select one or more users from the dropdown list for Integration Admin and Security & Governance Admin. All users configured in OvalEdge Security are available for selection.

No of Archive Objects

No Of Archive Objects*	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. Example: Setting it to 4 retrieves the last four changes, displayed in the 'Version' column of the 'Metadata Changes' module.

Bridge

Select Bridge*	If applicable, select the bridge from the drop-down list. The drop-down list displays all active bridges configured in OvalEdge. These bridges enable communication between data sources and OvalEdge without altering firewall rules.

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

2. The saved connection will appear on the Connectors home page.

Manage Connector Operations

Crawl/Profile

To perform crawl and profile operations, users must be assigned the Integration Admin role.

The Crawl/Profile button allows users to select one or more schemas for crawling and profiling.

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.

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.

S.No.	Error Message(s)	Error Description & Resolution
1	"Authentication failed"	Error Description: Indicates that the system could not verify the provided credentials during the authentication process. Resolution: Re-enter valid credentials or update incorrect login details, and ensure the account is active and authorized.
2	"Communications link failure" or "Connection refused"	Error Description: Occurs when the client cannot establish a network connection with the database server. This happens due to network interruptions, incorrect host/port settings, or the server not accepting connections. Resolution: Verify network connectivity, server availability, and the correctness of host and port details. Ensure the database service is running and not blocked by firewall rules or connection limits.
3	"Invalid number format for port number"	Error Description: Occurs when the provided port value contains non-numeric characters or falls outside the valid numeric range. The system cannot interpret the port as a valid integer. Resolution: Enter a numeric port value within the supported range (typically 1–65535). Verify and correct any accidental characters or formatting issues in the port field.
4	"Database does not exist"	Error Description: The system cannot locate the specified database because the name is incorrect, missing, or not yet created. Resolution: Verify the database name in the configuration and create the database if it does not already exist.
5	"Failed to retrieve DataSource from DataSourceProvider"	Error Description: The system could not load the required DataSource because the DataSourceProvider returned an invalid configuration or connection object. Resolution: Verify the DataSourceProvider configuration, ensure the DataSource is correctly defined, and re-establish the connection to restore access.

FAQs

What's the difference between a database and a schema in Denodo?

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.

Why does my connection string keep changing?

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.

Why can't I see any databases when trying to crawl?

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.

Why are only some databases visible while others do not appear?

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.

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

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.

Why do connection pool errors occur?

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.

How can the configuration be switched from using direct database credentials to using the credential manager?

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.

---

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