Configuration Rules for a Mixed HP 9000 / Integrity Serviceguard Cluster, March 2007
Table Of Contents
- Executive summary
- Version history
- Introduction
- Architectural rules and typical configurations
- Specific ISV information
- HP Superdome Hybrid Servers
- Typical configuration examples
- Transition to Integrity with HP Superdome hybrid servers and mixed clusters
- Adding one Integrity server to a two-node HP 9000 cluster
- Adding two HP Integrity servers to a two-node HP 9000 cluster
- Adding one critical application and two new Integrity nodes to existing four-node HP 9000 cluster
- Mixed clusters as transition aid from HP 9000 to Integrity in a multi-tier SAP environment
- HP 9000 to Integrity transition service utilizing HP Serviceguard cluster technology
- How to implement a mixed HP 9000 / Integrity HP Serviceguard cluster
- For more information
• Oracle does not support running the PA-RISC database binaries under the Aries emulator on HP
Integrity servers.
• Only Oracle 9iR2 and 10gR2 or later will be supported, with the PA-RISC version running on HP
9000 servers and the Intel® Itanium® version running on Integrity systems. There will be no support
for 10gR1.
• Mixed clusters are not supported with Oracle Real Application Cluster (RAC) and HP Serviceguard
Extension for RAC (SGeRAC).
– However, Oracle supports RAC in disaster tolerant configurations in which the primary cluster
consists of nodes of a different architecture than the secondary cluster. In this configuration one
cluster consists of HP 9000 nodes only and the other cluster is build from Integrity systems with
Data Guard as data replication method between the two RAC clusters. This configuration is
supported only for Redo Apply (physical standby database) and not for SQL Apply (logical
standby database) by Oracle and does not include HP Continentalclusters.
Special requirements exist in a mixed cluster, if customers use natively compiled objects, for instance
procedures, functions, and types known as PL/SQL Native Compilation (NCOMP). Those objects
need to be recompiled locally if the database is started up on a node with a different architecture
then the one it did run on before. Additional information on NCOMP and regarding Oracle support
of mixed architecture clusters can be found in the Oracle documentation referenced at the “related
documents” section above, in particular:
•
http://www.oracle.com/technology/tech/pl_sql/htdocs/ncomp_faq.html#spnc_commands
• http://download-est.oracle.com/docs/cd/B13789_01/appdev.101/b10807/12_tune.htm#i48528
SAP with HP Serviceguard Extension for SAP
Mixed clusters have been validated and tested with SAP. Support for it is available since HP
Serviceguard Extension for SAP (SGeSAP) B.03.11.
SAP Application Server and SAP Central Instance packages (APP, D, and CI package types) are
supported in mixed environments. They can be configured to fail over between heterogeneous nodes.
A database package (JDB, DB, and DBCI package types) are also supported to fail-over between
heterogeneous nodes if the database is single instance Oracle 9i or 10g starting with SGeSAP
B.04.50. If those packages contain an Informix, DB2 or MaxDB database, they must fail-over
between homogenous nodes—either HP 9000 only or Integrity server only.
Livecache packages (LC package type) are only allowed to fail-over between homogeneous nodes in
a mixed cluster.
Informix Dynamic Server
Version 10.00FC1 of Informix Dynamic Server (IDS) is the first common release of IDS for HP9000
and HP Integrity Servers. This is also the minimum required IDS version to be deployed in a mixed HP
9000 / Integrity Serviceguard cluster.
For further details on IDS in mixed Serviceguard clusters, consult:
•
http://h71019.www7.hp.com/ActiveAnswers/downloads/Serviceguard_IBM-IDC_HP9000_Integrity.pdf
Sybase
At the time this documentation was written, tests with Sybase ASE version 15.01 were still in
progress. Please check with your HP or Sybase representative for the current status.
14