DB2 - Problem description
Problem IC70864 | Status: Closed |
ENHANCE "DB2HAICU -DELETE" TO REMOVE ANY LEFTOVER PEERNODE EQUIVALENCIES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * High Availability customers * **************************************************************** * PROBLEM DESCRIPTION: * * ENHANCE "DB2HAICU -DELETE" TO REMOVE ANY LEFTOVER PEERNODE * * EQUIVALENCIES * **************************************************************** * RECOMMENDATION: * * Upgrade to 9.7 FP4 * **************************************************************** | |
Local Fix: | |
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>%' " | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
ENHANCE "DB2HAICU -DELETE" TO REMOVE ANY LEFTOVER PEERNODE EQUIVALENCIES | |
Workaround | |
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>%' " | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC73736 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.08.2010 12.05.2011 12.05.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP4 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.4 |