DB2 FOR LUW / DB2FORLUW / A10 - DB2

In the case where a manual HADR takeover is issued by running 
the "db2 takeover hadr on db <dbname>" command from the standby 
host and it is successful. It is possible that TSA initiates an 
automated HADR takeover immediately after the fact, switching 
the HADR standby and primary back to their original locations 
and leaving them in a disconnected state. 
 
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. 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: 
 
rmrsrc -s "Name like '%ClusterInitiatedMove%'" IBM.Test

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 HADR users in TSA Automated Environment                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW 10.1 Fix Pack 4 or greater                * 
****************************************************************

Run the following as root and retry the takeover: 
rmrsrc -s "Name like '%ClusterInitiatedMove%'" IBM.Test

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem first fixed in DB2 LUW 10.1 Fix Pack 4

keiner bekannt / siehe Local-Fix

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

08.10.2013
02.06.2014
23.07.2014