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

FOR SQLFETCH() RGBVALUE IN CLI TRACE IS TRUNCATED WHEN USING DB2TRC -CLI
OPTION

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
rgbValue difference in classical trace vs db2trc -cli trace for 
SQLFetch(). when using db2trc -cli rgbvalue is truncating in cli 
traces 
 
classical trace snippet: 
 
SQLFetch( hStmt=1:7 ) 
       > Time elapsed - +8.000000E-006 seconds 
( iRow=1, iCol=1, fCType=SQL_C_WCHAR, rgbValue="DSYLI" - 
x'4400530059004C004900', pcbValue=10, piIndicator=10 ) 
 
 
db2trc -cli trace snippet: 
 
SQLFetch( hStmt=1:7 ) 
       > Time elapsed - +6.000000E-006 seconds 
( iRow=1, iCol=1, fCType=SQL_C_WCHAR, rgbValue="D" - 
x'44000000000000000000', pcbValue=10, piIndicator=10 )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpack 11 or Later                  * 
****************************************************************
Local Fix:
Use classical cli trace instead of db2trc -cli
Solution
First Fixed in DB2 LUW v9.7 Fixpack 11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

04.09.2014
08.10.2015
08.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList