DB2 - Problem description
Problem IC70993 | Status: Closed |
HADR PRIMARY REINTEGRATION SHOULD NOT HAPPEN WHEN TSA IS IN MANUAL MODE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
In a HADR scenario normally when the primary fails, the standby will takeover by force. Then later on when primary comes back up, it should reintegrate to become new Standby. However, when TSA is in Manual mode, this means automation is disabled, and no action should be taken. But this is not the case right now. We perform reintegration at the monitor script, so even if TSA Manual mode is enabled, reintegration will still occur. This is not the desired effect because it is not honouring the TSA Manual mode. The expectation is that no automation (including reintegration) should occur when TSA is in Manual mode. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Integrated HA solution users where TSA is used as the * * cluster manager to automate HADR failover. * **************************************************************** * PROBLEM DESCRIPTION: * * In a HADR scenario normally when the primary fails, the * * standby will takeover by force. * * Then later on when primary comes back up, it should * * reintegrate to become new Standby. * * * * However, when TSA is in Manual mode, this means automation * * is disabled, and no action should be taken. But this is not * * the case right now. We perform reintegration at the monitor * * script, so even if TSA Manual mode is enabled, reintegration * * will still occur. * * * * This is not the desired effect because it is not honouring * * the TSA Manual mode. * * * * The expectation is that no automation (including * * reintegration) should occur when TSA is in Manual mode. * **************************************************************** * RECOMMENDATION: * * Apply DB2 V9.5 FixPak 7 * **************************************************************** | |
Local Fix: | |
Change the hadr_monitor script such that it checks whether TSA is in Manual mode. If in manual mode, then skip the db2gcf call and continue with the db2pd / snapshot checks. e.g. + manual=$(lssamctrl | grep -c "Manual") + if [[ $manual == 0 ]]; then + # Want db2gcf to timeout prior to the monitor method timeout ... gcfTimeOut=15 su - ${candidate_P_instance?} -c "$INSTHOME/sqllib/bin/db2gcf -t ${gcfTimeOut?} -s -i ${candidate_P_instance?} -i ${candidate_S_instance?} -h ${DB2HADRDBNAME?}" grc=$? # logger -i -p debug -t $0 "su - ${candidate_P_instance?} -c $INSTHOME/sqllib/bin/db2gcf -t ${gcfTimeOut?} -s -i ${candidate_P_instance?} -i ${candidate_S_instance?} -h ${DB2HADRDBNAME?} returns $grc" + else + grc=10 + fi | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
Apply DB2 V9.5 FixPak 7 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC71074 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.09.2010 12.10.2010 12.10.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.7 | |
9.5.0.7 |