Managing Serviceguard Extension for SAP, December 2007

SGeSAP Cluster Administration
Mixed Clusters
Chapter 6310
PI040: System Configuration Change:
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
PI050: System Configuration Change:
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.
Oracle Filesets
Currently Oracle does not support the failover of databases based on HP
9000 binaries to nodes using executables compiled for the Integrity
platform. Consequently this means, the use of an Oracle database
package in a mixed environment is restricted to one platform. Therefore
the database package must be kept either on purely HP 9000 or Integrity
nodes. The installation and configuration of a database package should
have been done already, as mentioned in the prerequisites. Oracle
database servers at least need to match the version number that the
used Oracle client libraries have. Mixed clusters are only possible using
Oracle 9i versions, because the Integrity executable set of the SAP kernel
uses Oracle 9i client libraries. The SAP kernel acts as an Oracle client.
As a consequence, Oracle 8 database releases need to be upgraded before
they can be used in mixed cluster setups. HP recommends to use the
highest database server patch level that is supported for the used SAP
component. This will be at least Oracle 9.2.0.3. It is not possible to use a
HP 9000 based Oracle 8 database for environments that might serve
SAP components on IPF.