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

AFTER SQLPUTDATA IS CALLED, CALLING SQLPARAMDATA FOR THE SAME STATEMENT
FAILS WITH ERROR CLI0125E

product:
DB2 COMMON CLIE / DBCMNCLNT / A50 - DB2
Problem description:
This issue affects applications that use the CLI (Call Level 
Interface) API. 
It affects such applications that are connected to a DB2 on z/OS 
database but not applications that are connected to a DB2 LUW 
database. 
 
After an application calls SQLPutData for a given statement 
handle, any call of SQLParamData for the same statement handle 
fails (returns SQL_ERROR) with error code CLI0125E (Function 
sequence error). 
 
Because PHP uses the CLI API internally, this defect can cause a 
parameterized query using host variables that is executed by a 
PHP application to get error CLI0125E.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of applications for DB2 on Linux, UNIX and Windows     * 
* that use the CLI (Call Level Interface) API                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************
Local Fix:
Solution
Problem was first fixed in DB2 10.5 Fix Pack 5. 
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       :
21.08.2014
23.03.2015
23.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList