DB2 - Problem description
| Problem IC88677 | Status: Closed |
DB2 TSA SETUP SAMPLE FOR WINDOWS (MKHADR) DEFINE "CRITRSRCPROTMETHOD=5" WHICH IS INCORRECT | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - 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 * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 2. * **************************************************************** | |
| Local Fix: | |
change or update the CritRsrcProtMethod to 1 manually | |
| available fix packs: | |
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows | |
| Solution | |
First fixed in Version 10.1 Fix Pack 2. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.11.2012 10.01.2013 10.01.2013 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.2 |
|
| 10.5.0.2 |
|