|
Problem IT18546
|
Status: Closed |
IN AN AUTOMATED HADR(TSA) ENVIRONMENT, THE HADR RESOURCE GROUP'SEXCLUDED LIST ATTRIBUTE MAY REMAIN SET FOLLOWING A FAILOVER |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The "ExcludedList" attribute of a HADR resource group(RG) is set
by the DB2 engine during a "controlled" (user initiated)
takeover operation. At the end of takeover processing, the DB2
engine clears the "ExcludedList" attribute.
It is possible that the "ExcludedList" attribute is not cleared
at the end of takeover processing. This APAR fix adds additional
db2diag logging when setting and unsetting the "ExcludedList"
attribute in an effort to catch issues around improperly setting
and/or unsetting this attribute's value. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 10.5 Fix Pack 9 or higher *
**************************************************************** |
| Local Fix: |
Manually clear the RG's excluded list by issuing the following
command as root:
chrg -u d -x <hostname> <RGname> |
| Solution |
First fixed in Db2 10.5 Fix Pack 9 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.12.2016
29.09.2017
29.09.2017 |
| Problem solved at the following versions (IBM BugInfos) |
9.0.
|
| Problem solved according to the fixlist(s) of the following version(s) |
