DB2 - Problem description
Problem IC69082 | Status: Closed |
DEFAULT VALUE FOR AUTO_REVAL DATABASE CONFIGURATION PARAMETER IS INCORRECT ON BIG ENDIAN PLATFORMS | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
On big-endian platforms, the default value for the AUTO_REVAL database configuration parameter retrieved via the db2GetCfg API is incorrect. Precisely, you only get the invalid value when calling the db2GetCfg API for the AUTO_REVAL parameter, specifying the db2CfgGetDefaults flag. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 Version 9.7 GA through to Fix Pack 2 servers, on * * big-endian platforms using the db2GetCfg API with the * * db2CfgGetDefaults flag set. * **************************************************************** * PROBLEM DESCRIPTION: * * Incorrect assignment of the default value for the AUTO_REVAL * * database configuration parameter leads to the API returning * * the incorrect value for big-endian platforms. * **************************************************************** * RECOMMENDATION: * * Apply DB2 Version 9.7 Fix Pack 3 or refer to the constant * * defined for the default value directly. Namely, refer to * * SQLF_AUTO_REVAL_DEFERRED as defined in sqlutil.h * **************************************************************** | |
Local Fix: | |
There is no workaround when using the API, however, the default value is SQLF_AUTO_REVAL_DEFERRED defined in sqlutil.h. Hence, use the constant itself for referencing the default value. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem first fixed in DB2 Version 9.7 Fix Pack 3 and all subsequent Fix Packs. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69114 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.06.2010 16.09.2010 16.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |