DB2 - Problembeschreibung
Problem IC69082 | Status: Geschlossen |
DEFAULT VALUE FOR AUTO_REVAL DATABASE CONFIGURATION PARAMETER IS INCORRECT ON BIG ENDIAN PLATFORMS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * 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. | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Problem first fixed in DB2 Version 9.7 Fix Pack 3 and all subsequent Fix Packs. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC69114 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 08.06.2010 16.09.2010 16.09.2010 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP3 | |
Problem behoben lt. FixList in der Version | |
9.7.0.3 | |
9.7.0.3 |