My Oracle Support Banner

How to Manage Oracle Grid Infrastructure During Operating System Upgrades (Doc ID 1559762.1)

Last updated on MARCH 24, 2022

Applies to:

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Solaris on SPARC (64-bit)
HP-UX PA-RISC (64-bit)
IBM AIX on POWER Systems (64-bit)
Linux x86-64


Oracle supports the rolling upgrade of the operating system in a cluster when both versions of the operating system are certified with the version of Oracle Database you are running. Note mixed operating system versions are only supported for the duration of an upgrade (i.e., within 24 hours)--the cluster should never be operated with mixed operating systems for an extended period.


The purpose of this note is to outline the steps one may take to manage Oracle Grid Infrastructure during Operating System Upgrade.

Note: When applying OS patches, one must explicitly stop clusterware (crsctl stop crs), apply the desired OS patch(es), relink, and restart Oracle Grid Infrastructure and RDBMS/RAC.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Traditional / Fully Supported Method
 Alternative Method
 Database - RAC/Scalability Community


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.