SAPHana resource stuck in "slave" state on both nodes of RHEL 6 for SAP HANA High Availability cluster with pacemaker, reporting "Dual primary detected" on one node

Solution Unverified - Updated -

Issue

  • We tried to start our SAP HANA cluster, but both nodes came up in "slave" state and never promoted to "master" or "primary"
  • SAPHana resource is reporting duplicate primary on one node
Sep 14 13:48:56 node2 SAPHana(rsc_SAPHana_PH1_HDB00)[29194]: INFO: LPA: Dual primary detected and AUTOMATED_REGISTER='false' ==> WAITING
Sep 14 13:48:56 node2 SAPHana(rsc_SAPHana_PH1_HDB00)[29194]: INFO: RA ==== end action monitor_clone with rc=0 (0.151.1) (8s)====
  • Should I set AUTOMATED_REGISTER in my SAPHana cluster?

Environment

  • Red Hat Enterprise Linux (RHEL) 6 for SAP HANA with the High Availability Add-On
  • pacemaker
  • One or more SAPHana multi-state (master/slave) resources

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.