Oracle Clusterware (CRS or GI) Rolling Upgrades
Last updated on JANUARY 22, 2018
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 184.108.40.206 [Release 10.1 to 12.1]
Information in this document applies to any platform.
The purpose of this document is to provide information about the Oracle Clusterware (formerly CRS)
rolling upgrade feature and how to install a patchset or major release without Oracle Clusterware downtime.
While Oracle generally supports rolling upgrades for Oracle Clusterware, Oracle does not support
'slow, delayed, or extended' rolling upgrades, whereby any node in the cluster remains at the older
version for an extended period of time.
Once the rolling upgrade is initiated, by design the expectation would be that the upgrade rapidly
rolls through each node in the cluster and finishes within 24 hours.
While fully operational, the cluster will provide some restricted functionally during the time of
the rolling upgrade. For example: Oracle Clusterware will not accept the creation of new cluster
resources during the upgrade. ASM (if used in the cluster) will not perform an automatic
re-balancing until all nodes in the cluster have been upgraded successfully.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms