|
Problem IT05127
|
Status: Closed |
In a DB2 HA DPF environment, partition numbers 997, 998 and 999 are unable to failover between systems. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In a DB2 HA DPF environment, partition numbers 997, 998 and 999
are unable to failover between systems. For example, take the
following DPF environment as shown by this db2nodes.cfg file:
$ cat /db2home/instance/sqllib/db2nodes.cfg
0 ceha04 0
1 ceha04 1
2 ceha04 2
999 ceha04 3
and the lssam output looking as follows for the partition #999
resource group:
Online IBM.ResourceGroup:db2_pstedman_999-rg Nominal=Online
'- Online IBM.Application:db2_pstedman_999-rs
|- Offline
IBM.Application:db2_pstedman_999-rs:ceha03
'- Online
IBM.Application:db2_pstedman_999-rs:ceha04
Issuing the "rgreq -o move db2_pstedman_999-rg" command as root
to failover partition #999 from node ceha04 to ceha03 results in
the following lssam output:
Online IBM.ResourceGroup:db2_pstedman_999-rg Nominal=Online
'- Online IBM.Application:db2_pstedman_999-rs
|- Pending online
IBM.Application:db2_pstedman_999-rs:ceha03
'- Online
IBM.Application:db2_pstedman_999-rs:ceha04
The result is that partition # 999 continues to run on host
ceha04 and eventually the resources are displayed as follows:
Online IBM.ResourceGroup:db2_pstedman_999-rg
Control=MemberInProblemState Nominal=Online
'- Online IBM.Application:db2_pstedman_999-rs
Control=MemberInProblemState
|- Offline
IBM.Application:db2_pstedman_999-rs:ceha03
'- Online
IBM.Application:db2_pstedman_999-rs:ceha04 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* System running DB2 v10.1 FP4 or lower *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.1 FP5 or higher *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
Fixed in DB2 v10.1 FP5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.10.2014
27.08.2015
27.08.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
