home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC81749 Status: Geschlossen

DB2CLUSTER -CM -ENTER -MAINTENANCE -ALL COMMAND MAY FAIL, BUT DOMAIN MAY
BECOME OFFLINE AFTER THE ERROR MESSAGE.

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
"db2cluster -cm -enter -maintenance -all" command may fail with 
an error message when 
the domain does not become offline for a certain period of time 
after the command has been given. 
The domain can still  become offline after the error message. 
 
 
# db2cluster -cm -enter -maintenance -all 
The domain has been unable to enter maintenance mode. 
A diagnostic log has been saved to 
'/tmp/ibm.db2.cluster.--xxxx'.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.8 FixPack 5                             * 
****************************************************************
Local-Fix:
Workaround: 
Make sure that the cluster is in the correct state by issuing 
"db2cluster -cm -verify -maintenance" on all hosts
Lösung
Problem was first fixed in DB2 UDB Version 9.8 FixPack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.03.2012
14.06.2012
14.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP5
Problem behoben lt. FixList in der Version
9.8.0.5 FixList