Symptom
- System Replication frequently re-sync's and reconnects.
- Logs grow and it is slow to perform full replication.
- indexserver is suddenly restarted without any prior HANA error recorded.
- Daemon traces at the time of the indexserver restart show information such as
i Daemon TrexDaemon.cpp(04395) : process hdbindexserver with pid <######> exited because it caught signal 9
- OS logs (messages) show events such as
...<hostname> kernel: [9175922.756466] Out of memory: Killed process <pid> (hdbindexserver) total-vm:########8kB, anon-rss:#########kB, file-rss:0kB, shmem-rss:############kB
... <hostname> rtkit-daemon[7880]: The canary thread is apparently starving. Taking action.32kB..
Read more...
Environment
SAP HANA High Availability (System Replication, DR, etc.)
Product
SAP HANA, platform edition all versions
Keywords
System Replication, frequent restart, OS level execution, SAP HANA High Availability, oom-killer, memory resource, secondary site HANA Database, Note 1857315, HANA server disappears, crashes, crashdump. , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , BC-OP-LNX , Linux , 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.