DB2 FOR LUW / DB2FORLUW / 970 - DB2

When issuing a manual takeover from the HADR standby, the 
command returns successfully and the standby db becomes the new 
primary. However, immediately afterwards, TSA initiates a second 
takeover request and switches the new primary db back to a 
standby. The reason for this behavior may be that a 
ClusterInitiatedMove resource flag was not cleaned up and still 
exists in /tmp from a previous TSA takeover operation. 
 
If this is the case, then the following db2diag.log message 
should be seen on the standby host at the time that the manual 
HADR takeover command was issued: 
 
2013-09-26-14.17.39.603232-240 E1930E465           LEVEL: Event 
PID     : 2510                 TID  : 47851748976960PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000          DB   : HADRDB 
APPHDL  : 0-15                 APPID: 
*LOCAL.db2inst1.130926181739 
AUTHID  : DB2USER1 
EDUID   : 554                  EDUNAME: db2agent (HADRDB) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDBMgr::StartUsingLocalDatabase, probe:13 
START   : Received TAKEOVER HADR command. 
 
Immediately after the above db2diag.log message, the following 
db2diag.log message should be seen: 
 
2013-09-26-14.17.41.260002-240 E2396E435           LEVEL: 
Warning 
PID     : 2510                 TID  : 47851748976960PROC : 
db2sysc 
INSTANCE: db2inst1             NODE : 000          DB   : HADRDB 
APPHDL  : 0-15                 APPID: 
*LOCAL.db2inst1.130926181739 
AUTHID  : DB2USER1 
EDUID   : 554                  EDUNAME: db2agent (HADRDB) 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaLockHADRResource, probe:181 
 
If this second db2diag.log message is not seen, then this issue 
is being hit. The cause is that the IBM.Test 
ClusterInitiatedMove resource flag was not properly cleaned up 
as part of a prior TSA automated HADR takeover.

**************************************************************** 
* USERS AFFECTED:                                              * 
* TSA automated HADR environment                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 FP11                                      * 
****************************************************************

In order to confirm whether or not this flag still exists, 
verify the output of the following commands: 
export CT_MANAGEMENT_SCOPE=2 
lsrsrc IBM.Test | grep ClusterInitiatedMove 
 
and: 
 
ls /tmp | grep ClusterInitiatedMove 
 
If the ClusterInitiatedMove flag resource or file exists, it 
will need to be manually removed. In order to remove the flag 
resource, run the following command as root: 
export CT_MANAGEMENT_SCOPE=2 
rmrsrc -s "Name like '%ClusterInitiatedMove%'" IBM.Test

keiner bekannt / siehe Local-Fix

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

23.01.2015
06.10.2015
15.01.2016

9.7.FP11