Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Application Configuration
Chapter 286
rsdb/reco_trials = 15
rsdb/reco_sleep_time = 60
rsdb/reco_sosw_for_db = off (based on OSS #109036)
rsdb/reco_sync_all_server = on
IS997 Installation Step:
For each secondary node, the SAP instance profiles and SAP startup
profiles need to be copied.
cp /sapmnt/<SID>/profile/START_DVEBMGS<INSTNR>_<primary> \
/sapmnt/<SID>/profile/START_DVEBMGS<INSTNR>_<secondary>
cp /sapmnt/<SID>/profile/<SID>_DVEBMGS<INSTNR>_<primary> \
/sapmnt/<SID>/profile/<SID>_DVEBMGS<INSTNR>_<secondary>
In all START_DVEBMGS<INSTNR>_<secondary> files, replace any
reference to <SID>_DVEBMGS<INSTNR>_<primary> with
<SID>_DVEBMGS<INSTNR>_<secondary>.
IS1000 Installation Step:
There are two SAP transport configuration files: DOMAIN.CFG and
TP_DOMAIN_<SID>.PFL. Changing these files on a filesystem level will
cause SAP transaction STMS to report wrong values. Change the value
in STMS directly. If STMS has not been initialized with other values, this
step can be omitted.
SM59->add <relocci> as destination of R/3 connection <SID>
STMS_DOM->doubleclick <SID>->TransportTool tab->DBHOST
parameter should be <relocdb>