|
Problem IT02522
|
Status: Closed |
IN A TSA/HADR ENVIRONMENT, THE STANDBY HADR RESOURCE MAY BE IN A FAILED OFFLINE STATE |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Platforms *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW v10.5 Fixpack 4 or Later. *
**************************************************************** |
| Local Fix: |
export CT_MANAGEMENT_SCOPE=2
resetrsrc -s "Name = 'db2_db2inst1_db2inst1_HADRDB-rs' &&
NodeNameList = {'db2host1'}" IBM.Application |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First Fixed in DB2 LUW v10.5 Fixpack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 13.06.2014
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
