If you configure the JAVA stack, you need to know that the JAVA stack does not detect that a database is running on the remote node. You must disable the database start from the start profile of the application instances.
# Start_Program_00 = immediate $(_DB)
To recover the enqueue replication after network outages, add the following line to the instance profile of the enqueue replication server.
enque/enrep/keepalive_count = 1
If your SAP version supports an integration between the SAP management console and Oracle Solaris Cluster, issue user administration permission to the SAP administrator. On all nodes, execute the following command:
# usermod -A solaris.cluster.admin sidadm
Ensure that the SAP enqueue server is not restarted upon process failures, by changing the Restart_Program_01 = local $(_EN) pf=$(_PF) line in the SAP central services profile to Start_Program_01 = local $(_EN) pf=$(_PF). For example:
#----------------------------------------------------------------------- # Start SAP enqueue server #----------------------------------------------------------------------- _EN = en.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME) Execute_03 = local rm -f $(_EN) Execute_04 = local ln -s -f $(DIR_EXECUTABLE)/enserver$(FT_EXE) $(_EN) Start_Program_01 = local $(_EN) pf=$(_PF)
Disable the automatic start of the sapstartsrv processes at server boot on all the nodes. Rename or remove the link /etc/rc3.d/S90sapinit to avoid the start of sapstartsrv processes during reboot of the server:
# cd /etc/rc3.d/ # ls -al # mv S90sapinit s90sapinit