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

CALLING SQLPARAMDATA() WITH WRONG PARAMETER MARKER DOESN'T THROW ERROR
IN INTERLEAVED MODE

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
When attribute sql_attr_interleaved_stream_putdata or 
sql_attr_iinterleaved_stream_putdata is set, and lets say 2,3 
and 4th parameter marker in statement are in  DATA_AT_EXEC 
mode.Now calling SQLParamData() with parameter number as say 8 
where 8 is a non-existing parameter marker,CLI driver  doesn't 
throw any error. Data supplied for above is inserted into next 
available column which is incorrect behavior.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI driver DB2 v97                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When attribute sql_attr_interleaved_stream_putdata or        * 
*                                                              * 
* sql_attr_iinterleaved_stream_putdata is set, and lets say    * 
* 2,3                                                          * 
* and 4th parameter marker in statement are in  DATA_AT_EXEC   * 
*                                                              * 
* mode.Now calling SQLParamData() with parameter number as say * 
* 8                                                            * 
* where 8 is a non-existing parameter marker,CLI driver        * 
* doesn't                                                      * 
* throw any error. Data supplied for above is inserted into    * 
* next                                                         * 
* available column which is incorrect behavior.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V97FP2                                            * 
****************************************************************
Local Fix:
None. Applications shoud use correct index for parameter markers
available fix packs:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
First fixed in DB2 UDB version v97 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.03.2010
07.07.2010
07.07.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList