HP Serviceguard Extension for SAP (SGeSAP) manual Cold Admin Warm Online

### Add following line

. /etc/cmcluster/<LCSID>/sapwas.cntl start <LCSID> test_return 51

}

function customer_defined_halt_cmds

{

### Add following line

. /etc/cmcluster/<LCSID>/sapwas.cntl stop <LCSID> test_return 52

}

liveCache Installation Step: LC190

The/etc/cmcluster/<LCSID>/sap.configconfiguration file of a liveCache package is similar to the configuration file of Netweaver Instance packages.

The following standard parameters in sap.config have to be set for a liveCache package:

LCRELOC=<reloclc_s>

TRANSRELOC=<relocsapnfs_s>

CLEANUP_POLICY= [ strict normal lazy ]

The strict option can be set in order to guarantee the liveCache package gets all resources required on the adoptive node. Remember that this option can crash a system running on the adoptive node.

▲The following liveCache specific parameters in sap.config have to be set:

LCSTARTMODE specifies the mode of the liveCache database up to which it should be started automatically. Possible values for version 7.4 of liveCache are:

OFFLINE: only vserver will be started

ADMIN: liveCache started in cold mode

SLOW: liveCache started in cold -slow mode

ONLINE: liveCache started in warm mode

In liveCache version 7.5 some of these values have changed: (<from> -> <to>)

COLD -> ADMIN

WARM -> ONLINE

It is recommended to use the new values for liveCache version 7.5. For compatibility reasons the original values will still work though.

After failover, liveCache will only be recovered to the state referenced in LCSTARTMODE.

The behavior of the liveCache service monitoring script is independent from the setting of LCSTARTMODE. The monitoring script will always monitor the vserver process. It will start to monitor if liveCache is in WARM state, as soon as it reaches WARM state for the first time.

The LCMONITORINTERVAL variable specifies how often the monitoring polling occurs (in sec.)

hot standby Installation Step: LC193

The following additional parameters in sap.config have to be set for a hot standby liveCache package:

Hot standby systems have a preferred default machine for the instance with the master role. This should usually correspond to the hostname of the primary node of the package. The hostname of the failover node defines the default secondary role, i.e. the default standby and alternative master machine. For a hot standby system to become activated, the LC_PRIMARY_ROLE and the LC_SECONDARY_ROLE need to be defined with physical hostnames. No virtual addresses can be used here.

LC_PRIMARY_ROLE=<primary_node>

LC_SECONDARY_ROLE=<secondary_node>

SGeSAP Legacy Package Configuration 105