DB2 - Problem description
Problem IC68312 | Status: Closed |
DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ VERSION 3.8.80 FOR DB2 LUW V9.1 FIXPACK 10 | |
product: | |
DB2 CONNECT / DB2CONNCT / 910 - DB2 | |
Problem description: | |
============================================================ T4 Connectivity Type: In Sysplex environment, if the application sets the securityMechanism to ENCRYPTED_PASSWORD_SECURITY and DB2 server supports AES, getting Connection may fail sporadically with SQLException -4214. The problem has been fixed. (wsdbu00668088 wsdbu00668091) ____________________________________________________________ Type-4 XA Connectivity: The JCC driver is making duplicate authentication/connection flows to the DB2 server for LUW when opening the XA connection. (wsdbu00643372) ____________________________________________________________ Type-4 Connectivity: Driver throws an exception with SQLCODE4499 (-4499) with message "A DRDA Conversational Protocol Error was detected. Reason: 0x1245." when calling a stored procedure on DB2 for z/OS that returns a forward-only, rowset cursor. The problem has been corrected. (wsdbu00652260) ____________________________________________________________ | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of the IBM Data Server Driver for JDBC and SQLJ * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to V9.1 Fixpack 10 * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Solution | |
Problems fixed in DB2 LUW V9.1 Fixpack 10 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.04.2010 10.06.2011 10.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.10 |