SAP Knowledge Base Article - Preview

3715717 - Pacemaker shows SAPHanaSR monitor rc=7 (not running) on secondary although SAP HANA System Replication is ACTIVE and fully synchronized

Symptom

In an SAP HANA system using the Pacemaker/SAPHanaSR high-availability integration, the cluster reports a monitor status “not running” for the secondary resource similar to:

rsc_SAPHana_<SID>_HDB<NR>_monitor_* on <secondary> 'not running' (rc=7)

crm_mon or crm status shows a fail-count and a last-failure timestamp for the secondary resource.

At the same time, SAP HANA tools report a healthy replication state:

  • HDBSettings.sh systemReplicationStatus.py reports ACTIVE and Fully Synced = True
  • hdbnsutil -sr_state reports primary/secondary in sync (logreplay/sync)
  • landscapeHostConfiguration.py reports overall host status: ok

The database services are reported as running by the SAP HANA status checks.

In some situations the message may no longer appear after a server restart, although no SAP HANA configuration change was performed.


Read more...

Environment

SAP HANA DB Version 2.0

Product

SAP HANA, platform edition 2.0

Keywords

SAPHanaSR, Pacemaker, rc=7, fail-count, systemReplicationStatus , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.