Symptom
1. Restart occurred in the SAP HANA high availability cluster following an OS upgrade.
2. The restart was triggered by the cluster and not the database itself.
3. The SAP HANA resource agent initiated a clean stop and subsequent restart of the system.
Daemon Traces:
[XXXXXX]{-1}[-1/-1] i Daemon SignalsUNIX.cpp(00601) : signo 2=SIGINT from user. errno 0 code 0. Requested 'QUIT'. Sender pid XXXXXX, real user 'XXXXX', executable 'sapstart'
[XXXXXX]{-1}[-1/-1] i Daemon DaemonHandle.cpp(00094) : Got shutdown event (quit). Stop children processes with timeout 270000 ms
[XXXXXX]{-1}[-1/-1] i Daemon Events.cpp(00133) : "KillInstanceEvent" is due in 270000 ms. Program 'hdbcompileserver', pid XXXXXX
[XXXXXX]{-1}[-1/-1] i Basis TraceStream.cpp(00526) : ==== Starting hdb.XXXXXX, version XX.XX.XXX.XX (fa/hana2sp07), build linuxx86_64 XXXXXX XXXXXX
Pacemaker Logs:
SAPHana(SAPHana_P12_00)[402884]: INFO: ACT: Stopping SAP Instance P12-HDB00: Stop OK SAPHanaTopology(SAPHanaTopology_P12_00)[402620]: WARNING: RA: HANA_CALL stderr from command 'su - p12adm -c' is '', stderr from command 'python
SAPHana(SAPHana_P12_00)[427846]: INFO: DEC: hana_p12_site_srHook_SITEA= SAPHana(SAPHana_P12_00)[427846]: INFO: ACT: Starting SAPHANA Instance P12-HDB00: Start OK
Read more...
Environment
SAP HANA High Availability (System Replication, DR, etc.)
Product
Keywords
SAP HANA, high availability, system replication, RHEL OS upgrade, restart, cluster, resource agent, clean stop, replication enabled, primary node, maintenance mode , KBA , HAN-DB-HA , SAP HANA High Availability (System Replication, DR, etc.) , BC-OP-LNX , Linux , BC-OP-LNX-RH , Red Hat Linux , BC-OP-LNX-SUSE , SUSE 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.
SAP Knowledge Base Article - Preview