Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84568 Status: Geschlossen

SQLSETSTMTATTR WITH SQL_ATTR_CHAINING_END INCORRECTLY RETURNS SUCCESS

Produkt:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problembeschreibung:
If you have an application that is using CLI array input 
chaining and at least one statement in the chain of statements 
returned SQL_ERROR or SQL_SUCCESS_WITH INFO, SQL_SUCCESS is 
incorrectly returned when settiing SQL_ATTR_CHAINING_END 
 
 
To reproduce : 
 
quickc 1 1 sample db2inst1 db2inst1 
sqlallocstmt 1 
sqlexecdirect 1 "drop table test" -3 
sqlexecdirect 1 "create table test (c1 smallint, c2 char(2))" -3 
sqlprepare 1 "insert into test values (?, ?)" -3 
getmemarray 1 1 10 sql_c_long 
getmemarray 1 2 10 sql_c_char 3 
 
 
sqlsetstmtattr 1 SQL_ATTR_CHAINING_BEGIN 1 
 
 
sqlbindparameter 1 1 sql_param_input sql_c_long sql_integer 0 0 
1 memarray 
sqlbindparameter 1 2 sql_param_input sql_c_char sql_char 2 0 2 
memarray 
 
updateelem 1 -1 value 32761 
updateelem 2 -1 value 2 "ch" 
sqlexecute 1 
 
sqlbindparameter 1 1 sql_param_input sql_c_long sql_integer 0 0 
1 memarray 
sqlbindparameter 1 2 sql_param_input sql_c_char sql_char 2 0 2 
memarray 
 
updateelem 1 -1 value 32768 
updateelem 2 -1 value 2 "ch" 
sqlexecute 1 
 
sqlsetstmtattr 1 SQL_ATTR_CHAINING_END 1 
sqlrowcount 1
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1 or later                             * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
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

Lösung
The problem is first fixed in DB2 10.1 FP1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
22.01.2013
22.01.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList