During installation on 64-bit systems, ODBC directories are created for 32-bit, 64-bit, and their respective release-independent directories. On 32-bit systems, only 32-bit directories are created. The 32-bit and 64-bit directories are placed under the Teradata Tools and Utilities release directory. Release independent directories are created at the same directory level as the Teradata Tools and Utilities release directories. Release independent directories provide a way to set up the odbc.ini and odbcinst.ini files without having to change them when future Teradata Tools and Utilities releases are installed.
Subdirectories for the 32-bit and 64-bit directories are listed in Table 8.
|
Directory |
Contents |
|
bin |
Home for executables and scripts used to manage and support the ODBC Driver for Teradata |
|
include |
Driver Manager and ODBC Driver for Teradata include files |
|
lib |
Driver Manager and ODBC Driver for Teradata libraries |
|
locale |
Driver Manager message file |
|
msg |
Message catalog file |
|
samples |
C and C++ sample application |
The release independent directories are given the upper case names ODBC_32 and ODBC_64. Their sub-directories are symbolic links to their respective 32-bit and 64-bit Teradata Tools and Utilities release directories. ODBC_32 and ODBC_64 installations 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.When a new Teradata Tools and Utilities release is installed, the sub-directories are updated with new symbolic links.