DB2 FOR LUW / DB2FORLUW / 970 - DB2

The TSA policy in the sample setup scripts that are shipped with 
DB2 9.7 define "CritRsrcProtMethod=5" which is incorrect. 
It should define "CritRsrcProtMethod=1" instead. 
 
This is a on Windows platform only. 
 
In an error situation this can cause a node to not to reboot 
which may cause further issues like a duplicate IP-address 
assigned and an unavailable HADR database. 
 
The setup script under <install>\samples\tsa\mkhadr does the 
following: 
 
... 
echo "Making relationships ..." 
lsrsrc IBM.TieBreaker 
lsrsrc -c IBM.PeerNode 
chrsrc -c IBM.PeerNode OpQuorumTieBreaker="mynetworktb" 
chrsrc -c IBM.PeerNode CritRsrcProtMethod=5    <<< 
lsrsrc -c IBM.PeerNode 
rgreq -o lock ${RGNAME} 
...

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS ON WINDOWS PLATFORM                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 Fix Pack 8                    * 
****************************************************************

change or update the CritRsrcProtMethod to 1 manually

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
 

First fixed in DB2 UDB Version 9.7 Fix Pack 8

keiner bekannt / siehe Local-Fix

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

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

22.08.2012
08.04.2013
08.04.2013

9.7.FP8