DB2 - Problem description
Problem IC62412 | Status: Closed |
SQLROWCOUNT() RETURNS AN ESTIMATED ROW NUMBER FOR PREPARE STATEMENT | |
product: | |
DB2 CONNECT / DB2CONNCT / 950 - DB2 | |
Problem description: | |
After executing a PREPARE statement, SQLERRD3 will contain the prepared statement's estimated cardinality. For SELECT statements, this value is the estimated number of records returned. If DB2 has to reprepare at execute(e.g. bind option reopt(always)), the sqlca flows at sqlexecute. SQLRowCount() returns this sqlca(estimated number of records) for select statement instead of -1 or exact number of rows in some cases | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * SQLRowCount() after SELECT statements prepared. * **************************************************************** * PROBLEM DESCRIPTION: * * After executing a PREPARE statement, SQLERRD3 * * willcontaintheprepared statement's estimated * * cardinality.ForSELECTstatements, this value is the estimated * * numberofrecordsreturned. If DB2 has to reprepare * * atexecute(e.g.bindoption reopt(always)), the sqlca * * flowsatsqlexecute.SQLRowCount() returns * * thissqlca(estimatednumber ofrecords) for select * * statementinstead of -1 orexact numberof rows in some cases * **************************************************************** * RECOMMENDATION: * * Upgrade to 9.5 FP6 or later. * **************************************************************** | |
Local Fix: | |
N/A | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
With DB2 9.5 FP6, SQLRowCount() returns -1 for SELECT statement. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC62430 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.08.2009 25.05.2010 26.08.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6, 9.5.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) |