Configuring SAP profile parameters

After you install an SAP system on all the nodes, you must set up the profile parameters for the newly created server profile files for high availability.

1. Disable the Autostart parameter on all SAP instances in each profile by commenting the line Autostart = 1.
2. Ensure that PowerHA® SystemMirror® is already installed on cluster nodes. Add the following entries to the default profile file DEFAULT.PFL.

   
   #-----------------------------------------------------------------------
   # SAP high availability connector
   #-----------------------------------------------------------------------
   service/halib=/usr/sap/<SID>/SYS/exe/dbg/saphascriptco.so
   service/halib_cluster_connector=/usr/sbin/rsct/sapolicies/sap/bin/sap_tsamp_cluster_connector
   

   If the /usr/sap/<SID>/SYS/exe/dbg/saphascriptco.so file is not found on your local system, use the /usr/sap/<SAPSID>/SYS/exe/uc/<your_platform>/saphascriptco.so file.

3. Disable the SAP restart capability for Enqueue Server and Enqueue Replication Server in the corresponding profiles. Otherwise, the automatic restart capability of SAP that was enabled by using the startsapsrv command mismatches with the PowerHA SystemMirror start function and might cause problems with high availability.
   Set the SAP profile parameter for Enqueue Server (ENSA) and Enqueue Replicator Server (ERS) to Start_Program_<NR> in the ENSA and ERS profiles that are present in the /sapmnt/<SID>/profile directory. For servers other than ENSA and ERS, set the SAP profile parameter to Restart_Program_<NR>.

   If the SAP profile parameter is set to Start_Program_<NR>, then

   • When you start the SAP application instances for the first time, the startup operation is performed by the startsapsrv framework.
   • When a node failure occurs, during the recovery process, the SAP application instances are started by PowerHA SystemMirror. PowerHA SystemMirror resources can start automatically or resources can failover.

   If the SAP profile parameter is set to Restart_Program_<NR>, then

   • When you start the SAP application instances for the first time, the startup operation is performed by the startsapsrv framework.
   • When a node failure occurs, during the recovery process, the SAP application instances are started by PowerHA SystemMirror. PowerHA SystemMirror resources can start automatically.
4. Save the enqueue backup file in the NFS-mounted /sapmnt/<SID>/global directory so that it can be accessed from all nodes in the cluster. The enqueue backup file is created when the enqueue server is started. Add the following parameter to the ABAP SAP Central Services (ASCS) profile to share the enqueue backup files across all nodes in the cluster:

   enque/backup_file = $(DIR_GLOBAL)/ENQBCK(A)SCS

5. Verify the /usr/sap/sapservices file on all nodes.

   The /usr/sap/sapservices file must contain commands to start the SAP start service sapstartsrv for each SAP instance installed on the server. The /usr/sap/sapservices file must have permission of 0755 (rwxr-xr-x) as the /usr/sap/sapservices file is read by the sapinit service.

   If there is no entry for the SAP start service in the /usr/sap/sapservices file after installation, you must add an entry for starting the SAP start service in a single line without line breaks in the /usr/sap/sapservices file. An example entry follows:

    
   #!/bin/sh
   LD_LIBRARY_PATH= /usr/sap/<sid>/<instance>/exe:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH; /usr/sap/<sid>/<instance>/exe /sapstartsrv pf=<DIR_PROFILE>/<INSTANCE_START_profile> -D -u <sid>adm>