|
Problem IC63979
|
Status: Closed |
DB2PD -DBCFG AND GET DB CFG SHOW DIFFERENT AND INCORRECT OUTPUT FOR CURRENT AND DELAYED LOGFILSIZ AND LOGSECOND |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Iconsistent information about current and delayed values for
LOGFILSIZ and LOGSECOND can be reported by the following
commands:
* db2pd -db <dbname> -dbcfg
* db2 get db cfg for <dbname> show detail
The problem can be reproduced with the following steps in a
HADR environment:
* Change LOGFILSIZ and LOGSECOND in the standby db cfg
* Deactivate/activate standby db to make changes current
* Takeover HADR
* Standby db, now primary, will report inconsistent information
This is a continuation of APAR IZ38381. |
| Problem Summary: |
USERS AFFECTED:
All
PROBLEM DESCRIPTION:
See ERROR DESCRIPTION
PROBLEM SUMMARY:
See ERROR DESCRIPTION |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 UDB Version 9.7, FixPak 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.10.2009
15.12.2009
15.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
