Skip to main content Skip to complementary content

Prerequisites

Before you can land or replicate data, make sure to complete the following prerequisites:

  • Install the required driver on the Data Movement gateway server

  • Grant the required permissions on the data source

  • Configure the data source connector

Driver setup

Download SAP HANA ODBC 64-bit Driver 2.0.19-2.12 from the SAP Software Download Center. You must have an account with SAP to download the software.

Information note

SAP HANA ODBC driver 2.13 and later are not supported.

Example driver name: HDBODBC

Then on the Data Movement gateway machine, open a shell prompt and do the following:

  1. Stop the Data Movement gateway service:

    sudo systemctl stop repagent

  2. Optionally, confirm that the service has stopped:

    sudo systemctl status repagent

    The status should be as follows:

    Active: inactive (dead) since <timestamp> ago

  3. Install the driver on the Data Movement gateway machine.

  4. Add the following section to the odbcinst.ini file located in directory /etc:

    [HDBODBC]

    Description=64-bit HANA ODBC Driver

    Driver=/opt/sap/hdbclient/libodbcHDB.so

    fileUsage=1

  5. Start the Data Movement gateway service:

    sudo systemctl start repagent

  6. Optionally confirm that the service has started:

    sudo systemctl status repagent

    The status should be as follows:

    Active: active (running) since <timestamp> ago

Connecting using SSL

To connect to SAP HANA using SSL, the client must be configured to authenticate the SSL server certificate.

Port

On the Data Movement gateway machine, open inbound port number 3xx15 to the SAP HANA server where xx is the instance number of the SAP HANA database that contains the source tables.

For example, the port for instance 90 would be 39015.

Capturing data changes

When landing data using the SAP Hana (Database) connector, the following artifacts are automatically created in the source database:

  • Three triggers for each of the source tables being landed: The triggers capture changes to the source tables (INSERTs, UPDATEs, and DELETEs) and write them to the attrep_cdc_changes_cts table (described below). A separate trigger is created for each DML operation. The triggers are created in the source table schema.
  • attrep_cdc_changes_cts: This table contains changes captured by the triggers. The table will be created in the schema specified in the Create CDC table in schema field of the SAP HANA (Database) connector.
Information noteWhile there is no setup required from a user's perspective, the triggers are a prerequisite for capturing changes, which is why they are described in this topic.

See also: Permissions

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!