Opatchauto72030 Execute In — Nonrolling Mode [2021]

Technical Paper: Executing OPatchAuto Patch 72030 in Non-Rolling Mode

1. Abstract

Oracle’s opatchauto utility is the standard tool for applying interim patches, bundle patches, and Patch Set Updates (PSU) to Oracle Grid Infrastructure (GI) and Oracle RAC environments. Patch 72030 (used here as a representative patch ID) may require specific application strategies. This paper details the execution of opatchauto for patch 72030 using non-rolling mode — where all cluster nodes are patched simultaneously with downtime. We compare it to rolling mode, provide exact command syntax, pre-requisites, and a step-by-step execution guide.

Little things worth knowing: what does opatchauto actually do?

If you are running this without a shared filesystem (e.g., ACFS or NFS), ensure the patch location is accessible on all nodes, or copy the patch directory to each node and run opatchauto locally with the -local flag in addition to -nonrolling. opatchauto72030 execute in nonrolling mode

: Some patches (like certain JVM updates or major configuration changes) are flagged in their metadata as "non-rollable," forcing this mode. Single-Node GI : In some versions (like 12.2.0.1.10+), opatchauto may require the -nonrolling

To resolve this, you must explicitly use the -nonrolling flag in your command:  This paper details the execution of opatchauto for

This is typically used when you want to minimize the overall patching window duration or if a rolling upgrade is not supported for a specific patch. Pre-requisites

Output you might see:

Follow the Prompts: The utility will guide you through the patch application process. It may ask for confirmation to stop services or apply the patch.