SAP HANA

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

Overview

Connector Details

Connector Category	RDBMS
Connector Version	Release7.x
Releases Supported (Available from)	Legacy Connector
Connectivity [How the connection is established with SAP HANA]	JDBC
Verified SAP HANA Version	2

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.

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 the SAP HANA and mapped to the corresponding UI assets.

SAP HANA Object	SAP HANA Attribute	OvalEdge Attribute	OvalEdge Category	OvalEdge Type
Schema	Schema Name	Schema	Databases	Schema
Schema	Schema Comment	Source Description	Databases	Schema
Table	Tablename	Table	Tables	Table
Table	Table_Type	Type	Tables	Table
Table	Tablecomment/dd.DDTEXT	Source Description	Descriptions	Source Description
Columns	Column_Name	Column	Table Columns	Columnname
Columns	Data_Type	Column Type	Table Columns	Oecolumntype
Columns	Comments	Source Description	Table Columns	Columndescription
Columns	Data_Length	Data Type Size	Table Columns	Columnlength
Columns	Ordinal Position	Column Position	Table Columns	Columnposition
View	View Name	View	Tables	View
View	Text	View Query	Views	View
Procedures	Name	Name	Procedures	-
Functions	Name	Name	Functions	-
Functions	Text	Function Query	Functions	-
Indexes	Index name	Index	Indexes	Index
Indexes	If Unique	Yes /No	Indexes	Index

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.

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.

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 SAP HANA administrator grants these permissions, as standard accounts may not have the required access to assign them independently.

Objects	System Tables	Access Permissions
Validate Connection	Sys.M_Database	Select
Schema	Schemas	Select
Tables	Tables	Select
Tables	DD02T	Select
Table Columns	Table_Columns	Select
Table Columns	View_Columns	Select
Table Columns	DD03M	Select
Views	Public.Views	Select
Calculation Views	_Sys_Repo.Active_Object	Select
Procedures	Public.Procedures	Select
Functions	Public.Functions	Select
Indexes	Index_Columns	Select

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 SAP HANA, and complete the required parameters.

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

Field Name	Description
Connector Type	By default, "SAP HANA" 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 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 SAP HANA connection (Example: "SAPHANA_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 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
Port*	SAP HANA uses port 30015 by default. The port number can be modified as needed.
Database*	Enter the name of the target SAP HANA database to establish the connection.
Driver*	By default, SAP HANA uses ‘com.sap.db.jdbc.Driver.’ This field is not editable.
Username*	Enter the SAP HANA database account name configured for authentication.
Password*	Enter the SAP HANA database user’s password associated with the provided username.
Connection String	Configure the connection string for the SAP HANA 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 SAP HANA host or IP address. Authentication Plugins: jdbc:sap://{server}:30015/?autocommit=false This is the default authentication string used for connecting to SAP HANA.
Enter schema for DD tables	Enter the schema name where the Data Dictionary (DD) tables are stored in the SAP HANA system.
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.

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

  • 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 due to incorrect or missing authentication details. Resolution: Verify the username and password, ensure the correct authentication method is used, and retry after confirming the credentials are valid.
2	Please provide a valid database name	Error Description: The system displays this message when the database name field is empty or contains an invalid value that does not match the required format. Resolution: Enter a correctly formatted, valid database name that matches the expected naming conventions and exists in the target system.
3	Username or password is wrong	Error Description: The authentication attempt failed because the provided username or password does not match the stored credentials. Resolution: Verify that the correct username and password are entered and update or reset the credentials if necessary.
4	Error when trying to see the columns in a table	Error Description: The system fails to load or display the column metadata for a selected table due to missing permissions, connectivity issues, or incomplete metadata retrieval. Resolution: Verify database permissions, ensure the connection is active and stable, and refresh or reindex the metadata so the system can retrieve and display the table columns correctly.
5	can't find any schemas	Error Description: The system cannot retrieve schema metadata from the connected database, resulting in an empty or missing schema list. Resolution: Verify database permissions, ensure the user has access to schema metadata, and re-test the connection after confirming the database is reachable.

FAQs

Why is the system unable to establish a connection to the SAP HANA database?

When the application cannot connect to the SAP HANA server, verify that the server name, address, and port (typically 30015) are correct, and confirm that the SAP HANA service is up and reachable. Make sure there are no firewall or network restrictions blocking access. Test the network connection, and if needed, try connecting from SAP HANA Studio on the same machine. If the problem continues, contact the network or SAP administrator.

Why are no schemas visible when attempting to browse the database?

If schemas are not visible, the issue is caused by insufficient access privileges. The system displays only schemas where HAS_PRIVILEGES = 'TRUE'. Confirm that the connection is established to the correct database and verify the schema's existence by running a direct query. Ensure that the user account has the required schema-level permissions and refresh the schema list if needed. Specific system schemas may also be hidden based on administrative settings.

Why are no tables visible when browsing the selected schema?

If tables are not visible, the most common reason is insufficient privileges or selecting the wrong schema. Confirm that the correct schema is selected and that the required permissions are granted to access tables within it. Verify the presence of the tables by running a direct query on the database. In some cases, tables may exist under different schemas, so review all available schemas and refresh the table list if needed. Also, ensure that the database connection is active. SELECT privileges on the relevant schema are required to view tables.

---

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