Three UNIX scripts are deployed in the odbc_32 and odbc_64 bin directories. These scripts provide the power to emulate the legacy directory tree structure and customize their odbc.ini and odbcinst.ini files when a release prior to ODBC 14.00 was installed into a directory that is different than the prompted default directory.
These scripts are:
See Appendix A: “ODBC Legacy Migration” for information about migration, including examples of common migration scenarios.
Directory Tree Structure
The directory tree structure consists of:
Below is an example of the tree structure in relation to the fixed Teradata Tools and Utilities directory.
This tree structure places all Teradata Tools and Utilities products for each release in a version number sub-directory, which is listed as <version> in Table 5.
<user defined> |
<Teradata Tools and Utilities directory> |
<Teradata Tools and Utilities product sub-directory> |
/opt |
teradata/client/<version> |
odbc_32/ |
|
|
odbc_64/ |
Legacy ODBC Directory Tree Structure
Table 6 on page 26 describes the legacy ODBC directory tree structure for ODBC releases prior to ODBC 13.0.
<user selection> |
/ <PRE 13.0 ODBC product sub-directory> |
<Teradata Tools and Utilities product sub-directory> |
usr/odbc |
/ |
drivers include lib locale samples |