Crash enqueue server process - SAP NetWeaver on Amazon
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Crash enqueue server process

Description – crash enqueue server process using kill.

Run node – primary node where ASCS is running.

Run steps

hahost01:~ # ps -ef | grep enq ha1adm 15453 15441 0 13:35 ? 00:00:01 enq.sapHA1_ASCS00 pf=/usr/sap/HA1/SYS/profile/HA1_ASCS00_ascshost root 17487 8801 0 13:44 pts/1 00:00:00 grep --color=auto enq hahost01:~ # kill -9 15453

Expected result – because the Start_Program_01 = local $(_ENQ) pf=$(_PF) parameter is in the ASCS instance profile, the cluster will failover ASCS (message server process and enqueue process) to the secondary node.

hahost01:~ # crm status Cluster Summary: * Stack: corosync * Current DC: hahost02 (version 2.0.xxxxxxxxxxxx) - partition with quorum * Last updated: * Last change: by ha1adm via cibadmin on hahost02 * 2 nodes configured * 7 resource instances configured Node List: * Online: [ hahost01 hahost02 ] Full List of Resources: * res_AWS_STONITH (stonith:external/ec2): Started hahost02 * Resource Group: grp_HA1_ASCS00: * rsc_IP_HA1_ASCS00 (ocf::suse:aws-vpc-move-ip): Started hahost02 * rsc_FS_HA1_ASCS00 (ocf::heartbeat:Filesystem): Started hahost02 * rsc_SAP_HA1_ASCS00 (ocf::heartbeat:SAPInstance): Started hahost02 * Resource Group: grp_HA1_ERS10: * rsc_IP_HA1_ERS10 (ocf::suse:aws-vpc-move-ip): Started hahost01 * rsc_FS_HA1_ERS10 (ocf::heartbeat:Filesystem): Started hahost01 * rsc_SAP_HA1_ERS10 (ocf::heartbeat:SAPInstance): Started hahost01

Recovery procedure – N/A.