Serviceguard Extension for RAC Version A.11.20 Release Notes, April 2013

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
allow you to keep the node up and running in the cluster while you upgrade the other
nodes. You will still need to investigate and solve the problems on this node before the
cluster upgrade can complete. If you decide to perform a hot recovery, proceed as follows:
a. Halt the packages and restart them on another node.
b. Halt the node.
c. Reboot the node from the original root disk (contains the pre-upgrade versions of
HP-UX and Serviceguard).
d. Restart the cluster on the node, using Serviceguard Manager or cmrunnode (1m).
• If the applications do not function properly and this is the last node to be upgraded, you
cannot revert to the previous release on just this node. You must either solve the problems
with this release on this node, or revert the entire cluster to the previous release by halting
the cluster (cmhaltcl), rebooting each node from its original (pre-upgrade) root disk,
and restarting the cluster (cmruncl).
• If the applications are functioning properly, continue with the next step.
13. Repeat the above steps for each node in the cluster.
If the cluster fails before the rolling upgrade is complete (because of a catastrophic power
failure, for example), you can restart the cluster by running cmruncl (1m) on a node which
has been upgraded to the latest version of the software.
Performing a Non-Rolling Upgrade Using DRD
Limitations of Non-Rolling Upgrades using DRD
CAUTION: Stricter limitations apply to an upgrade to A.11.20. Do not proceed with an upgrade
to A.11.20 until you have read and understood the “Special Considerations for Upgrade to
Serviceguard A.11.20” in Appendix D of the latest version of Managing Serviceguard.
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
17).
In addition, all the limitations for non-rolling upgrades listed in Appendix A of Using Serviceguard
Extension for RAC also apply to non-rolling upgrades using DRD. You should also read the section
on “Non-Rolling Software Upgrades” in that appendix before you proceed.
Compatibility Information and Installation 21