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

if not already delivered in a translated form. At this first time of execution, the translated code
is also stored in the database for next time use. This table is usually sized to hold the code for
one platform. If you deploy application servers of different platforms within a single SAP system,
this table needs to be sized appropriately to avoid unnecessary translations.
A mixed cluster containing both HP 9000 and Integrity HP-UX nodes must fulfill the following
prerequisites:
• The system needs to be based on single-instance ORACLE database technology.
• All cluster nodes are installed with HP-UX 11i v2 (ud2) or higher.
• The bundles of the HP Serviceguard Storage Management Suite are not allowed in SAP
mixed clusters
• The cluster setup must follow the storage layout option 1 of chapter 2 (NFS-based)
• 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 www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard
Extension for SAP. 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
Mixed Clusters 181