> 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.1/connectors/connector-repositories/rdbms/sap-hana.md).

# SAP HANA

This article outlines the integration with the SAP HANA connector, enabling streamlined metadata management through features such as crawling, delta crawling, profiling, data preview, data quality, querying, and lineage building (Auto & Manual).

The connector establishes connectivity to the SAP HANA database through JDBC. Access to the SAP HANA database is established using the configured username and password to crawl and profile schemas, map the metadata to the corresponding Data Catalog assets, and build lineage.

<figure><img src="https://1121831267-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFZv5WsZmBfXjiJfMU2zR%2Fuploads%2FMXhM5h2x7RMcmoX4vduF%2Fimage.png?alt=media&amp;token=f912b5b8-7874-4c78-be86-154ac16f15ac" alt=""><figcaption></figcaption></figure>

## Overview

### Connector Details

| Connector Category                                                           | RDBMS                  |
| ---------------------------------------------------------------------------- | ---------------------- |
| Connector Version                                                            | Release6.3.x and later |
| <p>Connectivity</p><p>\[How the connection is established with SAP HANA]</p> | JDBC                   |
| Verified SAP HANA Version                                                    | 2                      |

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

### Connector Features

<table data-search="false"><thead><tr><th>Feature</th><th align="center">Availability</th></tr></thead><tbody><tr><td>Crawling</td><td align="center">✅</td></tr><tr><td>Incremental Crawling</td><td align="center">✅</td></tr><tr><td>Profiling</td><td align="center">✅</td></tr><tr><td>Query Sheet</td><td align="center">✅</td></tr><tr><td>Data Preview</td><td align="center">✅</td></tr><tr><td>Auto Lineage</td><td align="center">✅</td></tr><tr><td>Manual Lineage</td><td align="center">✅</td></tr><tr><td>Secure Authentication via Credential Manager</td><td align="center">✅</td></tr><tr><td>Data Quality</td><td align="center">✅</td></tr><tr><td>DAM (Data Access Management)</td><td align="center">❌</td></tr><tr><td>Bridge</td><td align="center">✅</td></tr></tbody></table>

{% hint style="info" %}
In Bridge Mode, subsequent crawls of Tables, Views, Relationships, Stored Procedures, and Functions retrieve only new or modified metadata after the initial crawl.
{% endhint %}

### Metadata Mapping

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

<table><thead><tr><th width="164.96295166015625">SAP HANA Object</th><th width="174.0369873046875">SAP HANA Attribute</th><th width="169.81488037109375">OvalEdge Attribute</th><th width="172.6663818359375">OvalEdge Category</th><th width="174.555419921875">OvalEdge Type</th></tr></thead><tbody><tr><td>Schema</td><td>Schema Name</td><td>Schema</td><td>Databases</td><td>Schema</td></tr><tr><td>Schema</td><td>Schema Comment</td><td>Source Description</td><td>Databases</td><td>Schema</td></tr><tr><td>Table</td><td>Tablename</td><td>Table</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Table_Type</td><td>Type</td><td>Tables</td><td>Table</td></tr><tr><td>Table</td><td>Tablecomment/ DDTEXT</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>Column Name</td></tr><tr><td>Columns</td><td>Data_Type</td><td>Column Type</td><td>Table Columns</td><td>OE Column Type</td></tr><tr><td>Columns</td><td>Comments/ DDTEXT</td><td>Source Description</td><td>Table Columns</td><td>Column Description</td></tr><tr><td>Columns</td><td>SCRTEXT_M</td><td>Title</td><td>Table Columns</td><td>Column Title</td></tr><tr><td>Columns</td><td>Data_Length</td><td>Data Type Size</td><td>Table Columns</td><td>Column Length</td></tr><tr><td>Columns</td><td>Ordinal Position</td><td>Column Position</td><td>Table Columns</td><td>Column Position</td></tr><tr><td>View</td><td>View Name</td><td>View</td><td>Tables</td><td>View</td></tr><tr><td>View</td><td>Text</td><td>View Query</td><td>Views</td><td>View</td></tr><tr><td>Procedures</td><td>Name</td><td>Name</td><td>Procedures</td><td>-</td></tr><tr><td>Functions</td><td>Name</td><td>Name</td><td>Functions</td><td>-</td></tr><tr><td>Functions</td><td>Text</td><td>Function Query</td><td>Functions</td><td>-</td></tr><tr><td>Indexes</td><td>Index name</td><td>Index</td><td>Indexes</td><td>Index</td></tr><tr><td>Indexes</td><td>If Unique</td><td>Yes /No</td><td>Indexes</td><td>Index</td></tr></tbody></table>

## Set up a Connection

### Prerequisites

The prerequisites to establish a connection:

#### **Whitelisting Ports**

Whitelist the inbound port 30015 to allow OvalEdge to connect to the SAP HANA Server database.

{% hint style="warning" %}
SAP HANA uses port 30015 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 SAP HANA Server.
{% endhint %}

#### **External Supporting Files**

{% hint style="info" %}
The required external JAR files are included as part of the **OvalEdge installation artifacts**. For driver installation and configuration details, refer to the [**Connector Drivers Setup Guide**](https://docs.ovaledge.com/connectors/additional-requirements/connector-drivers-setup-guide). Please contact the **OvalEdge Team** for assistance related to the driver files and configuration setup.
{% 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 SAP HANA administrator grants these permissions, as standard accounts may not have the required access to assign them independently.
{% endhint %}

<table data-search="false"><thead><tr><th width="218.77777099609375">Objects</th><th width="258.22216796875">System Tables</th><th>Access Permissions</th></tr></thead><tbody><tr><td>Validate Connection</td><td>Sys.M_Database</td><td>Select</td></tr><tr><td>Schema</td><td>Schemas</td><td>Select</td></tr><tr><td>Tables</td><td>Tables</td><td>Select</td></tr><tr><td>Tables</td><td>DD02T</td><td>Select</td></tr><tr><td>Table Columns</td><td>Table_Columns</td><td>Select</td></tr><tr><td>Table Columns</td><td>View_Columns</td><td>Select</td></tr><tr><td>Table Columns</td><td>DD03M</td><td>Select</td></tr><tr><td>Views</td><td>Public.Views</td><td>Select</td></tr><tr><td>Calculation Views</td><td>_Sys_Repo.Active_Object</td><td>Select</td></tr><tr><td>Procedures</td><td>Public.Procedures</td><td>Execute</td></tr><tr><td>Functions</td><td>Public.Functions</td><td>Execute</td></tr><tr><td>Indexes</td><td>Index_Columns</td><td>Select</td></tr><tr><td>Relationships</td><td>REFERENTIAL_CONSTRAINTS</td><td>References</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 **SAP HANA**, 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.111083984375">Field Name</th><th>Description</th></tr></thead><tbody><tr><td>Connector Type</td><td>By default, "SAP HANA" 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><p>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/additional-requirements/credential-manager-configuration">here</a>.</p></td></tr><tr><td>License Add-On</td><td><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><p>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/license-types-and-add-ons">here</a>.</p></td></tr><tr><td>Connector Name*</td><td><p>Enter a unique name for the SAP HANA connection              </p><p>(Example: "SAPHANA_Prod").</p></td></tr><tr><td>Connector Environment</td><td>Select the environment (Example: PROD, STG) configured for the connector.<br>For more details, click <a href="https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/prerequisites#connector-environment">here</a>.</td></tr><tr><td>Connector Description</td><td>Enter the description related to the connector.</td></tr><tr><td>Server*</td><td>Enter the SAP HANA host name or IP address in the Server field. The IP address is the network address of the server where SAP HANA is hosted</td></tr><tr><td>Port*</td><td>SAP HANA uses port 30015 by default. The port number can be modified as needed.</td></tr><tr><td>Database*</td><td>Enter the name of the target SAP HANA database to establish the connection. </td></tr><tr><td>Driver*</td><td>By default, SAP HANA uses ‘com.sap.db.jdbc.Driver.’ This field is not editable.</td></tr><tr><td>Username* </td><td>Enter the SAP HANA database account name configured for authentication.</td></tr><tr><td>Password* </td><td>Enter the SAP HANA database user’s password associated with the provided username.</td></tr><tr><td>Connection String</td><td><p>Configure the connection string for the SAP HANA 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 SAP HANA host or IP address.</li></ul><p>Authentication Plugins:<br>jdbc:sap://{server}:30015/?autocommit=false</p><p>This is the default authentication string used for connecting to SAP HANA.</p></td></tr><tr><td><p>Enter schema for DD </p><p>tables</p></td><td>Enter the schema name where the Data Dictionary (DD) tables are stored in the SAP HANA system.</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.11114501953125"></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.11114501953125"></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="221.111083984375"></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="221.11114501953125"></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.

**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.
  * **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.
  * **Connection Pooling**: Configure database connection pool parameters to optimize database connectivity and resource utilization. For more details, click [here](https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings#connection-pooling).
  * **Lineage**: Configure Server Dialects for source code parsing and Connector Priority for table lineage connection.
  * **Others**: Configure notification recipients for metadata changes.
* **Build Lineage**: Automatically build data lineage using source code parsing.
* **Delete Connector**: Remove a connector with confirmation.

For more details on connector settings, click [here](https://docs.ovaledge.com/release8.1/connectors/introduction-to-connectors/setup-and-connectivity/connector-settings).

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

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="84.25">S. No</th><th width="217.80078125">Error Message</th><th width="394.49609375">Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>SAP HANA connection validation fails</td><td><p>Connection validation may fail if the SAP HANA database name is not correctly identified.<br><strong>Resolution:</strong></p><ul><li>If validation fails, switch the connection string to <strong>Manual</strong> mode.</li><li>Add <code>databaseName=&#x3C;actual HANA DB></code> to the connection string.</li><li>Save the connection details and revalidate the connection.</li></ul></td></tr><tr><td>2</td><td>Error while validating connection: Failed to obtain JDBC Connection; nested exception is java.lang.ClassNotFoundException: com.sap.db.jdbc.Driver</td><td><p>The SAP HANA JDBC driver is not included in the standard application package and must be added separately.</p><p>Resolution:</p><ul><li>Add the SAP HANA JDBC driver file under the Third Party JAR section.</li><li>Ensure the driver file name matches the driver referenced in the connector configuration form.</li><li>Validate the connection again after confirming the driver file placement.</li></ul></td></tr><tr><td>3</td><td>Error while validating connection: Failed to obtain JDBC Connection; nested exception is com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC general error, invalid database name specified</td><td><p>The database name entered in the setup form does not match the database available on the SAP HANA system.</p><p>Resolution:</p><ul><li>Run the following query directly on the SAP HANA system to check the current database name:<br>select DATABASE_NAME from SYS.M_DATABASE</li><li>Enter the database name in the setup form exactly as returned by the lookup.</li><li>Validate the connection again after saving the corrected database name.</li></ul></td></tr><tr><td>4</td><td>Error while validating connection: Failed to obtain JDBC Connection; nested exception is com.sap.db.jdbc.exceptions.JDBCConnectException: SAP DBTech JDBC, cannot connect to the configured host and port, connection timed out</td><td><p>The configured SAP HANA host or port cannot be reached from the application.</p><p>Resolution:</p><ul><li>Verify that the server address and port match the SAP HANA system configuration.</li><li>If a Bridge is used, confirm that the same host and port are reachable through the Bridge.</li><li>Check firewall and network access rules that may be blocking the connection.</li></ul></td></tr><tr><td>5</td><td>Authentication failed</td><td><p>Indicates that the system could not verify the provided credentials due to incorrect or missing authentication details.<br><strong>Resolution:</strong></p><p>Verify the username and password, ensure the correct authentication method is used, and retry after confirming the credentials are valid.</p></td></tr><tr><td>6</td><td>Username or password is wrong</td><td><p>The authentication attempt failed because the provided username or password does not match the stored credentials.<br><strong>Resolution:</strong></p><p>Verify that the correct username and password are entered and update or reset the credentials if necessary.</p></td></tr></tbody></table>

{% endtab %}

{% tab title="Crawling" %}

<table data-search="true"><thead><tr><th width="87.0078125">S. No.</th><th width="189.7578125">Error Message</th><th>Error Description &#x26; Resolution</th></tr></thead><tbody><tr><td>1</td><td>Crawl completed with errors: SAP DBTech JDBC insufficient privilege, not authorized</td><td><p>The connection account does not have the required permissions to retrieve the requested objects.</p><p>Resolution:</p><ul><li>Grant read-type permission on tables, views, and calculation views.</li><li>Grant EXECUTE permission on procedures and functions so their definitions can be retrieved.</li><li>Grant the required permission to read primary key and foreign key constraints so table relationships can be identified.</li></ul></td></tr><tr><td>2</td><td>Table and column descriptions remain empty after a successful crawl, even though a schema name has been entered in the setup form</td><td><p>SAP HANA stores descriptions either with the table definition or separately in two dedicated description tables.</p><p>Resolution:</p><ul><li>Grant read permission on the two tables that store table and column descriptions within the schema entered in the setup form.</li><li>Verify that the schema entered in the setup form contains those two description tables.</li><li>If the schema field is left empty, only descriptions entered when the table was created are retrieved.</li></ul></td></tr><tr><td>3</td><td>Index count shown in the crawl summary does not match the indexes found while browsing individual tables</td><td><p>Index details are recorded at the individual table level and are not fully represented at the summary or schema level.</p><p>Resolution:</p><ul><li>Open the summary page of the specific table to view its index details.</li><li>Review the crawl job log for the relevant run to identify tables containing indexes.</li><li>For large environments, index details can be added to the job log for easier identification as a known area for improvement.</li></ul></td></tr><tr><td>4</td><td>Error when trying to see the columns in a table</td><td><p>The system fails to load or display the column metadata for a selected table due to missing permissions, connectivity issues, or incomplete metadata retrieval.<br><strong>Resolution:</strong></p><ul><li>Verify database permissions.</li><li>Ensure the connection is active and stable.</li><li>Refresh or reindex the metadata so the system can retrieve and display the table columns correctly.</li></ul></td></tr><tr><td>5</td><td>Can't find any schemas</td><td><p>The system cannot retrieve schema metadata from the connected database, resulting in an empty or missing schema list.<br><strong>Resolution:</strong></p><ul><li>Verify database permissions.</li><li>Ensure the user has access to schema metadata.</li><li>Re-test the connection after confirming the database is reachable.</li></ul></td></tr><tr><td>6</td><td>Modified Views, Procedures, or Functions are not appearing after Delta Crawl</td><td><p>Delta crawl does not fetch newly modified Views, Procedures, or Functions.<br><strong>Resolution:</strong></p><ul><li>Ensure Bridge mode is enabled.</li><li>Verify the metadata object was modified after the previous crawl.</li><li>Confirm the connector has the required metadata access permissions.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

## FAQs

{% tabs %}
{% tab title="Connectivity" %}

<table data-search="true"><thead><tr><th width="88.1171875">S. No.</th><th width="174.43359375">Question</th><th>Answer</th></tr></thead><tbody><tr><td>1</td><td>Why is an external driver file needed to connect to SAP HANA?</td><td><p>The SAP HANA JDBC driver is not included in the application's default package.</p><ul><li>Upload the required driver file under the Third-Party File section.</li><li>The driver must be uploaded before the SAP HANA connection can be created and validated.</li></ul></td></tr><tr><td>2</td><td>How can the correct database name be found before setting up the connection?</td><td><p>The exact database name can be obtained directly from SAP HANA.</p><ul><li>Run a lookup query against the system view under the SYS schema that stores the current database name.</li><li>Enter the returned value exactly in the database name field of the setup form.</li><li>An incorrect database name prevents connection validation from succeeding.</li></ul></td></tr><tr><td>3</td><td>Does the SAP HANA connector support single sign-on or additional login verification steps?</td><td><p>No. Currently, the connector supports only a plain username and password.</p><ul><li>This applies to the main connection setup.</li><li>It also applies to the optional remote login option used in query policies.</li><li>Single sign-on and additional verification steps are not currently supported and may be considered for a future enhancement.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Crawling" %}

<table data-search="true"><thead><tr><th width="86.890625">S. No.</th><th width="190.5390625">Question</th><th>Answer</th></tr></thead><tbody><tr><td>1</td><td>Why does the schema field in the setup form matter for descriptions?</td><td><p>SAP HANA supports two types of table and column descriptions:</p><ul><li>Table-creation description: Entered when the table is created and retrieved automatically.</li><li>Business description: Maintained separately in two dedicated system tables.</li></ul><p>When the schema field is populated with the schema containing the two description tables, the connector retrieves the business descriptions from those tables.</p><p>If the schema field is left blank, only the table-creation descriptions are retrieved.</p></td></tr><tr><td>2</td><td>What permissions are needed on the SAP HANA side for the connection to work correctly?</td><td><p>The following permissions are required:</p><ul><li>Read-type permission: Tables, views, and calculation views.</li><li>EXECUTE permission: Procedures and functions.</li><li>Required constraint-read permission: Primary key and foreign key constraints for relationship discovery.</li><li>Read permission: The two dedicated description tables when separately maintained descriptions need to be retrieved.</li></ul></td></tr><tr><td>3</td><td>What is the difference between incremental crawl and delta crawl for the SAP HANA connector?</td><td><p>Incremental crawl:</p><ul><li>Retrieves tables that were missed or skipped during an earlier crawl.</li><li>Does not detect changes to columns of tables that were already crawled successfully.</li></ul><p>Delta crawl:</p><ul><li>Uses an SAP HANA history or audit table to identify changes since the previous run.</li><li>Used only in specific Bridge-based setups where the number of tables crosses a certain threshold.</li><li>Selected automatically rather than manually.</li></ul><p>In current and upcoming releases, delta crawl is being replaced by a batch-style approach that retrieves tables in smaller chunks.</p></td></tr><tr><td>4</td><td>How does the copy title to catalog option under business glossary settings behave once a term is associated with a table or column?</td><td><p>The Copy Title to Catalog option is a connector-level setting used for bulk actions.</p><ul><li>It allows titles to be copied across multiple tables and columns at once.</li><li>The connector-level setting acts as the default.</li><li>Once a term is associated with a specific table or column, the term-level configuration takes priority.</li><li>The term-level configuration overrides the connector-level setting.</li></ul></td></tr><tr><td>5</td><td>Why are no tables visible when browsing the selected schema?</td><td><p>If tables are not visible, the most common reason is insufficient privileges or selecting the wrong schema.</p><ul><li>Confirm that the correct schema is selected and that the required permissions are granted to access tables within it.</li><li>Verify the presence of the tables by running a direct query on the database.</li><li>In some cases, tables may exist under different schemas, so review all available schemas and refresh the table list if needed.</li><li>Ensure that the database connection is active.</li><li>SELECT privileges on the relevant schema are required to view tables.</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Profiling" %}

<table data-search="true"><thead><tr><th width="87.68359375">S. No.</th><th width="181.30078125">Question</th><th>Answer</th></tr></thead><tbody><tr><td>1</td><td>Are all columns profiled during a crawl?</td><td><p>No. Some columns and data types are excluded from profiling.</p><ul><li>Columns with a length greater than 4,000 characters are excluded by default.</li><li>Large object storage types and long text types are also not profiled.</li><li>These restrictions help avoid resource-intensive profiling.</li><li>The 4,000-character limit applies across all connector types, not only SAP HANA.</li></ul></td></tr><tr><td>2</td><td>What does the row count constraint control during profiling?</td><td><p>The Row Count Constraint applies only when the profile type is set to Automatic.</p><ul><li>When enabled, the connector compares the table's actual row count against the configured limit.</li><li>If the table exceeds the limit, only a sample of rows based on the configured sample size is profiled.</li><li>When disabled, the entire table is profiled regardless of size.</li><li>Profiling very large tables can affect performance when the constraint is disabled.</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

***

Copyright © 2026, 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.1/connectors/connector-repositories/rdbms/sap-hana.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.