Serviceguard Extension for RAC Version A.11.19 Release Notes, October 2009 (T1907-90051)

NOTE: Starting with Oracle 10g, Oracle Clusterware processes register with cmgmsd
while Oracle server processes register with Oracle Clusterware. The maximum number
of Oracle server processes supported is determined by Oracle Clusterware. The
maximum number of processes registered by Oracle Clusterware should not exceed
the maximum supported by cmgmsd.
Upgrade Using DRD
DRD stands for Dynamic Root Disk. Using a Dynamic Root Disk on HP-UX 11i v3
allows you to perform the update on a clone of the root disk, then halt the node and
reboot it from the updated clone root disk.
You can obtain the DRD software free from software.hp.com; search for
DynRootDisk. For more information, go to HP's Dynamic Root Disk Information
Library at docs.hp.com/en/DRD/infolib.html. (You can also reach the information
library from www.hp.com/go/drd —> Additional Information; or go to
www.hp.com and search for Dynamic Root Disk Information Library).
IMPORTANT: Use the clone disk only on the system on which it was created. At
present Serviceguard does not support booting from a clone disk made on another
system (sometimes referred to as DRD re-hosting).
Rolling Upgrade Using DRD
A rolling upgrade using DRD is like a rolling upgrade, but is even less disruptive
because each node is down for a shorter time. It is also very safe; if something goes
wrong you can roll back to the original (pre-upgrade) state by rebooting from the
original disk.
This method is the least disruptive, but you need to make sure your cluster is eligible;
see“Restrictions for DRD Upgrades” (page 17).
If, after reading and understanding the restrictions, you decide to perform a rolling
upgrade using DRD, follow the instructions under “Performing a Rolling Upgrade
Using DRD” (page 22).
Non-Rolling Upgrade Using DRD
In a non-rolling upgrade with DRD, you clone each node's root disk and apply the
upgrade to the clone, then halt the cluster and reboot each node from its updated clone
root disk.
This method involves much less cluster down time than a conventional non-rolling
upgrade, and is particularly safe because the nodes can be quickly rolled back to their
original (pre-upgrade) root disks. But you must make sure your cluster is eligible; see
“Restrictions for DRD Upgrades” (page 17).
16 Serviceguard Extension for RAC Version A.11.19 Release Notes