DB2 FOR LUW / DB2FORLUW / A10 - DB2

In the case where both HADR databases are in PEER and CONNECTED 
state, it is possible that the standby HADR resource, as seen in 
the "lssam" output, is in a "Failed offline" state as opposed to 
the expected "Offline" state. 
 
In this case, we are susceptible to an outage to the HADR 
primary database, and so the "Failed Offline" state must be 
cleared as soon as possible. 
 
Example: 
We have HADR database called "hadrdb", primary on host 
"db2host2" and standby on host "db2host1". 
 
lssam output: 
Online IBM.ResourceGroup:db2_db2inst1_db2inst1_HADRDB-rg 
Control=MemberInProblemState Nominal=Online 
        |- Online 
IBM.Application:db2_db2inst1_db2inst1_HADRDB-rs 
Control=MemberInProblemState 
                |- Failed offline 
IBM.Application:db2_db2inst1_db2inst1_HADRDB-rs:db2host1 
                '- Online 
IBM.Application:db2_db2inst1_db2inst1_HADRDB-rs:db2host2 
 
In the above example, we would clear the "Failed Offline" state 
by running the following commands as root from either host: 
 
export CT_MANAGEMENT_SCOPE=2 
resetrsrc -s "Name = 'db2_db2inst1_db2inst1_HADRDB-rs' && 
NodeNameList = {'db2host1'}" IBM.Application

**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v10.1 Fixpack 5 or Later.                 * 
****************************************************************

export CT_MANAGEMENT_SCOPE=2 
resetrsrc -s "Name = 'db2_db2inst1_db2inst1_HADRDB-rs' && 
NodeNameList = {'db2host1'}" IBM.Application

First Fixed in DB2 LUW v10.1 Fixpack 5.

not known / see Local fix

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

12.06.2014
13.07.2015
13.07.2015