Teradata ODBC Driver 13.0 for Windows 32-bit
2 files included in this download
Description
Download the Teradata ODBC Driver 13.0 for Windows. Teradata ODBC Driver 13.0 supports Teradata 13.0 features in both Teradata and (Entry Level) ANSI modes, and is backwards compatible with previous releases of Teradata back to V2R6.0.
README
Teradata ODBC Driver
for
Windows
Product: ODBC Driver For Teradata
Version: 13.0.0.0
Product Dependencies:
1. Teradata GSS client package (TeraGSS)
2. Shared common components for Internationalization for Teradata (tdicu)
3. Microsoft Data Access Components (MDAC)
Contents
1.0 Introduction
1.0.1 Customer Impact list
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 - New ODBC 13.0 directory tree structure
Appendix B - DSN Migration
1.0 Introduction
This release of the ODBC driver for Teradata will support Teradata 13.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
The 64-bit ODBC Driver for Windows has been built using the Visual Studio 2005
VC++ Ver. 8.0 for the EM64T platform, and Visual Studio 2003 VC++ Ver. 7.1
for the other Windows ODBC Drivers.
The ODBC 13.0 release has introduced a new ODBC directory tree structure where
the ODBC Driver libraries are no longer placed in the system32 directory. The
new ODBC tree structure can be seen in Appendix B. The ODBC 13.0 installation
package has taken steps to make this new tree structure transparent to the
existing DSNs that have been created by updating the Driver Attribute in the
DSN to the new location of the tdata.dll library.
1.0.1 Customer Impact List
DR 122470 tracks a problem that has been reported to Microsoft and there are
certain steps to take to work around this problem.
DR 122470 -- 3P: W2003 client machine must be rebooted for upgrades to work; Microsoft incident SRZ080531000020
PROBLEM/ISSUE
============
Environment Variable PATH does not get updated after installing a Custom application on
Windows Server 2003
Workaround
==========
1) mstsc - open session in console mode
When installing Teradata Tools and Utilities software on a Windows Server 2003 system
using a terminal session opened with "mstsc", open the session in console
mode: "mstsc /console". Otherwise, the Windows Server 2003 system will have to be
rebooted after installing the software.
2) logoff followed by logging on
3) Enter the Environment variables dialog box and touch one of the variables and select OK.
2.0 Release Content
2.1 New Features included in this release
a) New Features included in TTU 13.0 GCA release (see ODBC User Guide for description)
DR 115120 -- Deploy a 32-bit ODBC Driver built with Visual Studio 8.0 for Windows platforms
DR 115298 -- RFC: Support Period Data Types
DR 115600 -- RFC: Support DDL Replication
DR 115599 -- Support Scalar Subqueries
DR 115601 -- Support RESET WHEN for Windows functions
DR 115604 -- Support old TTU with new database
DR 115607 -- Add new keywords in Teradata 13.0 to list returned by SQLGetInfo with SQL_KEYWORDS
DR 115761 -- RFC: Refactor ODBC Driver data conversion code
2.2 Driver Manager Problems fixed in this release
2.3 ODBC Driver Problems fixed in this release
DR 54946 -- ODBC driver options list box too small
DR 67684 -- Solaris: Request for -compat=5, iostream library support of our ODBC Driver
DR 91374 -- ODBC parsing fails for "LOCKING ROW FOR ACCESS" qualifier queries
DR 96311 -- ODBCTRACE to have Timestamp
DR 99825 -- LDAP Authentication: ODBC,OLEDB Client connectivity issue
DR 100701 -- Allow 32-bit and 64-bit ODBC drivers to coexist on the same system
DR 110312 -- ODBC do not install terasso.dll in windows/system32
DR 111221 -- Convert existing ODBC Help files (.hlp) to an alternative Help file format, such as .chm, .html, or .xml
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 114662 -- Prevent driver reading environment variable for user-id with recent authentication methods
DR 114957 -- Avoiding corruption when V2R6.2 BIGINTs are used with TTU8.1 ODBC
DR 115120 -- Deploy a 32-bit ODBC Driver built with Visual Studio 8.0 for Windows platforms
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 115298 -- Support Period Data Types
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 115599 -- Support Scalar Subqueries
DR 115600 -- Support DDL Replication
DR 115601 -- Support RESET WHEN for Windows functions
DR 115604 -- Support old TTU with new database
DR 115607 -- Add new keywords in Teradata 13.0 to list returned by SQLGetInfo with SQL_KEYWORDS
DR 115761 -- Refactor ODBC driver data conversion code
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 116045 -- ConfigDSNW does not handle lpszAttributes argument correctly
DR 116050 -- Remove Support phone numbers from displays and readme files
DR 116700 -- ODBC SQLSpecialColumns() API will use new DBS view to obtain catalog metadata
DR 117394 -- Convert the windows install package for the tdodbc product into a Basic MSI package
DR 117527 -- ODBC to uninstall previous version on Windows when installing new version
DR 119316 -- ODBC : Memory not being released after application disconnects from database
DR 120373 -- STVTEST: ODBC driver fails to parse a DDL Replication query on windows
DR 120407 -- segmentation violation in linux ODBC driver.
DR 120453 -- Parser crashes on preparing certain SQL queries containing parameters and double parenthesis
DR 120716 -- Driver returns {error} STATE=HY000, CODE=0, MSG=[Teradata][ODBC Teradata Driver] Major Status=0 on unix-LDAP connect
DR 120984 -- STVTEST:Period Time & Timestamp data retrieved to SQL_C_WCHAR using charset UTF16 is incomplete
DR 121324 -- Conversion from SQL Char to SQL_C_UBIGINT returns 9223372036854775807 for values > 9223372036854775807
DR 121655 -- STV:Problem when converting from SQL_C_BINARY -> All PDTs for SQL_NULL_DATA
DR 121658 -- Change in syntax: RESET-WHEN specification must be before ROW specification
DR 121774 -- LDAP fails to connect when specifying Kanji active directory in username field
DR 121806 -- STV:Fetch/GetData observed with success instead of error when the BindCol bufferlength is less than the actual length
DR 122401 -- STV: Incorrect data or crash observed with TSET using ODBC13d
DR 122439 -- SQLConfigDataSource corrupts existing DSN when request type is ODBC_CONFIG_DSN or ODBC_CONFIG_SYS_DSN
DR 122787 -- Add support for the AppCodePage DSN/Connection key value to the ODBC driver.
DR 122826 -- ODBC access violation when fetching row with 2 CLOB columns having NULLs
DR 123494 -- Use strtol() instead of strtoimax() for strtoll() on HPUX PA64
DR 123532 -- Misspelling in connection string - AUTHENTICATONPARAMETER (a missing "I")
* This release also includes all the DR/RFCs committed up to
Release 12.0.0.1
3.0 Requirements
3.1 System
Microsoft Windows 2000 original and up to SP4
Microsoft Windows 2003 original and up to SP1 (32-bit and 64-bit)
Microsoft Windows XP original and up to SP2 (32-bit and 64-bit)
Microsoft Windows Vista Enterprise (32-bit and 64-bit)
3.2 Supported Teradata Database versions
Teradata Database V2R6.0
Teradata Database V2R6.1
Teradata Database V2R6.2
Teradata Database 12.0
Teradata Database 13.0
3.3 ODBC Dependencies
1. Teradata GSS client package (TeraGSS)
2. Shared common components for Internationalization for Teradata (tdicu)
3. Microsoft Data Access Components (MDAC)
(MDAC bundled with the Windows XP, 2003, Vista O/S)
3.4 ODBC Application development
When developing an ODBC C++ application, the developer is encouraged to
use the recommended compiler Visual Studio 2005 VC++ Ver. 8.0.
The ODBC 13.0 release has deploy tdsql.h which contains definitions to
Teradata specific attributes for the ODBC connection, statement and
descriptor objects. These are extensions to the ODBC standard. The
tdsql.h file can be found in the install directory of the
ODBC Driver for Teradata. For example,
C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata
3.5 Microsoft Data Access Components (MDAC)
MDAC 2.5 RTM or later
The Microsoft Data Access Components (MDAC) is bundled with
64-Bit Windows systems
MicrosoftR WindowsR XP SP2 (32-bit)
MicrosoftR WindowsR 2003 SP1 (32-bit)
MicrosoftR WindowsR Vista (32-bit)
and will not be included the "ODBC Driver for Teradata" installation
package.
4.0 ODBC Software Installation/Uninstallation
The ODBC 13. 0 release now supports both the 32-bit and 64-bit ODBC Drivers
on a single Windows system. Each ODBC Driver has its own installation package
so two installations would be required to get both Drivers onto the system.
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 products to be installed before the
"ODBC Driver for Teradata" is installed.
4.2 Installation
Before installing the ODBC "Driver for Teradata", it is recommended that
all applications are closed, including Microsoft Office, and to disable
any virus protection software running on the system. If any of the
required system DLLs are used by a running applications, the installation
of the Teradata ODBC Driver may fail.
The ODBC install package is available on the TTU GCA CD-ROM or as a
self-extracting file that can be downloaded from the Patch Server or the
Teradata Down Load Center when an EFIX is required.
There are two type of installation formats. The one found on the TTU GCA
CD-ROM is a installation directory containing all the InstallShield files
with a setup.exe program to be execute. The format that is downloaded is
a single self-extracting file when executed will begin to extract the
file's contents to a predefined location followed by the automatic
execution of the setup.exe program. An example of the self-extracting
file name is TDODBC.13.00.00.00.EXE.
Note: If the installation shows any errors, open the Setup.log file that
is created in the directory to find out what the errors are. The
User Guide will provide you more information about the instructions,
possible errors and their descriptions and solutions.
4.2.1 TTU CD-ROM
When installing from the TTU CD-ROM, the user will be guided
through the installation for the "ODBC Driver for Teradata". Just
follow the guidelines on the screen and it will automatically
determine the type of system hardware (32-Bit or 64-Bit) and install
the approriate version of the driver.
4.2.2 Install (Setup of ODBC Driver for Teradata)
Dialog Windows
==============
- Welcome to the InstallShield Wizard for ODBC Driver for Teradata
- License Agreement
- Choose Destination Location
Default: "C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata"
- Start Copying Files
- InstallShield Wizard Complete
Yes, I want to view the ReadMe file
Yes, I want to run the ODBC Administrator now (* omitted on 64 bit systems)
* On 64-Bit Windows systems the user can launch the ODBC
Administrator program from
Start->All Programs->ODBC Administrator
or from the Administrative Tools menu.
4.2.3 Custom Install (Setup of ODBC Driver for Teradata)
4.2.4 Silent Install
4.2.4.1 Customizing an InstallShield Response file
N/A
4.2.4.2 Invoking a Silent Install
From a DOS window, the user will change directories to where the
"ODBC Driver for Teradata.msi" is located and use any of the below
command to silently install the ODBC Driver for Teradata Package.
msiexec /i "ODBC Driver for Teradata.msi" /qn
(Default: "C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata")
An example of the command line is below where INSTALLDIR is the
user specificed destination.
msiexec /i "ODBC Driver for Teradata.msi" /qn INSTALLDIR=C:\test
4.3 Uninstallation
To uninstall the "ODBC Driver for Teradata" the user needs to use the
Add/Remove Programs panel
Start->Settings->Control Panel->Add/Remove Programs
and
select the "ODBC Driver for Teradata package"
for removal.
4.4 Upgrades
4.5 List Software Product
The following steps are used to display information about the
"ODBC Driver for Teradata" installed. The user needs to use the
Add/Remove Programs panel
Start->Settings->Control Panel->Add/Remove Programs
and
select the "ODBC Driver for Teradata package"
5.0 Configuration
For first time users, one or more DSNs will need to be configured. This is
done through the ODBC Administrator. There is an icon for the ODBC
Administrator in the ODBC driver's program folder.
5.1 ODBC and ODBCINST INI Configuration
5.2 DSN Configuration
After starting the ODBC Administrator, click on the Add... button to
configure a new data source. This will bring up a dialog with the names
of all installed ODBC drivers. Select Teradata and then continue.
(You may use the Help button to get information on how the various fields
are used.)
Note: Your TCP/IP must be functional through Microsoft Windows(r) in
order to fully configure data sources.
5.2.1 ODBC Driver Setup for Teradata Database (Dialog Box)
Fill in the information in the first ODBC Teradata Driver Setup dialog
box.
1. A data source name is mapped to a combination of a Teradata system
running Teradata Database such as (but not limited to) a 34xx, 35xx,
3600, 43xx, 44xx, 47xx, 51xx and so on, and a default database within
that system.
2. One can optionally configure multiple data source entries for the same
Teradata system to associate different user logons, default databases,
or options. Data Source
3. Description is an optional comment field.
4. Enter the alias name or IP address of the Teradata Server you will be
using. If you are using the alias name of a server, you must either be
using Domain Name Services, or a local hosts file to resolve the named
alias. Setup will automatically add "COPn" (where n is a number) to
the name in order to search for other host IP addresses with similar
aliases, following the standard Teradata naming conventions. Multiple
server names may be entered by putting entries on separate lines.
5. The ODBC Driver Setup for Teradata Database dialog contains a new
check box in the Teradata Server Info section. If this box is checked,
the alias names entered will not be resolved to IP addresses at setup
time. Instead the driver will resolve the names at connect time.
Entering user information is optional.
6. IMPORTANT: Note that although the password is encrypted, storing a
password is never 100% secure.
5.2.2 Teradata ODBC Driver Options (Dialog Box)
The first optional dialog box which contains options that are most useful.
5.2.3 Teradata ODBC Driver Advanced Options (Dialog Box)
The second optional dialog box, Advanced, contains options that are very
risky to change; if you do not understand the effects of changing these
default settings, you should not make any changes.
6.0 Sample ODBC Applications
7.0 Restrictions
Additional restrictions are listed in the ODBC Driver for Teradata User Guide
7.1 ODBC restrictions
7.2 Binary Compatibilites
8.0 Limitations/Issues
In Release 13.0, All Teradata DSN Driver values are migrated to the new tdata32.dll path
( Default: "C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata\lib\tdata32.dll" )
Note : All Teradata DSN Driver values prior to 13.0 will be migrated and previous
Teradata DSN Driver values are available in %SYSTEMROOT%\temp\Teradata_DSN_Migration_[type]_[timestamp].txt
For restoration of previous values , use tdodbcdsn.vbs file located at
( Default: "C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata ) directory.
with the back up file.
USAGE : cscript tdodbcdsn.vbs %SYSTEMROOT%\temp\Teradata_DSN_Migration_[type]_[timestamp].txt
On 64-bit machine, User DSN's will be migrated based on location of tdata32.dll
i.e system32 or syswow64 when a 64bit or 32bit ODBC Driver for Teradata Package
is installed respectively.
New User DSN's will not be migrated with the tdodbcdsn.vbs script.
9.0 Documentation
1) ODBC Driver for Teradata User Guide
(Release 13.00.00 B035-2509-088A August 2008)
2) www.info.teradata.com
10.0 Support
10.1 Contact Information
Customers with support contracts may report problems with the ODBC Driver to
Teradata Customer Services either by phone via the regional support center or
on the web via Teradata@YourSevices
www.teradata.com
Contact your Teradata Customer Services Representative for details.
Appendix A - New ODBC 13.0 directory tree structure
The new ODBC Driver tree structure is shown in the diagram below.
C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata\
Help
Lib
Pbodb0x0.txt
Readme.txt
tdodbcdsn.vbs
tdsql.h
Appendix B - DSN Migration
DSN Migration will be automatically done by the ODBC Driver for Teradata
Package.
For explicit DSN Migration , from a DOS window, the user will change directories
to where the tdodbcdsn.vbs is located and use the below commandline to change all
Teradata DSN's to the present installed version.
For 32bit Package : cscript tdodbcdsn.vbs 32bit
For 64bit Package : cscript tdodbcdsn.vbs 64bit
For Backward DSN Migration, to restore the previous Teradata DSN driver
values , change directories to where the tdodbcdsn.vbs is available and use
the below command line .
Note : The below command only restores the DSN values which are available
at the time of installation.
cscript tdodbcdsn.vbs %SYSTEMROOT%\temp\Teradata_DSN_Migration_[type]_[timestamp].txt
Discussion
hi its very useful