home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC76381 Status: Closed

SOME BOOLEAN TYPE OF DB2 CONFIGURATION PARAMETERS CAN ONLY ACCEPT EITHER
YES/NO OR ON/OFF VALUES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5 or newer               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in Version 9.7 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.05.2011
19.01.2012
19.01.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 FixList