DB2 FOR LUW / DB2FORLUW / A50 - DB2

In certain situations the old primary database may not 
automatically reintegrate as the standby after running db2haicu 
maintenance mode option 5 to move HADR databases for scheduled 
maintenance. 
 
Before the "START HADR AS STANDBY" command is received by the 
db, there is an application connecting to the db which is 
driving database activation: 
 
2015-07-16-12.19.39.582447+120 I704901E564           LEVEL: Info 
PID     : 11404                TID : 140233223956224 PROC : 
db2sysc 
INSTANCE: xxxxxx            NODE : 000            DB   : xxxxxx 
APPHDL  : 0-321                APPID: xxxx 
AUTHID  : xxxxx               HOSTNAME: xxxxxx 
EDUID   : 128                  EDUNAME: db2agent (xxxx) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeLocalDatabase::FirstConnect, probe:7233 
MESSAGE : The database passed the SD-compatibility check 
DATA #1 : Boolean, 1 bytes 
true 
 
2015-07-16-12.19.39.625846+120 E732052E523           LEVEL: 
Event 
PID     : 11404                TID : 140231776921344 PROC : 
db2sysc 
INSTANCE: xxxx             NODE : 000            DB   : xxxx 
APPHDL  : 0-327                APPID: *LOCAL.xxx 
AUTHID  : xxxx             HOSTNAME: xxxx 
EDUID   : 167                  EDUNAME: db2agent (xxx) 
FUNCTION: DB2 UDB, base sys utilities, 
sqeDBMgr::StartUsingLocalDatabase, probe:13 
START   : Received START HADR SECONDARY command. 
 
If the instance is restarted in the middle of this, the 
reintegration flag might get cleared and as a result the 
database will not be automatically started as the standby. This 
is not a split-brain. The database can be manually started back 
up as the standby. Any attempts to activate the database will 
fail with sqlcode SQL1768N reason code 7. 
 
This APAR will make the reintegration logic more robust 
to explicitly check that the database role has been changed to 
standby before the reintegration flag is deleted.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 and Fix Pack 7                   * 
****************************************************************

Manually start the HADR database as standby via the "START HADR 
AS STANDBY" command.

Problem was first fixed in DB2 Version 10.5 and Fix Pack 7

keiner bekannt / siehe Local-Fix

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

10.08.2015
20.01.2016
20.01.2016