Teradata ODBC Driver 12.0.0.1 for MP-RAS
2 files included in this download
Description
Download the Teradata ODBC Driver for MP-RAS. This release supports Teradata 12.0 features in both Teradata and (Entry Level) ANSI modes, and is backwards compatible with previous releases back to Teradata Database V2R6.0.
README
Teradata ODBC Driver
for
MPRAS
Product: ODBC Driver For Teradata
Version: 12.00.00.01
Product Dependencies:
1. Teradata GSS client package (TeraGSS)
2. Shared common components for Internationalization for Teradata (tdicu)
Contents
1.0 Introduction
2.0 Release Content
3.0 Requirements
4.0 ODBC Software Installation/Uninstallation
5.0 Configuration
6.0 Sample ODBC Applications
7.0 Restrictions
8.0 Limitations/Issues
9.0 Documentation
10.0 Support
Appendix A Description of New Features
A.0 DSN retryOnEINTR option
1.0 Introduction
This release of the ODBC driver for Teradata will support Teradata 12.0
features in both Teradata and (Entry Level) ANSI modes, and is backwards
compatible with previous releases of Teradata as noted in section 3.2
2.0 Release Content
2.1 New Features included in this release
a) New Features included in TTU 12.0 GCA release (see ODBC User Guide for description)
DR 98321 -- RFC: Support the retrieval of auto-generated keys from an insert statement
DR 98318 -- RFC: Support V2R6.2 StatementInfo Parcel
DR 105850 -- RFC: Table function dynamic results
DR 105851 -- RFC: Provide support for Stored Procedure Dynamic Result Sets
DR 105853 -- RFC: Provide support for UNICODE Data Dictionary
DR 105854 -- RFC: Multi-level partitioned primary index
DR 105848 -- RFC: Add support for Mini Batch: INSERT-SELECT and MERGE-INTO error logging syntax
DR 107617 -- RFC: Add new keywords in V2R7.0 to list returned by SQLGetInfo with SQL_KEYWORDS
2.2 Driver Manager 5.1 Problems fixed in this release
DR 100879 -- 3P : DD 5.1 DM core dumps while MDS runs on a Japanese locale machine
DR 106403 -- 3P : Token returned by SQLParamData is incorrect for UTF-16 applications on UNIX
DR 110922 -- RFC: coredumps when SQLDescribeParam(hstmt,1,NULL,NULL,NULL) is called after SQLPrepare on 64-bit sparc & aix.
DR 111252 -- 3P : DD Driver Manager causes segmentation faut on SQLGetDiagField() with invalid RecNumber/DiagIdentifier
DR 112969 -- 3P : ODBC Client 3.05 compilation problem on HP-UX 11.11, HP-UX 11.23.
2.3 ODBC Driver Problems fixed in this release
12.0.0.1 DRs
============
DR 91374 -- ODBC parsing fails for "LOCKING ROW FOR ACCESS" qualifier queries
DR 99825 -- LDAP Authentication: ODBC,OLEDB Client connectivity issue
DR 100743 -- Include changes from aix-power in the aix-power.32 installation scripts
DR 100879 -- 3P : DD 5.1 DM core dumps while MDS runs on a Japanese locale machine
DR 111252 -- 3P : DD Driver Manager causes segmentation faut on SQLGetDiagField() with invalid RecNumber/DiagIdentifier
DR 112969 -- 3P : ODBC Client 3.05 compilation problem on HP-UX 11.11, HP-UX 11.23.
DR 114149 -- No column headers are returned if ANSI style comments '--' is present before the SQL statement
DR 114167 -- Inconsistent behavior of "Disable Prepare for SQLs in parenthesis or preceded by comments" DSN option
DR 114957 -- Avoiding corruption when V2R6.2 BIGINTs are used with TTU8.1 ODBC
DR 115183 -- The owner and group attributes on tdodbc files were set to 713 and 30000 respectively from TTU 8.1, TTU 8,2, TTU 12.0
DR 115337 -- Accept self-defining extensions to PCLGTWCONFIG parcel in any order
DR 115404 -- ODBC 3.6: SQLExecute with param size greater than 1 fails with 2683 error if last value in array of parameters is NULL
DR 115775 -- ODBC on Unix MPRAS throws 3706 if query has current_timestamp ( format 'DD-MMM-YY bhh:miBT' )
DR 115862 -- SQLPrepare() perfomance problem. Printer Friendly View
DR 115976 -- TDODBC 12.0: SQLExecute failing with Wrong number of parameters error after any INSERT fails with database error
DR 115983 -- Silent Installation of ODBC on AIX machines
DR 116700 -- ODBC SQLSpecialColumns() API will use new DBS view to obtain catalog metadata
* This release also includes all the DR/RFCs committed up to
Release 12.00.00.01
3.0 Requirements
3.1 System
NCR UNIX MP-RAS 3.2
NCR UNIX MP-RAS 3.3
3.2 Supported Teradata Database versions
Teradata Database V2R6.0
Teradata Database V2R6.1
Teradata Database V2R6.2
Teradata Database 12.0
3.3 ODBC Dependencies
1. Teradata GSS client package (TeraGSS)
2. Shared common components for Internationalization for Teradata (tdicu)
3.4 ODBC Application development
When developing an ODBC C++ application, the developer must use the
recommended compiler MPRAS 3.2 GCA release, with the SCDE package or
later (scde package)
4.0 ODBC Software Installation/Uninstallation
4.1 ODBC Dependencies
There are two products that must be installed onto the system before the
ODBC Driver can function properly. They are
1. Teradata GSS client package (TeraGSS)
2. Shared common components for Internationalization for Teradata (tdicu)
It is best for these two product to be installed before the "ODBC Driver
for Teradata" is installed.
4.2 Installation
The following command is used to install the "ODBC Driver for Teradata".
pkgadd -d <device> tdodbc
where <device> is typically the directory path of the tdodbc package.
4.3 Uninstallation
The following command is used to uninstall the "ODBC Driver for Teradata".
pkgrm tdodbc
4.4 Upgrades
4.5 List Software Product
The following command is used to display information about the
"ODBC Driver for Teradata" installed.
pkgadd tdodbc
pkgadd -l tdodbc
5.0 Configuration
5.1 ODBC and ODBCINST INI Configuration
A template odbc.ini and odbcinst.ini file is available in the ODBC
installation directory.
5.1.1 odbc.ini
The odbc.ini file must be copied to each user's home directory and
renamed .odbc.ini (hidden file). The user must customize this file
to reflect appropriate data source configuration information.
By default, the .odbc.ini file is expected to be in the user's
home directory but the ODBCINI environment variable may be used
to specify the pathname of the .odbc.ini file. A sample of this file
containing Teradata DSN entries can be copied from <install dir>/odbc.ini.
This template file does not have the leading period, so when copying this
file to a user's home directory a leading period must be added.
5.1.2 odbcinst.ini
The odbcinst.ini is read by the Driver Manager to determine which drivers
are currently installed, and their ODBC SDK compliance. There is just
one odbcinst.ini file on a system and it resides in the ODBC installation
directory.
Note: A common error seen when running an ODBC application is the
inability to load the ODBC driver. The cause is usually that of
the .ini file not defining the exact location of the driver. So,
it is *key* that these .ini files contains the exact location of
the ODBC driver(s) to be used. The odbc.ini and odbcinst.ini will
be automatically edited to reflect the location of the Teradata
ODBC driver upon package installation.
LD_LIBRARY_PATH environment variable is mandatory.
5.2 DSN Configuration
6.0 Sample ODBC Applications
6.1 adhoc C/C++ program
This is a sample program which demonstrates how to
- Connect to a Data Source
- Execute a SQL statement
- Retrieve the result set created from the SQL statement
This sample program is written in both C and C++ language and is
located under the <install dir>/samples directory
7.0 Restrictions
7.1 ODBC restrictions
7.2 Binary Compatibilites
8.0 Limitations/Issues
9.0 Documentation
1) ODBC Driver for Teradata User Guide
(Release 12.00.00 B035-2509-067A July 2007)
2) www.info.ncr.com
10.0 Support
10.1 Contact Information
Problems with the ODBC Driver should be reported to Teradata Customer Services.
To report a problem, customers from the United States should call the Teradata
Americas Care Center (TACC) at 1-800-531-2222, and specify their PIN.
International customers should contact their country-level Remote Services
Center (RSC).
Discussion
You must sign in to leave a comment.