home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC64831 Status: Closed

JCC THROWS SQLEXCEPTION WITH ERROR CODE -4476 WHEN
PREPAREDSTATEMENT.EXECUTEQUERY() DOESN'T RETURN A RESULTSET.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If PreparedStatement.executeQuery() doesn't return a ResultSet, 
JCC throws SQLException with error code -4476. This behavior is 
JDBC compliant. Now we add a new DataSource property 
allowNullResultSetForExecuteQuery, the type of this property is 
integer and the default is 
com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET. If it is set to 
com.ibm.db2.jcc.DB2BaseDataSource.YES, JCC will NOT throw 
SQLException if executeQuery returns null ResultSet. This 
behavior is not compliant with JDBC specification. This property 
only applies to SQL CALL statement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If PreparedStatement.executeQuery() doesn't return a         * 
* ResultSet, JCC throws SQLException with error code -4476.    * 
* This behavior is JDBC compliant. Now we add a new DataSource * 
* property allowNullResultSetForExecuteQuery, the type of this * 
* property is integer and the default is                       * 
* com.ibm.db2.jcc.DB2BaseDataSource.NOT_SET. If it is set to   * 
* com.ibm.db2.jcc.DB2BaseDataSource.YES, JCC will NOT throw    * 
* SQLException if executeQuery returns null ResultSet. This    * 
* behavior is not compliant with JDBC specification. This      * 
* property only applies to SQL CALL statement.                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 1.                       * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 1.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64969 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.11.2009
26.04.2010
26.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList