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

INDPTR OF TYPE SQLLEN IS NOT REALLY RETURNING 64 BIT LENGTH.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The issue is on the SQLLEN handling inside the ODBC driver, On 
Windows 64 BIT platform, there is a mishandling in DB2 64-bit 
ODBC driver that it treats the array of 
SQLLEN data as an array of 32-bit integer rather than an  array 
of 64-bit integer, so the DB2 ODBC driver and database server 
would think that bind parameter is SQL_DATA_AT_EXEC type of bind 
parameter for the case of batch insert, although none of the 
array bind parameter is in that type
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using IBM Data Server Client 9.5 on 64-bit Windows * 
* Server.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The issue is on the SQLLEN handling inside the ODBC driver.  * 
* On Windows 64 BIT platform, DB2 64-bit ODBC driver           * 
* mishandles the array of SQLLEN data as an array of 32-bit    * 
* integer rather than an array of 64-bit integer, so the DB2   * 
* ODBC driver and database server would think that bind        * 
* parameter is SQL_DATA_AT_EXEC type of bind parameter for the * 
* case of batch insert, although none of the array bind        * 
* parameter is in that type.                                   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply FP5 to solve the issue.                                * 
****************************************************************
Local Fix:
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
The issue is first fixed in FP5 of V9.5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.08.2009
18.02.2010
18.02.2010
Problem solved at the following versions (IBM BugInfos)
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList