Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
APAR (Authorized Program Analysis Report) |
Abstract
MSGCPFBB17 CHGCRG CAN NOT SWITCH TO BACKUP BECAUSE CLUSTER IS
PARTITIONED.
Error Description
CHGCRG fails because the CRG is in a false partition. The
primary had crashed, causing a partition. The backup node was
ended, then re-started and change cluster node status called to
change the primary to failed. The CHGCRG to make the backup the
new primary fails with CPFBB17, cluster is partitioned.
The problem is when the backup node joined, since it was the
first node in the cluster, it only created an ack index entry
for work thread 1, even thogh both work threads are created.
Change cluster node status fails because it can't change the
index entry for work thread 2.
Problem Summary
Before the CHGCRG, a change cluster node status from partition
to fail was done. The CRG node status for the partitioned node
was not changed to fail
Problem Conclusion
The CRG code was changed to correctly handle the situation.
Temporary Fix
Comments
Circumvention
PTFs Available
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 5770SS100SI6 |
Failing Module.......................... | RCHMGR |
Reported Release................... | R710 |
Duplicate Of.............................. |
System i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
06 September 2017