DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* TSA/HADR solution users                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Same as error description                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Apply DB2 V9.7.0.4                                           * 
****************************************************************

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

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 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
 

Apply DB2 V9.7.0.4

keiner bekannt / siehe Local-Fix

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

10.09.2010
24.01.2011
24.01.2011

9.7.0.4