Using Serviceguard Extension for RAC, 6th Edition, April 2008

• You can perform a rolling upgrade only on a configuration that has not been
modified since the last time the cluster was started.
• Rolling upgrades are not intended as a means of using mixed releases of
Serviceguard and SGeRAC within the same cluster. SGeRAC requires the
compatible version of Serviceguard. Upgrade all cluster nodes as quickly as possible
to the new release level.
For more information on support, compatibility, and features for SGeRAC, refer
to the Serviceguard and Serviceguard Extension for RAC Compatibility and Feature
Matrix, located at http://docs.hp.com -> High Availability -> Serviceguard
Extension for RAC
• You cannot delete Serviceguard/SGeRAC software (via swremove) from a node
while the cluster is in the process of a rolling upgrade.
Non-Rolling Software Upgrades
A non-rolling upgrade allows you to perform a software upgrade from any previous
revision to any higher revision or between operating system versions. For example,
you may do a non-rolling upgrade from SGeRAC A.11.14 on HP-UX 11i v1 to A.11.16
on HP-UX 11i v2, given both are running the same architecture.
The cluster cannot be running during a non-rolling upgrade, therefore it is necessary
to halt the entire cluster in order to perform the upgrade. The next section describes the
steps for doing a non-rolling software upgrade.
Steps for Non-Rolling Upgrades
Use the following steps for a non-rolling software upgrade:
1. Halt Oracle (RAC, CRS, Clusterware, OPS) software on all nodes in the cluster.
2. Halt all nodes in the cluster.
# cmhaltcl -f
3. If necessary, upgrade all the nodes in the cluster to the new HP-UX release.
4. Upgrade all the nodes in the cluster to the new Serviceguard/SGeRAC release.
5. Restart the cluster. Use the following command:
# cmruncl
6. If necessary, upgrade all the nodes in the cluster to the new Oracle (RAC, CRS,
Clusterware, OPS) software release.
7. Restart Oracle (RAC, CRS, Clusterware, OPS) software on all nodes in the cluster
and configure the Serviceguard/SGeRAC packages and Oracle as needed.
Limitations of Non-Rolling Upgrades
The following limitations apply to non-rolling upgrades:
• Binary configuration files may be incompatible between releases of Serviceguard.
Do not manually copy configuration files between nodes.
• It is necessary to halt the entire cluster when performing a non-rolling upgrade.
176 Software Upgrades