H2 Database
This article outlines the integration with H2 Database connector, enabling streamlined metadata management through features such as crawling, querying, and data preview. It also ensures secure authentication via Credential Manager.
Overview
Connector Details
Connector Category
RDBMS
OvalEdge Releases Supported
Release8.1
Connectivity
[How the connection is established with H2 Database]
JDBC driver
Connector Features
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 H2 Database and mapped to the corresponding UI assets.
Schema
Schema name
Container identifier
Container
Container
Table
Table name
Table name
Table
Entity
Views
View name
View name
View
Entity
Functions
Function name
Function name
Function / Procedure
Function
Procedures
Procedure name
Name
Function / Procedure
Procedure
Sequences
Sequence name
Sequence name
Sequence
Sequence
Indexes
Index identifier
Index identifier
Index
Index
Triggers
Trigger name
Trigger identifier
Trigger
Trigger
Columns
Column name and data type
Column name and data type
Column
Column
Set up a Connection
Prerequisites
The following are the prerequisites to establish a connection:
Network Access
Ensure outbound connectivity is allowed to the H2 Database server when using server mode.
The default port for H2 Database server mode is 9092. If a different port is configured, ensure the updated port is specified during connection setup and communication is properly established. For embedded modes (mem: or file:), port access is not required, but local file system access must be available.
Service Account User Permissions
It is recommended to use a separate service account to establish the connection to the data source, configured with the following minimum set of permissions.
👨💻 Who can provide these permissions? These permissions are typically granted by the H2 database administrator, as users may not have the required access to assign them independently.
Connection Validation
Database
-
Ability to connect and run Select 1
Crawling
Schemas
INFORMATION_SCHEMA.SCHEMATA
Select
Crawling
Tables / Views
INFORMATION_SCHEMA.TABLES
Select
Crawling
Functions / Procedures
Procedures
INFORMATION_SCHEMA.ROUTINES
Select
Crawling
Sequences
INFORMATION_SCHEMA.SEQUENCES
Select
Crawling
Indexes
INFORMATION_SCHEMA.INDEXES
Select
Crawling
Triggers
INFORMATION_SCHEMA.TRIGGERS
Select
Crawling
Columns
INFORMATION_SCHEMA.COLUMNS
Select
Crawling
Index Columns
INFORMATION_SCHEMA.INDEX_COLUMNS
Select
Query Sheet / Data Preview
Tables and Views
User schemas
Select
Connection Configuration Steps
Users are required to have the Connector Creator role in order to configure a new connection.
Log into the OvalEdge, go to Administration > Connectors, click + (New Connector), search for H2 Database, and complete the required parameters.
Fields marked with an asterisk (*) are mandatory for establishing a connection.
Connector Type
By default, "H2 Database" is displayed as the selected connector type.
Credential Manager*
Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.
Supported Credential Managers:
OE Credential Manager
AWS Secrets Manager
HashiCorp Vault
Azure Key Vault
Connector Name*
Enter a unique name for the H2 Database connection
(Example: "H2 Database").
JDBC URL
Enter the complete JDBC connection string. When the value is provided, it overrides the individual Host, Port, and Database path fields.
Example: jdbc:h2:tcp://localhost:9092/~/test
Connector Description
Enter a brief description of the connector.
Host*
Enter the H2 database host name for TCP/SSL Mode.
Port*
By default, the port number for the H2 database, "9092" is auto-populated. If required, the port number can be modified as per custom port number that is configured for your H2 database.
Database Path*
Enter the database path to which the service account user has access within the H2 database.
(Example: ~/test, mem:db1, file path)
Username*
Enter the service account username set up to access the H2 database
(Example: "oesauser").
Password*
Enter the password associated with the service account user.
Use SSL/TLS
Enable SSL/TLS by clicking on the button.
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.
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.
The saved connection will appear on the Connectors home page.
Manage Connector Operations
Crawl/Profile
To perform crawl operations, users must be assigned the Integration Admin role.
The Crawl/Profile button allows users to select one or more schemas for crawling
Navigate to the Connectors page and click Crawl/Profile.
Select the schemas to crawl.
The Crawl option is selected by default.
Click Run to collect metadata from the connected source and load it into the OvalEdge Data Catalog.
After a successful crawl, the information appears in the Data Catalog > Databases/Tables/Table Columns tab.
The Schedule checkbox allows automated crawling at defined intervals, from a minute to a year.
Click the Schedule checkbox to enable the Select Period drop-down.
Select a time period for the operation from the drop-down menu.
Click Schedule to initiate metadata collection from the connected source.
The system will automatically execute the crawl operation 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 using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.
Viewing: Click the Eye icon next to the connector name to view connector details, including databases, tables, columns, and codes.
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 connection's integrity.
Settings: Modify connector settings.
Crawler: Configure data extraction.
Query Policies: Define query execution rules based on roles.
Access Instructions: Add notes on how data can be accessed.
Business Glossary Settings: Manage term associations at the connector level.
Delete Connector: Remove a connector with confirm
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.
1
Invalid connection config.
Error Description:
Required connection details were missing during validation.
Resolution:
Open the connector settings.
Provide all mandatory fields.
Click Validate again.
2
Database path is required.
Error Description:
Database path was not provided and JDBC URL override was not used.
Resolution:
Enter a valid Database path.
Or provide a full JDBC URL.
Retry validation.
3
Host is required.
Error Description:
The host was missing for server mode when the JDBC URL was not provided.
Resolution:
Enter the Host value.
Verify port and mode (TCP/SSL).
Validate again.
4
Connection failed.
Error Description:
JDBC connection or validation query failed.
Resolution:
Verify host, port, database path, and credentials.
Check network/firewall and SSL settings.
Retry validation.
5
Failed to get fields.
Error Description:
Metadata retrieval failed due to permission or schema access issues.
Resolution:
Verify access to INFORMATION_SCHEMA tables.
Ensure SELECT permissions on required objects.
Retry crawl.
Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA
Last updated
Was this helpful?