Managing Serviceguard Extension for SAP Version B.05.10, September 2010

Copy the <sid>adm home directory to he backup node(s).
This is a local directory on each node. Default home directory path is /home/<sid>adm.
Installation Step: IS120
On the second node, in the <sid>adm home directory the start, stop and environment scripts
need to be renamed.
If some of the scripts listed in the following do not exist, these steps can be skipped.
su - <sid>adm
mv startsap_<primary>_<INR> startsap_<secondary>_<INR>
mv stopsap_<primary>_<INR> stopsap_<secondary>_<INR>
mv .sapenv_<primary>.csh .sapenv_<secondary>.csh
mv .sapenv_<primary>.sh .sapenv_<secondary>.sh
mv .dbenv_<primary>.csh .dbenv_<secondary>.csh
mv .dbenv_<primary>.sh .dbenv_<secondary>.sh
mv .sapsrc_<primary>.csh .sapsrc_<secondary>.csh
mv .sapsrc_<primary>.sh .sapsrc_<secondary>.sh
mv .dbsrc_<primary>.csh .dbsrc_<secondary>.csh
mv .dbsrc_<primary>.sh .dbsrc_<secondary>.sh
The following statement should automate this activity for standard directory contents. Do not
use a line break within the awk statement:
su - <sid>adm
ls -a|awk '/<primary>/ { system( sprintf( "mv %s %s\n", $0,\
gensub("<primary>", "<secondary>", 1 ))) }'
exit
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 hard coded references to the primary hostname.
Installation Step: IS130
If the system has a SAP kernel release < 6.0:
On each host the files /home/<sid>adm/startsap <local>_<INR> and
/home/<sid>adm/stopsap_<local>_<INR> exist and contain a line that specifies the start
profile. After a standard installation of a Central Instance this line is similar to:
START_PROFILE="START_<INSTNAME><INR>_<primary>"
As <sid>adm, change the line individually on each node.
On the primary host keep:
START_PROFILE="START_DVEBMGS<INR>_<primary>"
On the secondary (and any other potential failover) host, change the value in both files to:
START_PROFILE="START_DVEBMGS<INR>_<secondary>"
Oracle Database Step: OR150
If the primary node has the ORACLE database installed:
Create additional links in /oracle/<SID> on the primary node.
Example:
su - ora<sid>
ln .dbenv_<primary>.csh .dbenv_<secondary>.csh
ln .dbenv_<primary>.sh .dbenv_<secondary>.sh
exit
NOTE: If you are implementing an Application Server package, make sure that you install the
Oracle Client libraries locally on all nodes you run the package on. Refer to OSS Note 180430 for
more details.
Oracle Database Step: OR160
58 Step-by-Step Cluster Conversion