SAP Knowledge Base Article - Preview

3756821 - Primary database went down automatically and system failed over with no visible caused

Symptom

Primary database went down automatically and the system switched over to the secondary database; 

There is not visible symptom in the trace files: i.e. nameserver, indexserver, daemon, var/log/messages 

In the  /var/log/messages you can see HANA checks are happening regularly with no issues reported (rc=0), but there is a "demote request" close to the time of the issue just milliseconds after a monitoring check finishes with no alerts:

---

202X-xx-02T11:08:34.811420+ ...node1... SAPHanaTopology(rsc_SAPHanaTopology_<SID>_HDB<instance>)[PID]: INFO: RA ==== end action monitor_clone with rc=0 (0.162.5) (577s)====

...
...

202X-xx-02T11:08:34.824093+ node1 pacemaker-controld[PID]: notice: Requesting local execution of demote operation for rsc_SAPHana_<SID>_HDB<instance> on ...node1

---


Read more...

Environment

  • SAP HANA, platform edition
  • SAP HANA DB Engines

Product

SAP HANA, platform edition 2.0

Keywords

hana primary down, automatic failover, pacemaker demote, IPC timeout, rsyslogd saturation, syslog flooding, audit policy, health check timeout, cluster timeouts, system replication, sigint 2, demotion , 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.