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 IT05815 Status: Geschlossen

FAILED OFFLINE FIXPACK INSTALLATION WITH ERROR DBI1572E

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When performing offline fixpack update, the following error 
might cause the installation to fail : 
DBI1572E  The fix  pack update operation failed because the DB2 
member is involved in a  restart light process.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2 Purescale Cluster                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to the next Fixpack DB210.5 FP6                      * 
****************************************************************
Local-Fix:
Issue db2instance -list to determine which member is in Restart 
Light mode. This must be resolved before proceeding. Once The 
member is no longer in Restart Light mode and running on its 
home host, issue the following commands for that member : 
 
db2ALmanager -remove <member id> -offline -instance <instance 
name> 
db2ALmanager -add <member-id> -offline -instance <instance name> 
 
Then re-issue the Offline Fixpack Update.
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
27.11.2014
10.10.2017
10.10.2017
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList