DB2 FOR LUW / DB2FORLUW / 970 - DB2

If db2haicu previously failed at the point where it was trying 
to create a resource for the DB2 instance, you can be left with 
a PeerNode equivalency. This will interfere with any further 
cluster setup. db2haicu -delete will not be able to remove this 
equivalency. 
 
This APAR will enhance "db2haicu -delete" to remove PeerNode 
equivalencies should it come across any.

**************************************************************** 
* USERS AFFECTED:                                              * 
* High Availability customers                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ENHANCE "DB2HAICU -DELETE" TO REMOVE ANY LEFTOVER PEERNODE   * 
* EQUIVALENCIES                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 9.7 FP4                                           * 
****************************************************************

The following TSA command can be used to manually remove the 
equivalencies specific to a particular DB2 instance: 
 
rmequ -s "Name like 'db2_<instance_name>%' "

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

ENHANCE "DB2HAICU -DELETE" TO REMOVE ANY LEFTOVER PEERNODE 
 
EQUIVALENCIES

The following TSA command can be used to manually remove the 
equivalencies specific to a particular DB2 instance: 
 
rmequ -s "Name like 'db2_<instance_name>%' "

Vorgänger  : APAR is sysrouted TO one or more of the following: IC73736 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

31.08.2010
12.05.2011
12.05.2011

9.7.FP4