|
Problem IC69126
|
Status: Closed |
DB2IUPDT COMMAND WILL RESET THE DIAGSIZE VALUES BACK TO 0 |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
During the db2iupdt of an instance the DIAGSIZE database manager
configuration (DBM) parameter will be reset back to 0.
Reproduction:
db2start
db2 update dbm cfg using DIAGSIZE 50
db2 get dbm cfg |grep DIAGSIZE
Size of rotating db2diag & notify logs (MB) (DIAGSIZE) = 50
db2stop
db2iupdt udb971
db2start
db2 get dbm cfg |grep DIAGSIZE
Size of rotating db2diag & notify logs (MB) (DIAGSIZE) = 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* During the db2iupdt of an instance the DIAGSIZE database *
* manager *
* configuration (DBM) parameter will be reset back to 0. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.8FP4 or higher *
**************************************************************** |
| Local Fix: |
Workaround:
Update the DIAGSIZE after performing the db2iupdt:
db2 update dbm cfg using DIAGSIZE 50 |
| Solution |
First Fixed in DB2 v9.8FP4 or higher |
| Workaround |
not known / see Local fix |
| Comment |
This APAR was created in error via a script. If this APAR is
actually needed then please reopen it. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.06.2010
08.08.2011
08.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
