Serviceguard Extension for RAC Version A.11.20 Release Notes - (August 2011)

IMPORTANT: Not all paths that are supported for upgrade are supported for an upgrade using
DRD, and there are additional requirements and restrictions for paths that are supported.
Do not proceed until you have read the “Announcements”, “Compatibility”, and “Installing
Serviceguard” sections of the latest version of the Serviceguard release notes and the corresponding
sections of these SGeRAC release notes. Make sure your cluster meets the current requirements,
and take any necessary preparation steps as instructed in the release notes.
You must also make sure you have read and understood the “Restrictions for DRD Upgrades” (page
16).
In addition, all the limitations for rolling upgrades listed in Appendix A of Using Serviceguard
Extension for RAC also apply to rolling upgrades using DRD. You should also read the section on
“Rolling Software Upgrades” in that appendix before you proceed.
Before You Start
IMPORTANT: If you need to upgrade Oracle software, consult Oracle documentation.
• Make sure you plan sufficient system capacity to allow moving the packages from node to
node during the process without an unacceptable loss of performance.
• Make sure you have read and understood the “Restrictions for DRD Upgrades” (page 16),
and that your cluster meets the prerequisites.
• Make sure that you have downloaded the latest DRD software and are thoroughly familiar
with the DRD documentation. See “Rolling Upgrade Using DRD” (page 16) for more information.
• There are some restrictions on where the install depot can reside. Make sure you will be
upgrading the clone disk from a supported location. See “Restrictions for DRD Upgrades”
(page 16).
Running the Rolling Upgrade
1. On the node you want to upgrade, edit /etc/rc.config.d/cmcluster to include the
following line:
AUTOSTART_CMCLD = 0
This value will be replicated on the clone root disk and will keep the upgraded node from
automatically rejoining the cluster when it reboots.
2. Create a clone root disk for the node you want to upgrade.
3. Upgrade the clone disk to the new HP-UX release (if necessary), including Serviceguard (using
drd runcmd update-ux), or upgrade Serviceguard alone (using drd runcmd
swinstall).
4. Upgrade the clone disk to the new SGeRAC release.
5. Halt Oracle (RAC, Clusterware) on the node.
6. Halt the node. You can do this in Serviceguard Manager, or use the cmhaltnode (1m)
command. This will cause the node’s packages to start up on an adoptive node.
7. Reboot the node from the updated clone root disk.
8. Edit the /etc/rc.config.d/cmcluster file to include the following line:
AUTOSTART_CMCLD = 1
9. Restart the cluster on the upgraded node, using Serviceguard Manager or cmrunnode (1m).
10. Restart Oracle (RAC, Clusterware) on the upgraded node.
11. Move the packages back to the upgraded node.
12. Verify that the applications are functioning properly.
• If the applications do not function properly and this is not the last node to be upgraded,
you can revert to the previous release on this node. This is called hot recovery, and it will
20 Serviceguard Extension for RAC Version A.11.20 Release Notes