Secondary node does not get promoted after SAP HANA binaries are lost on the primary node in a High Availability cluster

Solution In Progress - Updated -

Issue

  • HANA is in stopped state on both nodes of a Pacemaker cluster after losing the hdb binaries on the primary node.
  • When the cluster is in maintenance mode, HANA continues to run on both nodes after the hdb binaries are removed from one node. When the cluster is not in maintenance mode, the SAPHana resource agent takes action to stop the HANA instances.

Environment

  • Red Hat Enterprise Linux 7 for SAP HANA (with the High Availability Add-on)

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