Using Serviceguard Extension for RAC, 3rd Edition, May 2006

Software Upgrades
Rolling Software Upgrades
Appendix A208
NOTE It is optional to set this parameter to “1”. If you want the node to join
the cluster at boot time, set this parameter to “1”, otherwise set it to
“0”.
6. Restart the cluster on the upgraded node (if desired). You can do this
in Serviceguard Manager, or from the command line, issue the
Serviceguard cmrunnode command.
7. Restart Oracle (RAC, CRS, Clusterware, OPS) software on the local
node.
8. Repeat steps 1-7 on the other nodes, one node at a time until all
nodes have been upgraded.
NOTE Be sure to plan sufficient system capacity to allow moving the
packages from node to node during the upgrade process to maintain
optimum performance.
If a cluster fails before the rolling upgrade is complete (perhaps because
of a catastrophic power failure), the cluster could be restarted by
entering the cmruncl command from a node which has been upgraded to
the latest revision of the software.
Keeping Kernels Consistent
If you change kernel parameters or perform network tuning with ndd as
part of doing a rolling upgrade, be sure to change the parameters to the
same values on all nodes that can run the same packages in a failover
scenario. The ndd command allows the examination and modification of
several tunable parameters that affect networking operation and
behavior.