Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Linux Configuration
Chapter 2 49
Never use the relocatable address in these filenames. If an application
server was already installed, do not overwrite any files which will start
the application server. If the rc-files have been modified, correct any
hardcoded references to the primary hostname.
IS160 Installation Step:
If the system has a SAP kernel release < 6.0:
On each host the files /home/<sid>adm/startsap_<local>_<INSTNR>
and /home/<sid>adm/stopsap_<local>_<INSTNR> exist and contain a
line that specifies the start profile. After a standard installation this line
is similar to:
START_PROFILE=”START_DVEBMGS<INSTNR>_<primary>”
As <sid>adm, change the line individually on each node.
On the primary host keep:
START_PROFILE=”START_DVEBMGS<INSTNR>_<primary>”
On the secondary host change the value in both files to:
START_PROFILE=”START_DVEBMGS<INSTNR>_<secondary>”
OR170 Optional Database Step:
Create a mount point for the Oracle files on the backup node if it is not
already there. For example:
su - ora<dbsid>
mkdir -p /oracle/<DBSID>
exit
SD180 SAPDB Database Step:
Create a mount point for the SAPDB files on the backup node if it is not
already there. For example:
su - sqd<dbsid>
mkdir -p /sapdb/<DBSID>
exit