User's Guide

• SGeSAP packages that do not contain database components can be configured to run on any node
in the cluster. This includes ci, jci, [a]rep and d package types.
• SGeSAP database instance packages must be configured to run only on either Integrity or HP 9000
nodes. This includes db, jdb and lc package types and all package types composed of these.
NOTE: Always check for the latest versions of the Serviceguard Extension for SAP manual and release
notes at http://docs.hp.com/en/ha.html. Especially for mixed cluster setups and configurations refer
to SAP note 612796 - 'Move to HP-UX Itanium systems'.
Even though the SAP HP 9000 executables might run on Integrity systems under the ARIES binary emulator,
SAP has no plans to support HP 9000 executables on Integrity systems. Consequently, it is mandatory to
obtain SAP executables for the additional Integrity nodes. So the SAPEXE and SAPDBEXE.SAR archives
for the Integrity based systems have to be downloaded, for example from Service Marketplace
(http://service.sap.com) for the corresponding already installed SAP component.
The SAP kernel executables for HP 9000 and Integrity processors need to be in sync with their patch levels.
It is guaranteed that the same patch levels are available from SAP at all times.
System Configuration Change: PI010
The shared disk containing SAP executables, profiles and globals ( /sapmnt/sapmnt/<SID> ) must have
sufficient disk space for a full set of additional Integrity binaries.
System Configuration Change: PI020
The SAP executable directory is the key point where the redirection for HP 9000 or Integrity executables is
performed, so the HP 9000 executables need to be moved to a distinct directory.
cd /sapmnt/<SID>
mv exe exe_pa
System Configuration Change: PI025
Create a directory for the Integrity binaries.
cd /sapmnt/<SID>
mkdir exe_ipf
and extract the downloaded SAR archives
SAR xvf <...>/SAPEXE.SAR /sapmnt/<SID>/exe_ipf
SAR xvf <...>/SAPDBEXE.SAR /sapmnt/<SID>/exe_ipf
System Configuration Change: PI030
The executable directory is substituted by a link referencing another local symbolic link that distinguishes
between a HP 9000 or Integrity based system.
cd /sapmnt/<SID>
ln -s /sapmnt/<SID>exe_local exe
Take note that the referenced local executable link does not reside on the shared disc - it is on the local file
system on each cluster node pointing to the appropriate executables for a HP 9000 or Integrity platform. In
that case for a HP 9000 system:
cd /sapmnt
ln -s /sapmnt/<SID>/exe_pa /sapmnt/<SID>exe_local
System Configuration Change: PI040
Similar to the local executable link on HP 9000 systems, perform the step for the Integrity node:
cd /sapmnt
ln -s /sapmnt/<SID>exe_ipf <SID>exe_local
System Configuration Change: PI050
Make sure to have a local copy of the Oracle client libraries on all nodes.
You'll need to download the HP 9000 version for the PA RISC nodes and the IPF version for the Integrity
nodes from http://service.sap.com.
Mixed Clusters 141