DB2 - Problem description
Problem IC86014 | Status: Closed |
INCORRECT MESSAGE IS DISPLAYED WHEN 'DB2 UPDATE DBM CFG ' IS ISSUED WITHOUT ATTACHING TO INSTANCE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 users below DB2 v97fp8 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v97fp8 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
Problem fixed in DB2 v97fp8 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC91759 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.08.2012 05.04.2013 05.04.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |