/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
- SAP HANA system is reported as “unexpectedly stopped”
- A System Replication takeover to the secondary host occurs
- Customer assumes a HANA crash or System Replication failure
- HANA traces do not show SIGSEGV, assertion failure, or OOM kill
- Cluster environments (e.g. Pacemaker) are typically involved
Read more...
Environment
SAP HANA DB Version 2.0
Product
SAP HANA, platform edition 2.0
Keywords
SAP HANA, System Replication, controlled shutdown, Pacemaker, QUIT SIGINT , 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.
/support/notes/service/facebook.svg)
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)