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

INCORRECT MESSAGE IS DISPLAYED WHEN 'DB2 UPDATE DBM CFG ' IS
ISSUED WITHOUT ATTACHING TO INSTANCE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If you attach to the instance before executing 'UPDATE DBM CFG' 
for an online configurable parameter (like DIAGLEVEL), then it 
will be active directly. You get message as below : 
 
$db2 update dbm cfg using DIAGLEVEL 4 
"DB20000I  The UPDATE DATABASE MANAGER CONFIGURATION command 
completed successfully." 
 
But if you don't have an instance attachment, the parameter is 
not changed online and immediately. But still you get same 
message as above (i.e. DB20000I ). Here is a sample of it : 
 
--------------------------------------------------- 
 
login: db2inst 
db2inst's Password: 
 
$ db2 update dbm cfg using DIAGLEVEL 4 
DB20000I  The UPDATE DATABASE MANAGER CONFIGURATION command 
completed 
successfully. 
$ db2 attach to db2inst 
 
   Instance Attachment Information 
 
 Instance server        = DB2/AIX64 9.7.6 
 Authorization ID       = db2inst 
 Local instance alias   = db2inst 
 
$ db2 GET DBM CFG SHOW DETAIL | grep DIAGLEVEL 
 Diagnostic error capture level              (DIAGLEVEL) = 2 
4 
$ 
 
--------------------------------------------------- 
 
See that, at this point the parameter value is not yet active. 
So DB2 should give a message other than DB20000I informing that 
the value is delayed and is not updated dynamically.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V101 FP3                                      * 
****************************************************************
Local Fix:
available fix packs:
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
DB2 V101 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
10.03.2015
10.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList