RAC and Oracle Clusterware Best Practices and Starter Kit (HP-UX) (文件 ID 811303.1)

In this Document

Purpose

Scope

Details

RAC Assurance Support Team: RAC and Oracle Clusterware Starter Kit and Best Practices (Generic)

RAC Platform Specific Starter Kits and Best Practices

RAC on HP-UX Step by Step Installation Instructions

RAC on HP-UX Best Practices

OS Configuration Considerations

Storage Considerations

Network Considerations

Oracle Software Considerations

Community Discussions

References

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 to 12.1.0.1 [Release 10.2 to 12.1]
HP-UX PA-RISC (64-bit)
HP-UX Itanium

Purpose

The goal of the Oracle Real Application Clusters (RAC) series of Best Practice and Starter Kit notes is to provide customers with quick knowledge transfer of generic and platform specific best practices for implementing, upgrading and maintaining an Oracle RAC system. This document is compiled and maintained based on Oracle's experience with its global RAC customer base.

This Starter Kit is not meant to replace or supplant the Oracle Documentation set, but rather, it is meant as a supplement to the same. It is imperative that the Oracle Documentation be read, understood, and referenced to provide answers to any questions that may not be clearly addressed by this Starter Kit.

All recommendations should be carefully reviewed by your own operations group and should only be implemented if the potential gain as measured against the associated risk warrants implementation. Risk assessments can only be made with a detailed knowledge of the system, application, and business environment.

As every customer environment is unique, the success of any Oracle Database implementation, including implementations of Oracle RAC, is predicated on a successful test environment. It is thus imperative that any recommendations from this Starter Kit are thoroughly tested and validated using a testing environment that is a replica of the target production environment before being implemented in the production environment to ensure that there is no negative impact associated with the recommendations that are made.

Scope

This article applies to all new and existing RAC implementations as well as RAC upgrades.

Details

RAC Assurance Support Team: RAC and Oracle Clusterware Starter Kit and Best Practices (Generic)

The following document focuses on RAC and Oracle Clusterware Best Practices that are applicable to all platforms including a white paper on available RAC System Load Testing Tools and RAC System Test Plan outlines for 10gR2 & 11gR1 and 11gR2:

Document 810394.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)

RAC Platform Specific Starter Kits and Best Practices

The following notes contain detailed platform specific best practices including Step-By-Step installation cookbooks (downloadable in PDF format):

Document 811306.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Linux)
Document 811280.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Solaris)
Document 811271.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Windows)
Document 811293.1 RAC and Oracle Clusterware Best Practices and Starter Kit (AIX)
Document 811303.1 RAC and Oracle Clusterware Best Practices and Starter Kit (HP-UX)

RAC on HP-UX Step by Step Installation Instructions

Click here for a Step By Step guide for installing Oracle RAC 10gR2 on HP-UX.
Click here for a Step By Step guide for installing Oracle RAC 11gR1 on HP-UX.

RAC on HP-UX Best Practices

The Best Practices in this section are specific to the HP-UX Platform. That said, it is essential that the Platform Independent Best Practices found in Document 810394.1 also be reviewed.

OS Configuration Considerations

Validate your hardware/software configuration against the RAC Technologies Matrix for Unix.
Ensure all required OS packages are installed and system prerequisites have been properly implemented for your particular release of Oracle. This information is documented in Document 169706.1 as well as the install guides for your particular release.
Ensure that the mandatory patches listed in Document 169706.1 for your particular release or later versions of these patches have been applied. Superseded patches can be found on HPs ITRC site by querying the patch database. You must have a valid support contract with HP to use this tool.
Ensure that OS Patch PHKL_40208 and PHKL_40372 or higher have been applied to avoid the node evictions described in Document 883801.1.
Do not use the bash shell for Oracle software owners, this may result in root.sh failures for 10.2 and 11.1 installations. Please see Document 734618.1 for details.
Hostnames on HP-UX should be 8 characters or less. Refer to Document 469569.1 for more details.
Ensure proper Oracle process scheduling priority for HP-UX as described in Document 759082.1.
In pre-11gR2 clusters, system times are to be synchronized across cluster nodes using NTPD and that NTPD should be configured to slew time. Without the slew option NTP will shift the system clock forwards or backwards in time when the offset is beyond the 128ms threshold which can result in node evictions in a RAC cluster. For instructions on how to enable the slewing option for xntpd see the xntpd HP-UX man page.
With 11gR2, Cluster Time Synchronization Daemon (CTSSD) can be used in place of NTPD. CTSSD will synchronize time with a reference node in the cluster when an NTPD is not found to be configured. Should you require synchronization from an external time source you must use NTPD which will cause CTSSD to run in "observer" mode. However, if NTP is running, then it must to be configured with the slewing option as documented in Document 551704.1.

Storage Considerations

HP LVM logical volume (LV) by default has an infinite I/O timeout which would cause the CSS daemon to hang if the node has no access to the storage that houses either the Oracle Clusterware software or Oracle Clusterware voting disk. To avoid the hang problem, the LVs used for these components should be configured with an I/O timeout value. The LVs time out value can be changed using the lvchange command. Note that the PV timeout value can be changed, so make sure to use the configured value instead of the default PV timeout of 30 seconds. The recommended value is: LV timeout value = (# of paths * PV Timeout) + 10 seconds. Reference unpublished Bug 7633778.
Shutdown the CRS stack cleanly before trying to unmount the shared filesystem. Most other clustered file systems require you to stop all process holding file descriptors open, before permitting the unmount command to continue. That is not presently the case with HP-UX Veritas Clustered Filesystem. If the clustered filesystem with OCR is unmounted 'cfsumount,' while the crs stack is still up and running, the cfsumount kills any holding processes. This will terminate the OCSSD process, without warning.

Network Considerations

Jumbo frames with mtu 9000 cause problems with hp nc7170 drivers.
On HP-UX 11.23 set streams_sqmax=50000 to reduce packet loss at the streams layer to increase RAC database stability and performance. See Document 363418.1.
On HP-UX systems running 10Gb Ethernet ensure that the revision B.11.31.1011 or later of the 10GigEthr-02 software bundle has been installed to prevent 11.2.0.2 GI install/startup failures due to improper multicast functionality. See Document 1276346.1 for details.
Review Document 296874.1 for information on configuring NIC redundancy (HP Auto Port Aggregation (APA) and MC/Service Guard) for the Oracle Virtual IPs (including SCAN).

Oracle Software Considerations

The Software Considerations in this section are specific to the HP-UX Platform. That said, it is highly recommended that the Platform Independent Best Practices found in Document 810394.1 be reviewed.

For 11.2.0.2 on HP-UX only 1 HAIP will be configured regardless of the number of interfaces defined for the cluster interconnect. This is by design (not a bug) and will not impact the failover of HAIP from one interface to another. This is documented in unpublished Bug 10114953.
On HP-UX Itanium, on pre-11.2 environments RACGMAIN can crash during a resource check with a SIGSEGV error. See Document 763724.1 for corrective action.
For all releases 10.2.0.4 - 11.2.0.1, apply the fix for Bug 10158006 to prevent database crashes when short stacks are taken. See Document 1271173.1 for details.

References

NOTE:810394.1 - RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)
NOTE:1365167.1 - hp-ux: 11gR2 Grid Infrastructure Node Eviction Due to Memory Pressure