- ASCS and ERS should be installed based on “virtual hostname” based on “virtual IP”, which should have been added to hosts files during earlier installation steps. Be sure to do so if they have not already been done prior to installing SAP.
- When installing SAP (specifically ASCS or SCS) you need to specify the SAPINST_USE_HOSTNAME=vip option. This is not required for ERS. (Note: Document the SAPINST_USE_HOSTNAME virtual IP address as it will be used later during creation of the SAP resources in LifeKeeper.)
- When installing SAP (specifically ASCS or SCS) you need to specify the SAPINST_USE_HOSTNAME=vip option. This is not required for ERS. (Note: Document the SAPINST_USE_HOSTNAME virtual IP address as it will be used later during creation of the SAP resources in LifeKeeper.)
Note: Specify sapinst SAPINST_USE_HOSTNAME=vip where vip is the virtual IP that will float between the nodes.
Run ./sapinst SAPINST_USE_HOSTNAME= {hostname}
- In seven phases, the Core Services should be created and started. If permission errors occur on jdbcconnect.jar, go to /sapmnt/STC/exe/uc/linuxx86_64 and make that directory as well as file jdbcconnect.jar writable (chmod 777 ---).
- In seven phases, the Core Services should be created and started. If permission errors occur on jdbcconnect.jar, go to /sapmnt/STC/exe/uc/linuxx86_64 and make that directory as well as file jdbcconnect.jar writable (chmod 777 ---).
Enqueue replication should be configured and checked working based on SAP documentation and best practices.
- ASCS and ERS profiles should be pointing to local mount point containing /usr/sap, sapmnt or any other necessary for SAP files in your environment, the actual files will be moved onto NFS mount points after it is installed and configured.
The ASCS and ERS instance profiles must be modified in order to prevent the enqueue server and enqueue replicator processes from being automatically restarted by the sapstart utility. After updating the instance profiles, SAP Start Service for each of these instances must be restarted in order for the changes to take effect. Follow the steps provided in Modify ASCS and ERS Instance Profile Settings, then return to this page to continue the setup process.
- Sapstop SAP on node 1
- Using the LifeKeeper GUI, right click on the IP address resource created for ASCS, select “In-Service” and select node2 to switch the IP onto node 2.
- Repeat step 1 to install SAP onto node 2 and ensure that it’s able to run correctly
- Sapstop SAP on node 2
- Using the LifeKeeper GUI, right click on the IP address resource created for ASCS, select “In-Service” and select node1 to switch the IP back onto node 1.
- Sapstart SAP on node 1 and ensure that it’s able to run correctly
Post your comment on this topic.