Requirements for Teradata

From HVR
Jump to: navigation, search

This section describes the requirements, access privileges, and other features of HVR when using Teradata for replication. For information about the capabilities supported by HVR on Teradata, see Capabilities for Teradata.

For information about compatibility and supported versions of Teradata with HVR platforms, see Platform Compatibility Matrix.

Teradata
Capture Hub Integrate
Icon-No.png Icon-Yes.png Icon-Yes.png

ODBC Connection

HVR uses ODBC connection to the Teradata server for which it requires the Teradata ODBC driver installed (on the machine from which it connects to the Teradata server). HVR only supports Teradata ODBC driver version 15.00 or 16.10. HVR also requires Teradata Parallel Transporter(TPT) packages to use HVR Refresh in bulk mode.

Teradata ODBC driver and TPT packages can be installed using Teradata Tools and Utilities (TTU) package. TTU 16.10 is available for Linux and Windows on Teradata download page, and TTU 15.00 is available for download from Teradata Support Portal (requires user authentication).

The following action definitions are required for TTU to find the correct message files:

Group Table Action
Teradata * Environment /Name=NLSPATH
Teradata * Environment /Value="/opt/teradata/client/<teradata_version>/odbc_64/msg/%N:/opt/teradata/client/<teradata_version>/tbuild/msg/%"

Location Connection

This section lists and describes the connection details required for creating Teradata location in HVR.

SC-Hvr-Location Teradata.png
Field Description
Database Connection
Node The hostname or ip-address of the machine on which the Teradata server is running.
  Example: td1400
User The username to connect HVR to the Teradata Node.
  Example: hvruser
Password The password of the User to connect HVR to the Teradata Node.
Linux / Unix
Driver Manager Library The directory path where the Unix ODBC Driver Manager Library is installed.
  Example: /opt/teradata/client/16.10/odbc_64/lib
ODBCINST The directory path where the odbcinst.ini file is located.
  Example: /opt/teradata/client/16.10/odbc_64/odbcinst.ini
Teradata TPT Library Path The directory path where the Teradata TPT Library is installed.
  Example: /opt/teradata/client/16.10/odbc_64/lib
ODBC Driver The user defined (installed) ODBC driver to connect HVR to the Teradata server.


Hub

Following is the Linux command line sytanx to start HVR scheduler on a Hub with Teradata:

$ hvrscheduler -EODBCINST=<ODBCINST directory path> -EHVR_TPT_LIB_PATH=<Teradata TPT Library Path> -EHVR_ODBC_DM_LIB=<Driver Manager Library> -h teradata '<Node>~<User>/<Password>'

For example,

$ hvrscheduler -EODBCINST=/opt/teradata/client/16.10/odbc_64/odbcinst.ini -EHVR_TPT_LIB_PATH=/opt/teradata/client/16.10/odbc_64/lib -EHVR_ODBC_DM_LIB=/opt/teradata/client/16.10/odbc_64/lib -h teradata 'td1400~hvruser/hvruser'

Grants for HVR on Target Database

By default, the HVR user has all required permissions to integrate changes into default user database.

The grants select table, insert table, update table and delete table are required if the HVR user want to replicate into tables which are not owned by the HVR user (using action TableProperties /Schema).

The grants create table and drop any table are required to create target tables using Hvrrefresh.

The grant select table is required if Hvrcompare or Hvrrefresh needs to read from tables which are owned by other schemas (using action TableProperties /Schema)

The grant create macro is required.