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 IC84484 Status: Closed

INCONSISTENCIES BETWEEN DB2PD DBCFG/DBMCFG OUTPUTS AND GET DB/DBM CFG
OUTPUTS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
There are several inconsistencies in the way that the db2pd 
command displays values from: 
   db2pd -dbcfg and -dbmcfg 
in comparison to the output from 
   db2 get db cfg and db2 get dbm cfg 
 
The main things addressed in this APAR are: 
 
1) Incorrect values are shown for AUTO_REVAL 
when using db2pd command. 
db2pd will show IMMEDIATE while get db cfg shows DEFERRED. 
 
Example: 
Reproduction using the sample database: 
 
$> db2pd -db sample -dbcfg | grep AUTO_REV 
 AUTO_REVAL           IMMEDIATE            IMMEDIATE 
 
$> db2 get db cfg for sample | grep AUTO_REV 
 Auto-Revalidation          (AUTO_REVAL) = DEFERRED 
 
2) db2pd would missing the COMPUTED flag here: 
 
$> db2 get db cfg for sample | grep DATABASE_MEMORY 
 Size of database shared memory (4KB)  (DATABASE_MEMORY) = 
COMPUTED (928000) 
 
$> db2pd -db sample -dbcfg | grep DATABASE_MEMORY 
DATABASE_MEMORY (4KB)          928000               928000 
 
3) Incorrect values are shown for DISCOVER_DB 
when using db2pd command. 
db2pd will show ENABLE while get db cfg shows DISABLE. 
 
Example: 
 
$> db2pd -db sample -dbcfg | grep DISCOVER 
DISCOVER_DB           ENABLE               ENABLE 
 
$> db2 get db cfg for sample show detail | grep DISCOVER 
 Discovery support for this database       (DISCOVER_DB) = 
DISABLE                    DISABLE 
 
 
This APAR will resolve these inconsistencies from 
the db2pd output.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
07.11.2012
07.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList