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

CLI BASED APPLICATION USING SQLGETDATA TO RETREIVE CLOB AGAINST NFM MAY
HAVE EXTRA CHARACTERS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
CLI based application using SQLGetData against NFM zos systems 
can get extra characters causing the data retreived to be 
interpretted incorrectly. 
 
The problem is caused by a second call to SQLGetData passing 
cbValueMax=0 when the call wasn't necessary. This is done before 
the actual SQLGetData call with the actual required length of 
data being retreived. 
 
 
SQLGetData( hStmt=1:2, iCol=1,fCType=SQL_C_CHAR, 
rgbValue=&00e1d4d7, cbValueMax=0, 
pcbValue=&00e1d498 ) 
     ---> Time elapsed -  +3.859000E-003 seconds 
 
SQLGetData( rgbValue="" - x'', pcbValue=2527 ) 
     <--- SQL_SUCCESS_WITH_INFO Time elapsed - +7.118400E-002 
seconds 
 
SQLGetData( hStmt=1:2, iCol=1,fCType=SQL_C_CHAR, 
rgbValue=&00e1d45b, cbValueMax=0, 
pcbValue=&00e1d45c ) 
     ---> Time elapsed -  +6.944000E-003 seconds 
 
( Unretrieved error message="[IBM][CLI Driver] CLI0002W  Data 
truncated.SQLSTATE=01004" ) 
 
 SQLGetData( rgbValue="" - x'',pcbValue=2527 ) 
     <--- SQL_SUCCESS_WITH_INFO Time elapsed - +1.023330E-001 
seconds 
 
with real value of cbValueMax: 
SQLGetData( hStmt=1:2, iCol=1,fCType=SQL_C_CHAR, 
rgbValue=&01b24af0, cbValueMax=32768,pcbValue=&01a2aa98 ) 
      ---> Time elapsed - +8.312000E-003 seconds 
 ( Unretrieved error message="[IBM][CLI Driver] CLI0002W  Data 
truncated. SQLSTATE=01004" )
Problem Summary:
User's affected: All 
Problem summary: CLI BASED APPLICATION USING SQLGETDATA TO 
RETREIVE CLOB AGAINST NFM MAY HAVE EXTRA CHARACTERS.
Local Fix:
Remove the extra SQLGetData call.
available fix packs:
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

Solution
First fixed in v9.7 fp1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.07.2009
15.01.2010
15.01.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList