Error Message

No error messages. Services are coming online as configured. The behavior needs to be modified.

The ERS instance profile needs additional configuration.

To resolve the issue of SAP ERS service group not failing over to the opposite node of the ASCS service group, additional configuration is needed in the ERS instance profile.

1. Open the ERS profile file and add the following lines under the section labeled standalone enqueue details from the (A)SCS instance:
   enque/poll_interval = 0
   enque/poll_timeout = 120
   enque/enrep/inactive_actio = sleep
   enque/table_size = 4096
2. Delete the following lines:
   Autostart = 1
enque/enrep/hafunc_implementation = script
3. Change the Restart_Program_00 to Start_Program_00 under the Start enqueue replication server section
   Start_Program_00 = local $(_ER) pf=$(_PFL) NR=$(SCSID)
4. Restart the SAP environment and test the failover again.

Additional information can be found on page 41 of the SAP Netweaver Agent Guide

The SAP ERS (Enqueue Replication Service) service group doesn't switch to the opposite node when the SAP ASCS (ABAP Central Services) service group is moved to the same node.This results in the service groups being online on the same node. For SAP replication to function correctly, the ASCS and ERS service groups need to be on opposite nodes.

JIRA: STESC-8557