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

<figure><img src="/files/AUeCYmb2Y242nIK5dne6" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                              | RDBMS       |
| ------------------------------------------------------------------------------- | ----------- |
| OvalEdge Releases Supported                                                     | Release8.1  |
| <p>Connectivity</p><p>\[How the connection is established with H2 Database]</p> | JDBC driver |

### 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 H2 Database and mapped to the corresponding UI assets.

<table><thead><tr><th width="183.4000244140625">H2 Database Object</th><th width="196.199951171875">H2 Database Attribute</th><th width="170.4000244140625">OvalEdge Attribute</th><th width="172.800048828125">OvalEdge Category</th><th width="146.4000244140625">OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>Schema name </td><td>Container identifier</td><td>Container</td><td>Container</td></tr><tr><td>Table</td><td>Table name</td><td>Table name</td><td>Table</td><td>Entity</td></tr><tr><td>Views</td><td>View name</td><td>View name </td><td>View </td><td>Entity</td></tr><tr><td>Functions </td><td>Function name</td><td>Function name</td><td>Function / Procedure</td><td>Function</td></tr><tr><td>Procedures</td><td>Procedure name</td><td>Name</td><td>Function / Procedure</td><td>Procedure</td></tr><tr><td>Sequences</td><td>Sequence name</td><td>Sequence name</td><td>Sequence</td><td>Sequence</td></tr><tr><td>Indexes</td><td>Index identifier</td><td>Index identifier</td><td>Index</td><td>Index</td></tr><tr><td>Triggers</td><td>Trigger name</td><td>Trigger identifier</td><td>Trigger</td><td>Trigger</td></tr><tr><td>Columns</td><td>Column name and data type</td><td>Column name and data type</td><td>Column</td><td>Column</td></tr></tbody></table>

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

{% hint style="warning" %}
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.
{% endhint %}

**Service Account User Permissions**

{% hint style="warning" %}
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.
{% endhint %}

{% hint style="info" %}
👨‍💻 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.
{% endhint %}

| Operation                  | Objects                | System Tables                                        | Access Permission                   |
| -------------------------- | ---------------------- | ---------------------------------------------------- | ----------------------------------- |
| Connection Validation      | Database               | <p>-<br></p>                                         | Ability to connect and run Select 1 |
| Crawling                   | Schemas                | INFORMATION\_SCHEMA.SCHEMATA                         | Select                              |
| Crawling                   | Tables / Views         | INFORMATION\_SCHEMA.TABLES                           | Select                              |
| Crawling                   | Functions / Procedures | <p>Procedures</p><p>INFORMATION\_SCHEMA.ROUTINES</p> | 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

{% hint style="info" %}
Users are required to have the Connector Creator role in order to configure a new connection.
{% endhint %}

1. Log into the OvalEdge, go to **Administration > Connectors**, click + (New Connector), search for **H2 Database**, 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="219.59991455078125">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "<strong>H2 Database</strong>" 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 your selection.</p><p>Supported Credential Managers:</p><ul><li>OE Credential Manager</li><li>AWS Secrets Manager</li><li>HashiCorp Vault</li><li>Azure Key Vault</li></ul></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the H2 Database connection              </p><p>(<strong>Example</strong>: "H2 Database").</p></td></tr><tr><td>JDBC URL</td><td><p>Enter the complete JDBC connection string. When the value is provided, it overrides the individual Host, Port, and Database path fields. </p><p><strong>Example</strong>: jdbc:h2:tcp://localhost:9092/~/test </p></td></tr><tr><td>Connector Description</td><td>Enter a brief description of the connector.</td></tr><tr><td>Host*</td><td>Enter the H2 database host name for TCP/SSL Mode.</td></tr><tr><td>Port*</td><td>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.</td></tr><tr><td>Database Path*</td><td><p>Enter the database path to which the service account user has access within the H2 database. </p><p>(<strong>Example</strong>: ~/test, mem:db1, file path)</p></td></tr><tr><td>Username*</td><td><p>Enter the service account username set up to access the H2 database </p><p>(<strong>Example</strong>: "oesauser").</p></td></tr><tr><td>Password*</td><td>Enter the password associated with the service account user.</td></tr><tr><td>Use SSL/TLS</td><td>Enable SSL/TLS by clicking on the button.</td></tr></tbody></table>

| **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\*      | <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> |
| **Bridge**                   |                                                                                                                                                                                                                                                                                                                                      |
| Select Bridge\*              | <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>                                                                                  |

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="info" %}
To perform crawl operations, users must be assigned the Integration Admin role.
{% endhint %}

The **Crawl/Profile** button allows users to select one or more schemas for crawling&#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.&#x20;
4. Click **Run** to collect metadata from the connected source and load it into the OvalEdge **Data Catalog**.
5. 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.

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

<table><thead><tr><th width="84.20001220703125">S.No.</th><th width="228.60003662109375">Error Message(s)</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Invalid connection config.</td><td><p><strong>Error Description:</strong> </p><ul><li>Required connection details were missing during validation.</li></ul><p><strong>Resolution:</strong></p><ul><li>Open the connector settings.</li><li>Provide all mandatory fields.</li><li>Click Validate again.</li></ul></td></tr><tr><td>2</td><td>Database path is required.</td><td><p><strong>Error Description:</strong> </p><ul><li>Database path was not provided and JDBC URL override was not used.</li></ul><p><strong>Resolution:</strong></p><ul><li>Enter a valid Database path.</li><li>Or provide a full JDBC URL.</li><li>Retry validation.</li></ul></td></tr><tr><td>3</td><td>Host is required.</td><td><p><strong>Error Description:</strong> </p><ul><li>The host was missing for server mode when the JDBC URL was not provided.</li></ul><p><strong>Resolution:</strong></p><ul><li>Enter the Host value.</li><li>Verify port and mode (TCP/SSL).</li><li>Validate again.</li></ul></td></tr><tr><td>4</td><td>Connection failed.</td><td><p><strong>Error Description:</strong> </p><ul><li>JDBC connection or validation query failed.</li></ul><p><strong>Resolution:</strong></p><ul><li>Verify host, port, database path, and credentials.</li><li>Check network/firewall and SSL settings.</li><li>Retry validation.</li></ul></td></tr><tr><td>5</td><td>Failed to get fields.</td><td><p><strong>Error Description:</strong> </p><ul><li>Metadata retrieval failed due to permission or schema access issues.</li></ul><p><strong>Resolution:</strong></p><ul><li>Verify access to INFORMATION_SCHEMA tables.</li><li>Ensure SELECT permissions on required objects.</li><li>Retry crawl.</li></ul></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/h2-database.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.