Last updated on NOVEMBER 02, 2013
Applies to:Oracle Database - Enterprise Edition - Version 188.8.131.52 and later
Information in this document applies to any platform.
There are two methods for upgrading Oracle Grid Infrastructure (Patch Set or version upgrades), including Oracle Clusterware and Oracle Automatic Storage Management (ASM):
1. The rolling method
This is the Oracle recommended method to upgrade Oracle Clusterware / Oracle Grid Infrastructure.
As the term 'rolling' implies, using this method, Oracle Grid Infrastructure is upgraded one node at a time in order to achieve maximum availability. This method requires Oracle Grid Infrastructure to be running on all nodes at upgrade time. It needs to run specifically on the node, on which Oracle Universal Installer (OUI) is run (also referred to as the 'local node') and on all nodes where rootupgrade.sh is executed.
2. The non-rolling method
This is an alternative method to upgrade Oracle Clusterware / Oracle Grid Infrastructure.
As the term 'non-rolling" implies, using this method requires that Oracle Grid Infrastructure is not running on any node in the cluster when the upgrade is performed. The non-rolling approach is typically discouraged, as it leads to a full downtime of Oracle Grid Infrastructure, including all resources and Oracle Databases that it might host. However, if downtime is acceptable or inevitable due to other maintenance operations, or the upgrade to be performed addresses a fix that prevents smooth rolling upgrades, the non-rolling method can be performed as a valid alternative.
This paper describes how to perform a non-rolling upgrade of Oracle Grid Infrastructure.
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