DB2 FOR LUW / DB2FORLUW / B10 - DB2

In an automated HADR environment, it is possible that the "db2pd
-ha" command reports incorrect primary and secondary node values
for a HADR database. Take for example the following HADR
database 'HADRDB' which is currently primary on hostA and
standby on hostB:

db2inst1@hostA: $ db2pd -hadr -db HADRDB | grep HADR_ROLE
                            HADR_ROLE = PRIMARY

db2inst1@hostB: $ db2pd -hadr -db HADRDB | grep HADR_ROLE
                            HADR_ROLE = STANDBY

It is possible that the "db2pd -ha" command reports conflicting
information. Take for example the following snippet from the
"db2pd -ha" command which reports hostB as the primary and hostA
as the standby:

db2inst1@hostA: $ db2pd -ha
(...)
   Resource Name                  =
db2_db2inst1_db2inst1_HADRDB-rs
   Resource State                 = Online
   Resource Type                  = HADR
   HADR Primary Instance          = db2inst1
   HADR Secondary Instance        = db2inst1
   HADR DB Name                   = HADRDB
   HADR Primary Node              = hostB
   HADR Secondary Node            = hostA
(...)

In this case, the information reported by the "db2pd -ha"
command is incorrect and can be safely ignored. This issue can
happen as a result of a cluster(TSA) initiated takeover and has
no impact on database functionality and/or availability.

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher                *
****************************************************************

The incorrect primary and secondary HADR node values reported by
"db2pd -ha" can be safely ignored.

not known / see Local fix

forerunner  : IT19324 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

19.03.2018
27.11.2018
27.11.2018