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

WITH MULTI-ROW INSERT, AFTER AN APPLICATION ENDS CHAINING AND IT FAILS, THE
NEXT SQLFETCH GETS ERROR CLI0115E

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
After a CLI (Call Level Interface) application sets the 
attribute SQL_ATTR_CHAINING_END for a statement handle (to end 
Multi-Row Insert chaining) and it fails for any reason, the next 
call to SQLFetch for any statement handle by the same CLI 
application then fails with the error: 
"[IBM][CLI Driver] CLI0115E  Invalid cursor state. 
SQLSTATE=24000". 
 
The error happens only if the attribute SQL_COLUMNWISE_MRI_ON is 
set (which activates the Multi-Row Insert feature). Therefore 
the error only happens when the database server is DB2 on z/OS. 
 
The DB2 on z/OS database server gets error DSNL032I with 
REASON=00D35B13
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI users connecting to DB2 for Z                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.1                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Upgrade to DB2 v10.1.1 to get the error message correctly.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
11.12.2012
11.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList