DB2 FOR LUW / DB2FORLUW / A10 - 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                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2.                      * 
****************************************************************

change or update the CritRsrcProtMethod to 1 manually

DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in Version 10.1 Fix Pack 2.

keiner bekannt / siehe Local-Fix

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

28.11.2012
10.01.2013
10.01.2013