Neueste VersionenFixList
11.1.0.7 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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC69126 Status: Geschlossen

DB2IUPDT COMMAND WILL RESET THE DIAGSIZE VALUES BACK TO 0

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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
Lösung
First Fixed in DB2 v9.8FP4 or higher
Workaround
keiner bekannt / siehe Local-Fix
Kommentar
This APAR was created in error via a script.  If this APAR is 
actually needed then please reopen it.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.06.2010
08.08.2011
08.08.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP4
Problem behoben lt. FixList in der Version