Unable to Get Multiple Result Sets from DB2® when using a Version 5.0 Datasource
 Technote (troubleshooting)
 
Problem(Abstract)
When executing a query against a DB2 V7.2 database from a Version 5.0 datasource configured in any release of WebSphere® Application Server V5.0, only one result set is returned when there should be multiple result sets. After the first result set is processed, getMoreResults() returns false when it should return true. This problem does not occur if a Version 4.0 data source is used in V5.0 or in previous versions of WebSphere.
 
Cause
The JDBC specification mandates that WebSphere has to close the first result set when getMoreResults() is called. In WebSphere V5.0, the relational resource adapter (RRA) wrappers explicitly close the result set. In V4.0, there were no wrappers so WebSphere relied on the JDBC driver to close the result set but there was no way to enforce it. It turns out that DB2 did not close the result sets, and now in V5.0, when they are closed by WebSphere, getMoreResults() can't find the next result set. This is a defect with DB2, see APAR IY43300.
 
Resolving the problem
To resolve the problem, apply DB2 7.2 Fix Pack 10a (or later). It is available to download at the DB2 support site. The fix to this problem will allow subsequent result sets to be found even though the first one was closed.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Data & Information Management DB2 Universal Database 3rd Party Tools - Websphere Platform Independent 7 DB2 UDB Express
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > DB Connections/Connection Pooling
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1154181
IBM Group: Software Group
Modified date: Dec 9, 2003