Latest versionsfixlist
11.1.0.6 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
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC83118 Status: Closed

"GET DATABASE CONFIGURATION" COMMAND DISPLAYS INCORRECT VALUE FOR
PARAMETER MIRRORLOGPATH.

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
If you change value for configuration parameter MIRRORLOGPATH 
for an active database, you will receive following message: 
============================================ 
DB20000I  The UPDATE DATABASE CONFIGURATION command completed 
successfully. 
SQL1363W  One or more of the parameters submitted for immediate 
modification 
were not changed dynamically. For these configuration 
parameters, all 
applications must disconnect from this database before the 
changes become 
effective. 
============================================ 
which tells you that you need to deactivate the database and 
reactivate it to have the change take effect. 
 
However after you deactivate the database and reactivate it, you 
would see the "get database configuration" command has incorrect 
output: the value on column "Current Value" is wrongly set to 
NULL for MIRRORLOGPATH, while the column "Delayed Value" has 
correct value. 
In "db2pd -dbcfg" output you would see similar problem: the 
value of "MIRRORLOGPATH (memory)" is wrongly set to NULL, while 
the value of "MIRRORLOGPATH (disk)" is correct. 
 
The change on MIRRORLOGPATH actually have taken effect after you 
reactivate the database, which means you would see log files 
created in the new mirror log path. 
The only problem is the incorrect value in "get database 
configuration" output and "db2pd -dbcfg" output.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.5 on Linux, Unix and Windows          * 
* platforms.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to DB2 LUW Version 9.5 Fix Pack 10 or higher levels.  * 
****************************************************************
Local Fix:
There are 2 means that help you see the correct value for 
parameter MIRRORLOGPATH: 
 
1. Recycle the DB2 instance by "db2stop" command and "db2start" 
command, and then you would see the correct value. 
 
2. Deactivate and reactivate the database *twice*, then after 
you reactivate the database for the 2nd time you would see the 
correct value.
Solution
First fixed in DB2 LUW Version 9.5 Fix Pack 10.
Workaround
There are 2 means that help you see the correct value for 
parameter MIRRORLOGPATH: 
 
1. Recycle the DB2 instance by "db2stop" command and "db2start" 
command, and then you would see the correct value. 
 
2. Deactivate and reactivate the database *twice*, then after 
you reactivate the database for the 2nd time you would see the 
correct value.
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC83910 IC87884 IC97520 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2012
22.08.2012
22.08.2012
Problem solved at the following versions (IBM BugInfos)
9.5.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.