DB2 - Problem description
Problem IC68988 | Status: Closed |
DB2IUPDT COMMAND WILL RESET THE DIAGSIZE VALUES BACK TO 0 | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 * **************************************************************** * 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.7FP3 or higher * **************************************************************** | |
Local Fix: | |
Workaround: Update the DIAGSIZE after performing the db2iupdt: db2 update dbm cfg using DIAGSIZE 50 | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 v9.7FP3 or higher | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC69126 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.06.2010 22.03.2011 22.03.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |