DB2 FOR LUW / DB2FORLUW / 970 - DB2

Problem that we have seen is that the windows cluster resource 
group appears to be very unstable and can cause the cluster 
administrator to fail and no longer work. As a result the entire 
ms cluster\s fail. 
 
All that is needed is to create a new resource using the 'DB2 
Server' resource type in an already predefined cluster group. 
The name of the resource needs to be an invalid instance name. 
Upon pressing next you will be notified that the instance does 
not exist. If you press ok to abort, it appears to create the 
definition and expects the instance to exist. Since the instance 
does not exist, it crashes the ms cluster and any restart fails. 
The only method I've found so far to resolve this is to create 
the instance that was in error and allow the ms cluster to 
restart. Once started you can then delete the offending 
resources.

ADDING AN INVALID MSCS DB2 RESOURCE CAUSES THE CLUSTER 
ADMINISTRATOR TO FAILS.

Workaround: Create the an instance for the problem resource and 
can then look to drop resource & then instance.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 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 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 9.7 Fix Pack 2

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

23.11.2009
17.05.2010
17.05.2010

9.7.FP2