DB2 - Problem description
Problem IC64845 | Status: Closed |
UNEXPECTED SQLCODE RETURNED FROM API DB2GETROWPARTNUM AND DB2GETDISTMAP DUE TO NOT INITIALIZED SQLCA. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Calling API db2GetRowPartNum and db2GetDistMap will probably result in unexpected sqlcode, since they do not initialize sqlca. The initialization is being done in a separate functions which aren't being called since db2 LUW v9.7. The fix is to move the initialization code in db2GetRowPartNum and db2GetDistMap. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL. * **************************************************************** * PROBLEM DESCRIPTION: * * Calling API db2GetRowPartNum and db2GetDistMap will probably * * result in unexpected sqlcode, since they do not initialize * * sqlca. * * * * The initialization is being done in a separate functions * * which * * aren't being called since db2 LUW v9.7. * * * * The fix is to move the initialization code in * * db2GetRowPartNum * * and db2GetDistMap. * **************************************************************** * RECOMMENDATION: * * Update to version 9.7 fix pack 2 or later. * **************************************************************** | |
Local Fix: | |
Initialize sqlca explicitly before calling db2GetRowPartNum or db2GetDistMap in application, for example, memsetting the struct sqlca with \0. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
This problem is first fixed in version 9.7 fix pack 2. | |
Workaround | |
Initialize sqlca explicitly before calling db2GetRowPartNum or db2GetDistMap in application, for example, memsetting the struct sqlca with \0. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67222 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.11.2009 25.05.2010 25.05.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP2 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |