home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT05815 Status: Closed

FAILED OFFLINE FIXPACK INSTALLATION WITH ERROR DBI1572E

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.11.2014
10.10.2017
10.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList