DB2 - Problem description
Problem IC64969 | Status: Closed |
JCC THROWS SQLEXCEPTION WITH ERROR CODE -4476 WHEN PREPAREDSTATEMENT.EXECUTEQUERY() DOESN'T RETURN A RESULTSET. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - 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.5 Fix Pack 5. * **************************************************************** | |
Local Fix: | |
n/a | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.5 Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.12.2009 26.04.2010 26.04.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) |