Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Linux Configuration
Chapter 3 119
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.
IS130 Installation Step:
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_<component><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>”