before the session begins. Only the local node where you execute the command should have its stack up initially, though some documentation suggests stopping all nodes for a clean session. Verify Prerequisites : Ensure you have the latest version of OPatch (often downloaded via Patch 6880880). Execute the Command opatchauto command as the user from your primary node, adding the -nonrolling # opatchauto apply -nonrolling Use code with caution. Copied to clipboard Handle SQL Patching : For non-rollable patches,
: Execute the following as the root user from the patch directory:
The -nonrolling option explicitly instructs OPatchAuto to run in non‑rolling mode.
Oracle Grid Infrastructure and Database patching can occasionally encounter critical failures. One of the most disruptive errors during this process is OPatchAuto Error 72030 . This error typically surfaces when database administrators (DBAs) attempt to apply a Patch Set Update (PSU) or Release Update (RU) in non-rolling mode. opatchauto72030 execute in nonrolling mode high quality
. Follow these critical steps to ensure a high-quality, successful patch application: Stop All Services : Unlike rolling mode, non-rolling patching requires that all remote nodes be stopped
On the , stop the databases and the local Grid Infrastructure stack:
Verify that all processes are down across the entire cluster before proceeding. before the session begins
OPatchAuto error 72030 is fundamentally an automation lifecycle failure. It indicates that the opatchauto core engine cannot systematically validate or execute the transition steps on the local node while keeping remote nodes active. Common root causes include:
Follow this structured approach to resolve the error and successfully complete your non-rolling patch execution. Phase 1: Pre-Verification and Environment Setup
error typically occurs when the tool detects that a rolling update is not feasible—often because the cluster is already in an inconsistent state or the patch itself is "non-rollable". Stop Remote Nodes: Execute the Command opatchauto command as the user
The local GI stack must be active on the node where you are running the command. Execute with Flag: Use the explicit -nonrolling parameter as shown in this 12c GI PSU Guide # opatchauto apply -nonrolling Use code with caution. Copied to clipboard High-Quality Execution Steps
tar -cvzf gi_home_backup.tar.gz /u01/app/19.0.0/grid tar -cvzf db_home_backup.tar.gz /u01/app/oracle/product/19.0.0/dbhome_1 tar -cvzf oraInventory_backup.tar.gz /u01/app/oraInventory Use code with caution.
is an error code thrown by the Oracle OPatchAuto utility when it cannot proceed with a requested operation. The error message typically appears in three sequential lines: