Why `SAPHana` Slave reports `secondary with sync status FAILED ==> EXCLUDE as possible takeover` and failover of `SAPHana` Master doesn't happen?

Solution Unverified - Updated -

Issue

  • Node running SAPHana resource as Slave reports the following messages in logs and when the node running SAPHana Master is stopped the other node doesn't get promote to Master.

    SAPHana(SAPHana_RH2_02)[xxx]:  2018/05/01_00:01:47 INFO: RA ==== begin action monitor_clone (0.152.21) ====
SAPHana(SAPHana_RH2_02)[xxx]:  2018/05/01_00:01:53 INFO: DEC: secondary with sync status FAILED ==> EXCLUDE as possible takeover node
SAPHana(SAPHana_RH2_02)[xxx]:  2018/05/01_00:00:53 INFO: RA ==== end action monitor_clone with rc=0 (0.152.21) (7s)====

Environment

  • Red Hat Enterprise Linux 7 with High Availability Add-on
  • pacemaker cluster managing SAP HANA SR using SAPHana resource agent

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.