DB2 - Problem description
Problem IC71519 | Status: Closed |
OCISTMTEXECUTE INCORRECTLY RETURNS OCI_NO_DATA WHEN THERE IS AN EMPTY RESULT SET | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When using the IBM DB2 Data Server Driver for DB2CI, the OCIStmtExecute API is incorrectly returning OCI_NO_DATA when there is an empty result set returned. OCI_NO_DATA should be returned on OCIFetch but not OCIStmtExecute. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * When using the IBM DB2 Data Server Driver for DB2CI, the * * OCIStmtExecute API is incorrectly returning OCI_NO_DATA when * * there is an empty result set returned. OCI_NO_DATA should * * be returned on OCIFetch but not OCIStmtExecute. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7, Fixpak 4 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 Version 9.7, Fix Pack 4 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC71651 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.09.2010 02.05.2011 02.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7., 9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |