SAP HANA Connector

Overview

Used for OneTrust Data Discovery, the SAP HANA (High-performance Analytic Appliance) connector enables customers to scan and retrieve data stored in memory across the multi-modal database.

Pod Residency: rdbms-scanner
Connection Method: JDBC URL

Supported Scan Actions


Scan Type	Description
Catalog	This scan type will fetch only the metadata in the database like details of table, or column are scanned.
Catalog & Scan	This scan type will scan both metadata and data under the tables and returns the appropriate terms.

Credential and System Permissions

OneTrust recommends to adhere to your organization's security and infrastructure policy and include system engineer resources or other qualified subject matter experts to set up credentials on data sources. For specific instructions for how to enable these credentials, refer to your data source's implementation documentation, knowledge base and/or support resources.

This connector relies on a JDBC URL connection.

JSON

# Sample Vault JSON

{
"connectionUrl": "jdbc:sap://1.1.1.1:39015/?autocommit=false",
"user": "your_user",
"password": "your_password"
}

# Sample Vault JSON

{
"connectionUrl": "jdbc:sap://1.1.1.1:39015/?autocommit=false",
"user": "your_user",
"password": "your_password"
}

Note:

You must create a user in SAP HANA Studio and assign read-only access for all resources you need access to in Data Discovery. That may include the following permission:

SELECT
SELECT CDS METADATA
SELECT METADATA
EXECUTE*

*Required for advanced use cases, such as data subject access request (DSAR) for data deletion, as a non-read action.

Special Views

OneTrust Data Discovery can support the four view types offered with SAP HANA:


View Types	Notes
Analytic Views	Must include this type in the include path for them to be scanned properly while setting the scan type to VIEW.
Attribute Views	Must include this type in the include path for them to be scanned properly while setting the scan type to VIEW.
Calculation Views	Must include this type in the include path for them to be scanned properly while setting the scan type to VIEW.
Standard RDBMS Views	N/A

Scan Profile Support

Note:

For additional details on scan profile configuration and management, see Setting Up Scan Profiles.

Limits

Limit Number of Objects to Scan
Max Number of Schemas per Catalog
Max Number of Tables per Schema
Select Limitation Method for Scanning Rows per Table, choose one:
- First with Limit: populates setting for Maximum Number of Rows per Table
- Random Percentage: populates setting for Percentage Scanned of Total Objects
- Random Percentage with Limit: populates settings for Percentage Scanned of Total Objects and Maximum Limit of Scanned Objects

Wildcard

Wildcards are not supported for column inclusion or exclusion.

Example: *Name* will not work to include/exclude both firstName and lastName columns
Instead, you must specify the exact column names separated by commas (e.g. firstName,lastName).

Important:

Columns Excluded in the Data Dictionary

When a column is excluded, it is still cataloged by the Data Dictionary. This means:

Basic metadata for the column is retrieved.
During extraction, the actual column content is skipped based on the configuration.

Include/Exclude Path Configuration Fields

Schema
Table
Column

Collected Objects & Fields


Objects	Fields
Database Schema Table Column File Key	Name Column index Size estimate Rows estimate Owner Product version Product name Product Family Field type Foreign key name Foreign key columns Primary key name Primary key columns

Denylist

This connector has databases and/or schemas that included in our denylist. For more information, see RDBMS Database and Schema Denylist.

Troubleshooting

RDBMS-Scanner Pods with Multiple Restarts

If the pod logs show an OOM (Out of Memory) error, the possible root cause when scanning SAP HANA, is that certain tables are causing this issue. Without more information about the table contents, it can be difficult to determine the exact cause of the error.

Error Example:

CODE

Caused by: java.lang.OutOfMemoryError: Java heap space

Caused by: java.lang.OutOfMemoryError: Java heap space

Resolution

Limiting the amount of data extracted from SAP HANA can reduce the likelihood of OOM errors. However, this may impact performance. The SAPHANA_FETCH_SIZE value can be adjusted to balance preventing OOM errors and maintaining acceptable performance.

Command to update the fetch size: