SE75136 - OSP-OTHER-F/RMSLLOCKCHECK-T/QCSTIDX-MSGMCH2601 MCH2601 LOCK
ENFORCEMENT RULES BROKEN WHEN TRYING TO ACCESS OBJECT QCSTCRGMIX

APAR (Authorized Program Analysis Report)

Abstract

OSP-OTHER-F/RMSLLOCKCHECK-T/QCSTIDX-MSGMCH2601 MCH2601 LOCK
ENFORCEMENT RULES BROKEN WHEN TRYING TO ACCESS OBJECT QCSTCRGMIX

Error Description

A message MCH2601 - "Lock enforcement rules broken when trying  
to access object QCSTCRGMIX" could be encountered in a device  
CRG's joblog if there is a save operation (usually involving    
SAVCFG) at the precise time that PowerHA is attempting to      
perform a HealthCheck of the replication environment from the  
replication target node. When this situation happens, it causes
the CRG job to end with errors, which triggers a failover event
to occur and the IASP is instructed to vary off by job          
QCSTVRYDEV.                                                    
                                                               
Code will be enhanced such that when the MCH2601 is            
encountered, there will be a delay and retry in order to obtain
the lock and avoid causing failover.                            
                                                               
To avoid encountering this situation, if doing save operations  
on a cluster node, the node should be an Inactive member of the
cluster.  If the save is on a source node in the cluster, end  
any device CRGs and then ent the cluster node.  If the save is  
on a target node in the cluster, end the cluster node.          

Problem Summary

A message MCH2601 - "Lock enforcement rules broken when trying  
to access object QCSTCRGMIX" could be encountered in a device  
CRG's joblog if there is a save operation (usually involving    
SAVCFG) at the precise time that PowerHA is attempting to      
perform a HealthCheck of the replication environment from the  
replication target node. When this situation happens, it causes
the CRG job to end with errors, which triggers a failover event
to occur and the IASP is instructed to vary off by job          
QCSTVRYDEV.                                                    
                                                               
Code will be enhanced such that when the MCH2601 is encountered,
there will be a delay and retry in order to obtain the lock and
avoid causing failover.                                        
                                                               
Additionally at R740, HA Policy QCST_CRG_CANCEL_FAILOVER set up
against the Device CRG would also prevent the IASP from varying
off and failover being triggered.                              

Problem Conclusion

Cluster code now detects if a save operation is in progress when
accessing the QCSTCRGMIX object and will retry the operation. If
the operation continues to fail, then the cluster node will    
continue to end but a failover or vary off of an IASP on the    
node will not occur.                                            

Temporary Fix

Comments

Circumvention

PTFs Available

R720 SI78581  1000

R730 SI79856  1000

R740 SI78004  2125

R750 SI78084  2104

Affected Modules

Affected Publications

Summary Information

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, 2018, 2019, 2020, 2021, 2022 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