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 IC61359 Status: Closed

WITH CLI STATEMENT CHAINING ON, AFTER YOU SUCCESSFULLY INSERT ROWS,
SQLROWCOUNT() WRONGLY INDICATES ZERO ROWS WERE INSERTED.

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
In CLI (Call Level Interface) applications, after you begin CLI 
array input chaining 
by setting the statement attribute SQL_ATTR_CHAINING_BEGIN, 
then you insert rows using a statement whose parameter markers 
are bound with column-wise array input, 
when you then call SQLRowCount() it wrongly indicates that zero 
rows were inserted.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of CLI applications with DB2 for Linux, UNIX and       * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* In CLI (Call Level Interface) applications, after you begin  * 
* CLI array input chaining by setting the statement attribute  * 
* SQL_ATTR_CHAINING_BEGIN, then you insert rows using a        * 
* statement whose parameter markers are bound with column-wise * 
* array input, when you then call SQLRowCount() it wrongly     * 
* indicates that zero rows were inserted.                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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. 
At a minimum, this fix should be applied on the client.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.06.2009
11.01.2010
11.12.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.1 FixList