The purpose of these release notes is to make you aware of any special actions required to configure and use the IBM Informix JDBC Driver on your computer. This file also describes new features and feature differences from earlier versions of this product and other IBM Informix products and how these differences affect current products. This release notes document is not intended to be all inclusive; it should be used as an addendum to the IBM Informix JDBC Driver Programmer's Guide, Version 3.0, which provides thorough information about product features and behavior. These release notes are written for Java programmers who use the JDBC API to connect to IBM Informix databases via the IBM Informix JDBC Driver.
IBM Informix JDBC Driver 3.0 is supported with the following server versions:
To use the IBM Informix JDBC Driver, you must have JDK 1.3.1 (or later) installed. (JDK 1.4.2 or later is recommended.) Please refer to http://java.sun.com/products/jdbc/ for details.
The following new features are not yet documented in IBM Informix JDBC Driver Programmer's Guide, Version 3.0:
jdbc:informix-sqli://3ffe:ffff:ffff:ffff:0::12:8088:informixserver=X...
For more information about workarounds, see Fixed
Problems.
g_1000 group - - i=100
ids1000_secondary ontlitcp amazon sec_1000 g=g_1000
ids1000_primary ontlitcp amazon prim_1000 g=g_1000
Now if the JDBC application uses a connection URL that uses this sqlhosts file and group name to make a connection, the JDBC driver will always connect to the primary server. The following is an example of such a URL:"jdbc:informix-sqli:informixserver=g_1000;user=foo;password=XXXX;SQLH_TYPE=FILE;SQLH_FILE=/informix/sqlhosts"
An exception will be thrown if the JDBC driver cannot find a primary server in the group.
Note: Enforcing connections to the primary server is enabled for Dynamic Server, Version 9.40.XC6 and later only.
These features are documented in the IBM Informix: JDBC Driver Programmer's Guide.
You cannot include an explanation point character (!) in your installation path.
Due to a Sun Microsystems Java (TM)
Bug 4361575 fix in JDK 1.4, UDT/UDR manager helper classes included in the ifxtools.jar
in the JDBC driver are not accessible from a packaged class. In previous releases,
JDBC driver UDT/UDR manager helper classes from ifxtools.jar were not
part of any package/named namespace, thus users with JDK 1.4 will not be able
to use these classes from any packaged class or named namespace.
As a part of a fix, the following
change was made in the JDBC driver. All the helper classes for UDT/UDR in ifxtools.jar
have been made part of the namespace / package called udtudrmgr.
The unpackaged version of these classes is also included for backward compatibility
with JDK 1.3. Users trying to use UDT/UDR manager classes in JDK 1.4 from the
packaged class will need to use following kind of import statements in their
programs:
Except for the pickaseat demo, the examples listed in the IBM Informix JDBC Driver Programmer's Guide, Version 3.0, use the DriverManager.getConnection() method to get a database connection. Sun Microsystems recommends using a DataSource object instead. For more information, refer to the Sun documentation and to the README.TXT file in the demo/pickaseat directory.
The
following are required. Otherwise, the java.net library might throw a java.net.UnknownHostException
when connecting to an IDS server using host with an ipV6 address.
The following defects were corrected in version 3.00.JC3:
PTS # | Description |
172546 | CANNOT DO SETSTRING ON THE PREPARED STATEMENT FOR A DATE FIELD IN DRIVER JC6 IN PREPARED STATEMENT |
172786 | 3.00.JC2 FAILS CONNECTION TESTS WHEN LDAP IS USED FOR SERVER:PORT LOOKUP |
172903 | JDBC CALLING STORED PROCEDURE WITH OUT PARAM OF STRUCT/ARRAY CANNOT RESOLVE UDR - AND WITH RETURNING CLAUSE THROWS NOT SUPPORTED EXCEPTION |
172526 | JDBC SETTIMESTAMP PROBLEM WITH DAYLIGHT SAVING TIME |
173318 | 3.00.JC1+ FAILS WITH SE SERVER (7.25.UC5, 5.20) ERROR -554 SYNTAX DISALLOWED IN THIS DATABASE SERVER |
172920 | CAN NOT CONNECT TO A 7.25 SE DATABASE, EVEN WHEN USING THE "USEV5SERVER=1" FLAG. 2.21.JC6 3.00.JC2 |
173447 | GET NULLPOINTEREXCEPTION IN SETPROPERTY WHEN CONNECT TO DATABASE BY MULTI THREADS. |
173549 | A CALL TO SETIFXIFX_ISOLATION_LEVEL METHODS OF IFXXADATASOURCE DOES NOT HAVE AN EFFECT ON THE SERVER |
173877 | CANNOT RESOLVE UDR FOR SERVER THAT DO NOT SUPPORT SQ_FPDESCRIBE |
173687 | WHEN GETIFXLOBCACHE() IS CALLED WITHOUT A PRECEEDING SETIFXLOBCACHE(0), IT RETURN JAVA.LANG.NUMBERFORMATEXCEPTION: NULL |
173659 | DRIVER GIVES ERROR ARRAYBOUNDEXCEPTION UNDER LOAD IN A MULTI THREADED ENVIRONMENT. |
173983 | JAVA.SQL.SQLEXCEPTION: UNKNOWN OBJECT TYPE |
174218 | WEBSPHERE NULL POINTER ERROR WHEN ACCESSING BLOB USING UNCOMMITTED READ |
174180 | JDBC 3.00 DOES NOT RELEASE STATEMENTS |
172583 | DRIVER CRASHES WITH NULLPOINTER EXCEPTION WHILE INSERTING INTO TABLE CONTAINING CLOB DATATYPE |
172823 | SETSTRING METHOD OF PREPARED STATEMENT DOES NOT CONVERT STRING TO SERIAL8 DATATYPE OF THE ENGINE AS PER EXPECTED |
172966 | JAVA.SQL.SQLEXCEPTION: ROW/COLUMN INDEX OUT OF RANGE |
The following defects were corrected in version 3.00.JC1 and 3.00.JC2:
PTS # |
Description |
170782 |
JDBC DOES NOT RETURN ERROR MESSAGE TEXT WHEN ERROR 7610 IS ENCOUNTERED. |
171611 |
CLOSING A CONNECTION OBTAINED VIA XACONNECTION GIVES ERROR ON CLOSING IT IF XAEND HAS NOT BEEN DONE. |
171651 |
IN SENDSTREAMBLOB, ON ERROR WE UNLOCK THE SESSION, BUT SESSION NEVER LOCKED. |
171694 |
PASSING A NON-EMPTY LIST/COLLECTION AFTER AN EMPTY LIST/COLLECTION GIVES -1207 "CONVERTED VALUE DOES NOT FIT INTO THE ALLOTTED SPACE" |
171818 |
SELECTING A CLOB IN ONE THREAD WHILE RUNNING OTHER SELECTS ON ANOTHER THREAD CAUSES -408, SOCKET WRITE ERRORS, AND HANGS |
171958 |
RESULTSET.NEXT THROW ROW/COLUMN INDEX OUT OF RANGE IF SETFETCHSIZE() WAS CALLED |
172005 |
IFXRESULTSET.GETUNLOADSTRING RETURNS INCORRECT VALUE IN TH_TH.THAI620 |
172020 |
NULL POINTER EXCEPTION IN CLEARPENDING |
172255 |
CUSTOMER FOUND THAT INITIALIZING CHARACTER ARRAY IN IFXPREPARDSTATEMENT.JAVA IS EATING LOT OF CPU CYCLES. |
172471 |
RESULTSET.BEFOREFIRST() DOES NOT CHANGE THE CURRENT ROW. RS.LAST(); RS.BEFOREFIRST(); RS.NEXT() WILL NOT RETURN 1ST ROW |
171254 |
JDBC NIGHTLY TEST FAILS. SMARTBLOB/RSMBL_01_X2 GETS NO CASTE FROM BLOB TO BYTE WHEN INSERTING A NULL INTO A BYTE COLUMN USING EXECUTEUPDATE() |
171277 |
WEBSPHERE APPLICATION SERVER: STATEMENT IS INVALID WITHIN A GLOBAL TRANSACTION |
171291 |
A CALL TO SETIFXIFX_ISOLATION_LEVEL METHOD OF IFXCONNECTIONPOOLDATASOURCE DOESNT HAVE EFFECT ON THE SERVER |
171424 |
IFXPREPAREDSTATEMENT.EXECUTEBATCH FAILED WHEN INSERTING NULL - CONNECTION HANGS |
171425 |
IFXJDBCX.JAR IS NOW REQUIRED. JAVA.LANG.NOCLASSDEFFOUNDERROR: COM/INFORMIX/JDBCX/IFXXAREUSABLECONNECTION |
171473 |
JDBC DRIVER DOES NOT INSERT A NULL INTO AN INT8 PARAMETER - PREPAREDSTATEMENT |
171539 |
ERROR WHEN INSERTING A VALID INTERVAL VALUE THROUGH A PREPARE STMT |
171572 |
SESSION NOT LOCKED FOR SMART BLOB API'S IN JDBC DRIVER |
The Xerces XML library xerces.jar has been removed from distribution with the IBM Informix JDBC driver 3.00. Xerces is an open source library that is freely available for download from the following location: http://www.alphaworks.ibm.com/tech/xml4j
Java and all Java-based
trademarks and logos are trademarks or registered trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
Licensed Material. Property
of IBM.
© Copyright International Business Machines Corporation 2005. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.