home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC62854 Status: Geschlossen

CLI ARRAY INPUT CHAIN RETURNS FUNCTION SEQUENCE ERROR CLI0125E

Produkt:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problembeschreibung:
If a warning is returned when you prepare a statement within a 
CLI array input chain that you started with the function 
SQLSetStmtAttr() and its attribute SQL_ATTR_CHAINING_BEGIN, the 
call of the function SQLSetStmtAttr() with attribute 
SQL_ATTR_CHAINING_END incorrectly returns SQL_ERROR and the 
application gets error CLI0125E Function sequence. 
 
The reason for error CLI0125E: 
The call of the function SQLSetStmtAttr() with attribute 
SQL_ATTR_CHAINING_BEGIN will get a warning, and the function 
exits without completing processing of SQL_ATTR_CHAINING_BEGIN 
attribute. 
This cause error CLI0125E during call to SQLSetStmtAttr() with 
SQL_ATTR_CHAINING_END attribute.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 CLI applications.                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* If a warning is returned when you prepare a statement within * 
* a  CLI array input chain that you started with the function  * 
* SQLSetStmtAttr() and its attribute SQL_ATTR_CHAINING_BEGIN,  * 
* the call of the function SQLSetStmtAttr() with attribute     * 
* SQL_ATTR_CHAINING_END incorrectly returns SQL_ERROR and the  * 
*                                                              * 
* application gets error CLI0125E Function sequence.           * 
*                                                              * 
*                                                              * 
*                                                              * 
* The reason for error CLI0125E:                               * 
*                                                              * 
* The call of the function SQLSetStmtAttr() with attribute     * 
* SQL_ATTR_CHAINING_BEGIN will get a warning, and the function * 
* exits without completing processing of                       * 
* SQL_ATTR_CHAINING_BEGIN  attribute.                          * 
*                                                              * 
* This cause error CLI0125E during call to SQLSetStmtAttr()    * 
* with  SQL_ATTR_CHAINING_END attribute.                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP1 or later.                             * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
The application doesn't return an error when a warning is 
encountered after upgrading to DB2 9.7 FP1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.08.2009
24.02.2010
16.12.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP1
Problem behoben lt. FixList in der Version
9.7.0.1 FixList