DB2 - Problembeschreibung
Problem IC76381 | Status: Geschlossen |
SOME BOOLEAN TYPE OF DB2 CONFIGURATION PARAMETERS CAN ONLY ACCEPT EITHER YES/NO OR ON/OFF VALUES | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
A boolean type of database or database manager configuration parameter should accept all the values of [YES,NO,ON,OFF]. However, the following parameters can ONLY accept either YES/NO or ON/OFF values: db cfg parameters: AUTO_DB_BACKUP, AUTO_MAINT, AUTO_PROF_UPD, AUTO_REORG, AUTO_RUNSTATS, AUTO_STATS_PROF, AUTO_TBL_MAINT, AUTORESTART, BLK_LOG_DSK_FUL, DL_UPPER, INDEXSORT, SEQDETECT. dbm cfg parameters: CATALOG_NOAUTH, DATALINKS, DIR_CACHE, FEDERATED, INITDARI_JVM, INITFENCED_JVM, KEEPDARI, KEEPFENCED , DFT_MON_BUFPOOL, DFT_MON_LOCK, DFT_MON_SORT, DFT_MON_STMT, DFT_MON_TABLE, DFT_MON_TIMESTAMP , DFT_MON_UOW. The fix of this APAR will allow these parameters to accept all values of YES,NO,ON,OFF. This APAR also fixes the output values of the database configuration parameter TRACKMOD from the command "get db cfg" and the command "db2pd -dbcfg". The current output values are "NO/OFF", which will be changed to "YES/NO" so they are consistent with the range list [Yes,No] documented in the information center. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5 or newer * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in Version 9.7 Fix Pack 5 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 13.05.2011 19.01.2012 19.01.2012 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP5 | |
Problem behoben lt. FixList in der Version | |
9.7.0.5 |