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 IC65495 Status: Geschlossen

A CLI TRACE FAILS TO DISPLAY THE CONTENTS OF THE APPLICATION BUF FER IF THE
COLUMN OR PARAMETER WAS BOUND WITH A CBVALUEMAX OF 0

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When taking a CLI trace of an application, the application 
buffer holding the column value or parameter marker value may be 
empty if the application sets the cbValueMax value to 0. 
 
For example, the following CLI trace snippet shows the problem: 
 
[11/18/2009 18:51:11.702023] SQLBindParameter( hStmt=1:1, 
iPar=1, fParamType=SQL_PARAM_INPUT, fCType=SQL_C_CHAR, 
fSQLType=SQL_CHAR, cbColDef=3, ibScale=0, rgbValue=&0012fb18, 
cbValueMax=3, pcbValue=&0012ff68 ) 
[11/18/2009 18:51:11.719392] ---> Time elapsed - +1.720000E-003 
seconds 
 
[11/18/2009 18:51:11.721445] SQLBindParameter( ) 
[11/18/2009 18:51:11.723404] <--- SQL_SUCCESS Time elapsed - 
+2.138100E-002 seconds 
 
[11/18/2009 18:51:11.725410] SQLBindParameter( hStmt=1:1, 
iPar=2, fParamType=SQL_PARAM_INPUT, fCType=SQL_C_CHAR, 
fSQLType=SQL_CHAR, cbColDef=3, ibScale=0, rgbValue=&0012fb14, 
cbValueMax=0, pcbValue=&0012ff6c ) 
[11/18/2009 18:51:11.745735] ---> Time elapsed - +2.006000E-003 
seconds 
 
[11/18/2009 18:51:11.747729] SQLBindParameter( ) 
[11/18/2009 18:51:11.749509] <--- SQL_SUCCESS Time elapsed - 
+2.409900E-002 seconds 
 
................. 
 
[11/18/2009 18:51:11.751517] SQLExecute( hStmt=1:1 ) 
[11/18/2009 18:51:11.755183] ---> Time elapsed - +2.008000E-003 
seconds 
[11/18/2009 18:51:11.756969] ( Package="SYSSH200 ", Section=4 ) 
[11/18/2009 18:51:11.762341] 
[11/18/2009 18:51:11.764467] ( Row=1, iPar=1, fCType=SQL_C_CHAR, 
rgbValue="ABC" - x'414243', pcbValue=-3, piIndicatorPtr=-3 ) 
[11/18/2009 18:51:11.777222] 
[11/18/2009 18:51:11.778995] ( Row=1, iPar=2, fCType=SQL_C_CHAR, 
rgbValue="" - x'', pcbValue=-3, piIndicatorPtr=-3 ) 
[11/18/2009 18:51:11.791185] 
 
In this case we have two parameters.   The value in the first 
parameter shows up fine when the statement is executed, however 
the value in the second parameter does not show up fine. 
 
The application calls the SQLBindParameter() API with a 
cbValueMax value of 0 on the second parameter.  When the 
statement is executed, the "rgbValue" shows up as empty string. 
This is not expected.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When taking a CLI trace of an application, the               * 
* applicationbuffer holding the column value or parameter      * 
* marker valuemay be empty if the application sets the         * 
* cbValueMax value to0.For example, the following CLI trace    * 
* snippet shows theproblem:[11/18/2009 18:51:11.702023]        * 
* SQLBindParameter( hStmt=1:1,iPar=1,                          * 
* fParamType=SQL_PARAM_INPUT,                                  * 
* fCType=SQL_C_CHAR,fSQLType=SQL_CHAR, cbColDef=3,             * 
* ibScale=0,rgbValue=&0012fb18, cbValueMax=3,                  * 
* pcbValue=&0012ff68 )[11/18/2009 18:51:11.719392] ---> Time   * 
* elapsed -+1.720000E-003 seconds[11/18/2009 18:51:11.721445]  * 
* SQLBindParameter( )[11/18/2009 18:51:11.723404] <---         * 
* SQL_SUCCESS Time elapsed -+2.138100E-002 seconds[11/18/2009  * 
* 18:51:11.725410] SQLBindParameter( hStmt=1:1,iPar=2,         * 
* fParamType=SQL_PARAM_INPUT,                                  * 
* fCType=SQL_C_CHAR,fSQLType=SQL_CHAR, cbColDef=3,             * 
* ibScale=0,rgbValue=&0012fb14, cbValueMax=0,                  * 
* pcbValue=&0012ff6c )[11/18/2009 18:51:11.745735] ---> Time   * 
* elapsed -+2.006000E-003 seconds[11/18/2009 18:51:11.747729]  * 
* SQLBindParameter( )[11/18/2009 18:51:11.749509] <---         * 
* SQL_SUCCESS Time elapsed -+2.409900E-002                     * 
* seconds.................[11/18/2009 18:51:11.751517]         * 
* SQLExecute( hStmt=1:1 )[11/18/2009 18:51:11.755183] --->     * 
* Time elapsed -+2.008000E-003 seconds[11/18/2009              * 
* 18:51:11.756969] ( Package="SYSSH200 ",Section=4             * 
* )[11/18/2009 18:51:11.762341][11/18/2009 18:51:11.764467] (  * 
* Row=1, iPar=1,fCType=SQL_C_CHAR, rgbValue="ABC" - x'414243', * 
* pcbValue=-3,piIndicatorPtr=-3 )[11/18/2009                   * 
* 18:51:11.777222][11/18/2009 18:51:11.778995] ( Row=1,        * 
* iPar=2,fCType=SQL_C_CHAR, rgbValue="" - x'',                 * 
* pcbValue=-3,piIndicatorPtr=-3 )[11/18/2009                   * 
* 18:51:11.791185]In this case we have two parameters.  The    * 
* value in the firstparameter shows up fine when the statement * 
* is executed,however the value in the second parameter does   * 
* not show upfine.The application calls the SQLBindParameter() * 
* API with acbValueMax value of 0 on the second parameter.     * 
* When thestatement is executed, the "rgbValue" shows up as    * 
* emptystring.  This is not expected.                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7, Fixpak 2                                * 
****************************************************************
Local-Fix:
Set the cbValueMax to a value that coincides with the maximum 
length of the application buffer that holds (or will hold) the 
contents of the data instead of to a value of 0.
verfügbare FixPacks:
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

Lösung
First fixed in DB2 UDB Version 9.7, Fixpak 2
Workaround
See LOCAL FIX
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.01.2010
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.
Problem behoben lt. FixList in der Version
9.7.0.2 FixList