Teradata JDBC Driver 3.1.0.103
Part of the Teradata Tools and Utilities 7.1 product suite
System Requirements
-------------------
This release of the Teradata JDBC Driver requires JDK/JRE 1.3 or 1.4.
This release of the Teradata JDBC Driver supports Teradata Database V2R5.0,
V2R5.1, V2R6.0, V2R6.1, V2R6.2, and 12.0.
This release requires a minimum patch level when running with a V2R5.0 DBS.
The version should be at the latest V2R5.0 E-Fix level, with the minimum
level being 5.0.0.23.
What's New
----------
- Discontinued support for the Type 3 Teradata JDBC Driver.
- Discontinued platform-specific install packages. The Teradata JDBC Driver
is now distributed as platform-independent jar files.
Release Notes
-------------
This section highlights issues that you should be aware of when upgrading to
the 3.1.0.103 release of the Teradata JDBC Driver. Please refer to the Teradata
JDBC Driver User Guide for more information about the driver.
This release includes changes to address the following DRs:
DR 88400 RCI: Null Pointer dereference in ParcelFactory.java
DR 128019 IndexOutOfBoundsException at java.io.BufferedInputStream for response message size near 65100 bytes
DR 128088 TTU 7.1 Teradata JDBC Driver 3.1.0.103 to support TD 12.0 (backport DR 108390)
This release includes changes to address the following DRs, originally included in
Release 3.1.0.102:
DR 85852 TeraLocalPrepared/CallableStatement.getResultSetType and other incorrect methods
DR 87267 JDBC error: ('0A'X) is not a valid Teradata SQL token
DR 92189 Large result sets don't close properly and leave spool files on DBS
DR 94605 Statement.addBatch fails when SQL contains trailing space
DR 94805 NPE thrown when calling Statement.close() after ResultSet.close()
DR 95078 interoperability issue when Connection.close called while query is in progress
DR 95828 CLIENT_CHARSET DataSource property
This release includes changes to address the following DRs, originally included in
Release 3.1.0.101:
DR 93549 Type 4 driver Get-column-by-name from 2nd RS throws "column not found" exception
This release includes changes to address the following DRs, originally included in
Release 3.1.0.100:
DR 84672 RFC: Remove platform packaging for JDBC Type 4 driver
DR 85393 RFC: Remove Type 3 driver from product
DR 91951 CLIENT_CHARSET connection parameter
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.9:
DR 91351 number of parameters mismatch error for reused prepared stmt w/bound NULL value
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.8:
DR 87192 tdgssjava fails to connect to V2R5.1 after connecting to V2R6
DR 87605 TDGSS fails randomly
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.7:
DR 87308 first RS metadata incorrectly retained for second RS from Statement.executeQuery
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.5:
DR 86267 tdgssjava fails when using IBM security provider on AIX
DR 86344 NullPointerException from AssignParcel.setUserName through WebSphere
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.4:
DR 85320 Improve Diffie Hellman key exchange to provide more secure key
DR 85837 TDGSS 5.1 Java library is incompatible with V2R6 DBS
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.3:
DR 63738 Connection.getConnection(String url) returns null pointer exception
DR 69005 TeraDatabaseMetaData uses == and != operators with strings
DR 69193 setString and setBytes throw NegativeArraySizeException when size
DR 69293 PreparedStatement.setMaxRows is not functional;doesn't limit #rows
DR 85024 Statement.close() hangs after autocommit failure in execute()
DR 85068 exception thrown when logging off
DR 85124 tdgssjava not thread-safe
DR 85319 Java library uses static variables and does not handle errors cleanly
DR 85517 incorrect exception handling for logon failure
DR 85558 WebSphere 5.0 setCursorName exception: TeraStatement: function not supported
This release includes changes to address a fix for the following DR, originally included
in Release 3.1.0.2:
DR 68567 java.sql.Date object returns time component as Not Zero
This release includes changes to address fixes for the following DRs, originally included
in Release 3.1.0.1:
DR 69051 RFC: Type 4 COP discovery should mimic CLI
DR 69254 Sessions remain in the Pool indefinitely
DR 84981 RFC: Enhanced diagnostics
Troubleshooting Topics
----------------------
Type 3 Teradata JDBC Driver is Discontinued
-------------------------------------------
The Type 3 Teradata JDBC Driver is no longer included. Related software, such as the
Teradata JDBC Gateway and its administration GUI, is also no longer included.
It is necessary for customers to move their applications from the Type 3 Teradata JDBC
Driver to the Type 4 Teradata JDBC Driver.
Solution:
The application's connection URL should be changed as follows:
JDBC Type 3: jdbc:teradata://gwhost:port/dbshost
JDBC Type 4: jdbc:teradata://dbshost
Applet Support is Limited
-------------------------
The applet security model only permits applets to connect to the system that
the applet was downloaded from. With this release, the following three-tier
application architecture is no longer supported:
- Client tier consisting of an applet using the Type 3 Teradata JDBC Driver
- Middle tier consisting of a web server and Teradata JDBC Gateway
- Back-end tier consisting of the Teradata Database
This release of the JDBC Driver supports the following three-tier J2EE
application architecture:
- Client tier consisting of browser-based HTML/DHTML and/or J2EE client applet
- Middle tier consisting of a J2EE application server - servlets and/or EJBs
using the Type 4 Teradata JDBC Driver
- Back-end tier consisting of the Teradata Database
Solution:
Remove JDBC API usage from applets, and relocate JDBC API usage to an
application server tier.
Installation
------------
This release of the Teradata JDBC Driver is distributed as platform-independent
jar files. For downloading convenience, the platform-independent jar files are
bundled together and provided in both zip format and tar format.
TeraJDBC__indep_indep.03.01.00.103.zip and TeraJDBC__indep_indep.03.01.00.103.tar
both contain the same set of platform-independent files:
readme.txt - this file
terajdbc4.jar - the Teradata JDBC Driver
tdgssjava.jar - the Teradata security library
Download either the zip file or the tar file, and unzip (or untar) the downloaded
file into a directory of your choice, and then set your classpath to refer to the
necessary jar files.
Your classpath must include:
terajdbc4.jar
tdgssjava.jar
Your classpath must NOT include any jar files from any previous releases of
the Teradata JDBC Driver. It is recommended, but not required, that any
previous release of the Teradata JDBC Driver be uninstalled prior to
downloading and using this release of the Teradata JDBC Driver.
Documentation
-------------
The Teradata JDBC Driver User Guide Release 03.01.00 is available online
at http://www.info.teradata.com/
Navigate to "Teradata Data Warehousing", then "Teradata Tools and Utilities",
then "Java Database Connectivity (JDBC)", and select the User Guide Release
03.01.00, which corresponds to this release of the Teradata JDBC Driver.
Documentation for how to use the Teradata JDBC Driver with supported application
servers is available on the http://www.teradata.com Teradata Download Center in
the Teradata JDBC Driver section.
|
|
|
|