home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC69097 Status: Geschlossen

DOCUMENTATION OF CHANGES IN IBM DATA SERVER DRIVER FOR JDBC AND SQLJ
VERSION 3.61.65/4.11.69 FOR DB2 LUW V9.7 FIXPACK 3

Produkt:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problembeschreibung:
============================================================ 
Documentation of changes in IBM Data Server Driver for JDBC 
and SQLJ version 3.61.65/4.11.69 for DB2 LUW V9.7 Fixpack 3. 
The previous version was 3.59.81/4.9.78 for DB2 LUW V9.7 
Fixpack 2. 
 
____________________________________________________________ 
T4 Connectivity: With the support of EXPLAIN MODE special 
registers starting in DB2 z/OS v10, EXPLAIN MODE sections 
need to be bound by the DB2Binder.  The required support is 
added in the driver. (wsdbu00646812) 
 
____________________________________________________________ 
All Connectivities: PreparedStatement.setCharacterStream () 
throws an indexoutofbounds exception for an XML document 
greater than 1GB. (wsdbu00642607) 
 
____________________________________________________________ 
All Connectivities: Against IDS, when auto generated keys 
are requested on a table without any auto generated columns 
defined via Connection.prepareStatement (String, int), 
SQLCODE -206 is encountered. (wsdbu00654101) 
 
____________________________________________________________ 
All Connectivities: Accessing the result set returned by 
a SQL stored procedure created with the CONCURRENT ACCESS 
RESOLUTION W (Wait for outcome) option, results in a null 
pointer exception. (wsdbu00642450) 
 
____________________________________________________________ 
All Connectivity Types: If the target server is i5 
and progressiveStreaming is on (the default is on), 
Clob.position(Clob, long)/Blob.position(Blob, long) or 
PreparedStatement.setBlob/setClob may throw an exception 
with error code -423. (wsdbu00664162) 
 
____________________________________________________________ 
All Connectivity Types: Previously, setObject with value 
null for static path would fail with SQLException "Invalid 
data conversion: Parameter instance null is invalid for 
 the requested conversion". Now JCC allows setObject 
with null for static path if it is not for z/OS stored 
procedures. (140483) 
 
____________________________________________________________ 
T4 Connectivity Type: If client reroute is configured 
and queryTimeOut is set, if the primary server goes down 
and the application reroutes to the alternative server, 
the application may hang. (141179) 
 
____________________________________________________________ 
All Connectivity Type: JCC now does range checking 
on DataSource property updateCountForBatch and 
cursorSensitivity. If the property is set to a value 
other than 0, 1, or 2, the driver will throw an exception. 
(wsdbu00661126, wsdbu00661167) 
 
____________________________________________________________ 
SQLJ All Connectivities: The SQLJ Customizer process 
returns a zero return code when the customization is 
successful but the SQLJ Bind invoked by it failed. The SQLJ 
Binder is invoked automatically by the SQLJ Customizer in a 
single process. So if the Binder fails, the Customizer 
should return a non-zero return code. (141014) 
 
____________________________________________________________ 
SQLJ All Connectivities: An ArrayIndexOutOfBounds exception 
occurs when statement caching is turned on under WebSphere 
6.1, and a single SQLJ statement is executed in both 
batched and non-batched execution paths. (wsdbu00653325) 
 
____________________________________________________________ 
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 XA Connectivity: Under a sysplexWLB environment, an 
XAException with XAER_PROTO error might be thrown when an 
error occurs on the network connection flow between the 
application and the DB2 server. (wsdbu00643370, 140754) 
 
____________________________________________________________ 
Type-4 XA Connectivity: Under a sysplexWLB environment, the 
JCC driver repeatedly tries to connect to the member that 
is already down. It should try to connect to the other 
available members. (wsdbu00661116) 
 
____________________________________________________________ 
Type-4 Connectivity: Under a sysplexWLB environment, an 
SQLException with SQLCODE204 (-204) might be thrown during 
automatic client reroute. (wsdbu00661111, 141161) 
 
____________________________________________________________ 
Type-4 Connectivity: Under a sysplexWLB environment, the 
application gets an XAException with XAER_DUPID error when 
re-executing XA start and the SQL statement during 
automatic client reroute. However, the subsequent XA End 
does not give any error. The new behavior is to throw an 
XAER_RBOTHER exception on XA End. This will inform the 
application that the global transaction is not in the 
correct state after the XAER_DUPID error and the 
application can issue XA Rollback to remedy the problem. 
(wsdbu00655926, 141529) 
 
____________________________________________________________ 
Type-4 Connectivity: Under a sysplexWLB environment, 
applications might hang if they get a 
java.net.NoRouteToHostException when some members 
are down. (wsdbu00655918, 141894) 
 
____________________________________________________________ 
Type-4 Connectivity: Under a sysplexWLB environment, an 
SQLException with SQLCODE20398 (-20398) will be thrown if 
one of the input parameters for a PreparedStatement is an 
inputStream and the JCC driver is re-executing the 
statement when automatic client re-route occurred. This is 
not the correct behavior. The statement should not be 
retried because part of the input steam might have been 
consumed and it cannot be restarted from the beginning of 
the inputStream. (wsdbu00643356, 139098) 
 
____________________________________________________________ 
All Connectivities: The DBTimestamp error message 
incorrectly prints out the ISO format as 
yyyy-mm-dd.hh.mm.ss[.ffffffffffff][ ](+|-)th:tm and 
yyyy-mm-dd.hh.mm.ss[.ffffffffffff] where the period between 
dd and hh should be hyphen. The correct format is 
yyyy-mm-dd-hh.mm.ss[.ffffffffffff][ ](+|-)th:tm 
and yyyy-mm-dd-hh.mm.ss[.ffffffffffff]. 
(wsdbu00654941 wsdbu00656138 ) 
 
____________________________________________________________ 
Type-2 LUW Connectivity: There are some environments where 
multiple JDBC drivers can exist in the same JVM. Some of 
these drivers accept the URL jdbc:default:connection on the 
client side while others only accept it in the server side 
stored procedure environment. Previously the JCC T2 LUW 
driver accepted the dbc:default:connection URL on the 
client side by returning "true" for 
java.sql.Driver.acceptsURL() and then eventually fails 
while loading the type 2 native library on the client side. 
This problem has been resolved by this defect. 
(wsdbu00655930) 
 
____________________________________________________________ 
Type-4 Connectivity: Driver throws an exception with 
SQLCODE4499 (-4499) with message "A DRDA Data Stream 
Syntax Error was detected" when describe information 
is returned for a large number of columns such that the 
amount of data returned expand exactly 2 complete, full 
DRDA blocks. (142836) 
 
____________________________________________________________ 
Type-4 Connectivity: Driver throws an exception with 
SQLCODE4470 (-4470) with message "Invalid operation: 
result set is closed" when ResultSet.next () is invoked 
following a seamless failover.  Driver code has been 
enhanced to make the failover non-seamless if there are 
open result sets at the time of failover. (141370) 
 
____________________________________________________________ 
Type-4 Connectivity: When driver properties 
"affinityFailbackInterval", "enableSeamlessFailover" 
and "enableClientAffinitiesList" are enabled, driver 
fails to failback to the primary server if the primary 
server is stopped and restarted. (137964) 
 
____________________________________________________________ 
Type-4 Connectivity: When driver properties 
"affinityFailbackInterval" and "sslConnection" are both 
enabled, driver fails to failback to the primary server 
because it was not creating a SSL socket to detect 
the availability of the failback server. (137301) 
 
____________________________________________________________ 
All Connectivity Types:  An extra space is injected into the 
string literal when escape syntax is used with a return 
value. (137966) 
 
____________________________________________________________ 
All Connectivity Types: Driver throws a 
java.lang.NullPointerException when 
DatabaseMetaData.getIndexInfo is called and servers 
returns SQLCODE413 (-413). (wsdbu00660747) 
 
____________________________________________________________ 
Type-4 Connectivity: No data is returned from the result 
set when connecting to DB2 for iSeries and 
DatabaseMetaData.getTables is called. (wsdbu00652278) 
 
____________________________________________________________ 
All Connectivity Types: The JCC driver may go into an 
infinite loop when setCharacterStream without length takes 
a stream that contains surrogate characters. (wsdbu00655959) 
 
____________________________________________________________ 
All Connectivity Types: Under binary XML, JCC prints out 
each item separator as a new line.  Now it is printed 
out as a space. (wsdbu00648349) 
 
____________________________________________________________ 
All Connectivity Types: Some data may be missing when 
setAsciiStream is used under binary XML. (137349) 
 
____________________________________________________________ 
Type-4 Connectivity:  Against servers which support binary 
XML, and deferPrepares and binary XML are enabled, a -301 
will occur when calling PreparedStatement.setSQLXML() 
against a BINARY, VARBINARY, or BLOB data type.  This is 
expected.  However, when the JDBC driver tries again to 
execute the statement, it will flow binary XML to the server 
when textual XML should be sent. (wsdbu00660370) 
 
____________________________________________________________ 
All Connectivities:  When SQLCODE -911 is returned from DB2 
LUW server, while accessing the result set returned for a 
select statement, a null pointer exception is thrown by the 
driver. (wsdbu00665571) 
 
 
____________________________________________________________ 
All Connectivities:  Parsing a XML sequence returned from 
the server as a result of a XQuery via the SAX source is 
resulting in a bug check exception from the driver. 
(wsdbu00642659) 
 
____________________________________________________________ 
T4 Connectivity Type: In a Sysplex environment, if the 
application sets the securityMechanism to 
ENCRYPTED_PASSWORD_SECURITY and DB2 server supports 
AES, getting a connection may fail sporadically 
with SQLException -4214. (wsdbu00668088) 
 
____________________________________________________________ 
All Connectivity Types: A Java StackOverflowError may occur 
when the target DB2 for LUW server returns an SQL error 
with error code -805 and the JCC property 
retrieveMessagesFromServerOnGetMessage is turned on. 
(wsdbu00670958) 
 
____________________________________________________________ 
SQLJ All Connectivities: An SQLException with the message 
'ResultSet is closed' may occur while retrieving data 
from a SQLJ singleton SELECT statement i.e. SELECT INTO 
statement under WebSphere(WAS) 7 server. (wsdbu00674905) 
 
____________________________________________________________ 
All Connectivities: When the DELIMIDENT variable is turned 
on in IDS and quoted column names are used to specify the 
auto generated keys column names, the driver is throwing 
a SQLException with -4461 SQL code. (wsdbu00671428)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of the IBM Data Server Driver for JDBC and SQLJ        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V9.7 Fixpack 3                            * 
****************************************************************
Local-Fix:
n/a
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Problems fixed in DB2 LUW V9.7 Fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.06.2010
23.09.2010
23.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP3
Problem behoben lt. FixList in der Version
9.7.0.3 FixList
9.7.0.3 FixList