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

SQLGETDIAGFIELDW RETURNS INCORRECT VALUE FOR PCBDIAGINFO

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
The CLI unicode function SQLGetDiagFieldW() returns an incorrect 
size for the error message : 
 
SQLGetDiagFieldW( pDiagInfo="[IBM][CLI Driver] CLI0100E  Wrong 
number of parameters. SQLSTATE=07001", pcbDiagInfo=140 ) 
=> pcbDiagInfo is set to 140 
If should be 70 : 
SQLGetDiagFieldW( pDiagInfo="[IBM][CLI Driver] CLI0100E  Wrong 
number of parameters. SQLSTATE=07001", pcbDiagInfo=70 )
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI applications                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP2 or later                             * 
****************************************************************
Local Fix:
N/A
available fix packs:
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

Solution
The problem is first fixed in DB2 10.1 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.11.2012
11.02.2013
11.02.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList