ODBC Integrated Directories - ODBC Driver for Teradata

ODBC Driver for Teradata® User Guide

Product
ODBC Driver for Teradata
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-08-22
dita:mapPath
xbl1544831938754.ditamap
dita:ditavalPath
nkw1500504256726.ditaval
dita:id
B035-2526
lifecycle
previous
Product Category
Teradata Tools and Utilities

ODBC contains release-independent directories which are denoted by ODBC_32 and ODBC_64.

Their sub-directories are symbolic links to the respective 32-bit and 64-bit Teradata Tools and Utilities release directories installed during the installation of the current ODBC.

ODBC_32 and ODBC_64 contain their respective odbc.ini and odbcinst.ini files which are free of any use of a Teradata Tools and Utilities release path. It is required that these templates be used when setting up the odbc.ini with the desired DSN settings. Otherwise, the user will be continuously updating the .ini files when different Teradata Tools and Utilities releases are installed. In particular, the path values in the odbc.ini template for InstallDir and Driver must be the ones defined in the template; they cannot be modified.

Whenever a new Teradata Tools and Utilities release is installed, the sub-directories are updated with the new symbolic links. This release will be the Active TTU of the system. See MultiVersion Support for more information.

The following table shows the release-independent directories.

On UNIX or Linux systems, the Teradata Tools and Utilities installation includes an option to uninstall previous versions of existing Teradata Tools and Utilities software. Any Teradata Tools and Utilities release version prior to 15.10.01 must be uninstalled before installing ODBC Driver for Teradata. This does not apply to efixes, because efixes are installed as an upgrade.

For information about installing operating system-specific utilities, see the documentation listed on https://docs.teradata.com/. Depending on the Teradata Tools and Utilities version installed, the actual value represented by <TTU version> might display as the version number.

/opt teradata/client/ ODBC_32/

include -> /opt/teradata/client/<TTU version>/include\

lib -> /opt/teradata/client/<TTU version>/lib\

locale -> /opt/teradata/client/<TTU version>/odbc_32/locale\

odbc.ini

odbcinst.ini

/opt teradata/client/ ODBC_64/

include -> /opt/teradata/client/<TTU version>/include

lib -> /opt/teradata/client/<TTU version>/lib64

locale -> /opt/teradata/client/<TTU version>/odbc_64/locale\

odbc.ini

odbcinst.ini