|
Problem IC86055
|
Status: Closed |
DB2 TSA SETUP SAMPLE FOR WINDOWS (MKHADR) DEFINE "CRITRSRCPROTMETHOD=5" WHICH IS INCORRECT |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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}
... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL USERS ON WINDOWS PLATFORM *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 9.7 Fix Pack 8 *
**************************************************************** |
| Local Fix: |
change or update the CritRsrcProtMethod to 1 manually |
| available fix packs: |
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
|
| Solution |
First fixed in DB2 UDB Version 9.7 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC88677
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.08.2012
08.04.2013
08.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
