Installation guide

4. Accessing Popular Databases
Driver Notes
• The mx.ODBC.DataDirect package is currently only available for Linux
32-bit and 64-bit systems. If you need the package on other platforms,
please write to [e-mail]
for assistance.
• The DataDirect ODBC driver manager is included in the same directory
as the Teradata ODBC driver itself. If you setup LD_LIBRARY_PATH to
the directory where the driver is located, mxODBC will automatically use
the right DataDirect ODBC driver manager, e.g.
export LD_LIBRARY_PATH=\
/opt/teradata/client/14.10/odbc_64/lib:\
/opt/teradata/client/14.10/tdicu/lib64
• The Teradata ODBC driver uses a separate file for loading error messages.
The path for this is set using the
NLSPATH environment variable and
should be set up like this (the directory will have to be adapted to the
location of the
tdodbc.cat file:
export NLSPATH=/opt/teradata/client/14.10/odbc_64/msg/%N.cat
If not set, you will get exceptions like this from the driver:
[Teradata][ODBC Teradata Driver] Unable to get catalog
string
.
• Native Unicode is supported by the driver/manager combination setup
with the
CharacterSet = UTF16 setting in the ~/.odbc.ini section for
Teradata.
• Trying to use the Teradata ODBC driver with unixODBC or iODBC
usually results in an immediate segfault.
• If you use the Teradata ODBC driver in combination with the DataDirect
ODBC manager, be sure to keep the ~/.odbc.ini file short. With longer
~/.odbc.ini files, the combination will segfault.
• The 14.10 version of the driver insists on having a section
[ODBC Data
Sources]
in the ~/.odbc.ini file. Without it, the driver doesn't connect
and fails with the following error message:
[Teradata][ODBC Teradata Driver] No DBCName entries were
found in DSN/connection-string
This does not happen with the 13.10 driver.
• We found that it is apparently not possible to use multi-line SQL
statements with the Teradata ODBC drivers 13.10 and 14.10. The
Teradata SQL parser complains about newline characters in the strings.
Removing these results in syntax errors. This makes it difficult to e.g.
define stored procedures from a Python application. The problem appears
to be a driver limitation which may be fixed in future Teradata driver
versions.
• The Teradata driver only supports relative forward scrolling in the result
set. Backwards scrolling is not supported.
57