DB2 - Problem description
Problem IC62500 | Status: Closed |
INDPTR OF TYPE SQLLEN IS NOT REALLY RETURNING 64 BIT LENGTH. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users using IBM Data Server Client 9.5 on 64-bit * * WindowsServer. * **************************************************************** * PROBLEM DESCRIPTION: * * The issue is on the SQLLEN handling inside the ODBC * * driver.On Windows 64 BIT platform, DB2 64-bit ODBC * * drivermishandles the array of SQLLEN data as an array of * * 32-bitinteger rather than an array of 64-bit integer, so the * * DB2ODBC driver and database server would think that * * bindparameter is SQL_DATA_AT_EXEC type of bind parameter for * * thecase of batch insert, although none of the array * * bindparameter is in that type. * **************************************************************** * RECOMMENDATION: * * Apply FP5 to solve the issue. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
The issue is first fixed in FP5 of V9.5. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC62503 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.08.2009 23.02.2010 23.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.5.0.5 |