The error typically occurs during Oracle Grid Infrastructure (GI) patching when opatchauto is executed in rolling mode but encounters a configuration that requires a non-rolling approach. This commonly happens when the Grid Infrastructure home is shared across nodes or when applying a patch that is inherently non-rollable. Direct Answer
When applying Release Updates (RU) or Bundle Patches (BP) to an Oracle RAC environment, administrators often choose between rolling (node-by-node) and non-rolling (all nodes down) methods. The 72030 error code acts as a safety gate. It prevents the patch utility from proceeding when it cannot guarantee the integrity of the cluster state. Common Root Causes
To resolve this issue successfully and ensure complete cluster parity, DBAs must switch strategies and . Root Cause Analysis 1. Shared Cluster Homes ( ORACLE_HOME / Grid Home)
If your Grid Infrastructure home is shared across nodes, binaries cannot be updated on one node while the other is still running from the same disk. opatchauto72030 execute in nonrolling mode exclusive
When OPatchAuto detects a shared home, it throws the following message:
Instead of restarting the entire patching session from scratch, you can instruct OPatchAuto to resume from where it failed, using explicit flags to force non-rolling behavior. Execute the following command as root : $ORACLE_HOME/OPatch/opatchauto resume -nonrolling Use code with caution.
The system is telling you that because your CRS (Cluster Ready Services) home is in a shared location (accessible by all nodes), it cannot be patched in a rolling fashion. The only viable path forward is to execute the operation in non-rolling mode . This is the foundational concept for this article. The error typically occurs during Oracle Grid Infrastructure
Running the command as the wrong user (e.g., oracle instead of root ) or having incorrect permissions on the /tmp directory or inventory.
OPatchAUTO72030 is an Oracle patching operation identifier that appears when using Oracle OPatch/OPatchAUTO to apply patches to Oracle Grid Infrastructure, Oracle Home(s), or database homes. The operation involves applying rolling or nonrolling patches; the message or error referencing OPatchAUTO72030 typically arises when OPatchAUTO is instructed to execute in nonrolling mode with exclusive resource locks, or when a patch cannot be applied in rolling mode and OPatchAUTO switches to or requires nonrolling (exclusive) mode.
Resolving OPATCHAUTO-72030: Executing in Non-Rolling Mode Exclusive The 72030 error code acts as a safety gate
: Ensure an explicit maintenance window is approved since all database and cluster services will be stopped.
To resolve this, you must stop all services across all nodes and use the -nonrolling flag with OPatchAuto .
Look for specific errors like CRS-1158: Clusterware cannot be started as exclusive or ACFS-9459: Failed to unload drivers .
To help provide more specific guidance,g., 19.18, 19.21, 21c).