Prerequisites #Prerequisites | Qlik Replicate Help
Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

Prerequisites

Last updated: 10/8/2026

The following section describes the prerequisites for working with Qlik Replicate and a Teradata Database Source.

Replicate Server for Windows

Install Teradata Database ODBC Driver 17.20 or 20.00 for Windows.

Download the driver from https://downloads.teradata.com/download/connectivity/odbc-driver/windows

Replicate Server for Linux

Qlik Replicate can access Teradata Database through either of the following ODBC driver managers:

  • unixODBC (recommended), which is bundled with Replicate and is the default.
  • DataDirect, which is provided with Teradata Database Client.
Information note

The driver manager applies to the whole Replicate Server. All endpoints in all tasks use the same driver manager.

unixODBC allows Teradata Database to be used in the same task as other unixODBC-based endpoints, such as Microsoft SQL Server, PostgreSQL, and MySQL. DataDirect cannot be combined with endpoints that use unixODBC. Use the Replicate File Channel for those combinations. Oracle, Hadoop, File, and Replicate Connect endpoints are not affected by this restriction.

  1. Stop the Replicate service and optionally confirm that it has stopped as described in Replicate server procedures.

  2. Download the driver from https://downloads.teradata.com/download/connectivity/odbc-driver/linux.

  3. Install Teradata Database Client 20.00 for Linux under /opt/teradata/client/20.00.

  4. Complete Option A or Option B below. Put all export commands in /opt/attunity/replicate/bin/site_arep_login.sh.

  5. Start the Replicate service and optionally confirm that it has started as described in Replicate server procedures.

Option A: unixODBC driver manager (recommended)

  1. Verify that AREP_ODBC_DRIVER_MANAGER is not set.

  2. Register the Teradata driver in /etc/odbcinst.ini.

  3. Copy the section name from /opt/teradata/client/20.00/odbc_64/odbcinst.ini: [Teradata Database ODBC Driver 20.00] Driver=/opt/teradata/client/20.00/odbc_64/lib/tdataodbc_sb64.so

  4. Add the following commands to site_arep_login.sh in that order:

    export LD_LIBRARY_PATH=/opt/attunity/replicate/lib:/opt/teradata/client/20.00/lib64:/opt/teradata/client/20.00/odbc_64/lib:$LD_LIBRARY_PATH

    export ODBCINI=/opt/teradata/client/20.00/odbc_64/odbc.ini

  5. Delete any libodbc.so or libodbcinst.so symbolic links to the Teradata libraries in /usr/lib64 or /lib64.

Option B: DataDirect driver manager

  1. Add the following commands to site_arep_login.sh in that order:

    export LD_LIBRARY_PATH=/opt/teradata/client/20.00/odbc_64/lib:/opt/teradata/client/20.00/lib64:/opt/attunity/replicate/lib:$LD_LIBRARY_PATH

    export ODBCINI=/opt/teradata/client/20.00/odbc_64/odbc.ini

    export ODBCINST=/opt/teradata/client/20.00/odbc_64/odbcinst.ini

    export AREP_ODBC_DRIVER_MANAGER=/opt/teradata/client/20.00/odbc_64/lib/libodbc.so

  2. Verify that /opt/teradata/client/20.00/odbc_64/odbcinst.ini contains the Teradata driver definition.

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 – please let us know!

Leave your feedback here