Follow this structured protocol to bypass error 72030 and successfully complete your Oracle Grid Infrastructure patching lifecycle. Step 1: Analyze the Opatchauto Log File
If your maintenance window strictly requires all nodes to be down at once, you cannot use the automated opatchauto wrapper. Instead, manually patch the nodes utilizing binary-level opatch . $GRID_HOME/crs/install/rootcrs.sh -prepatch Use code with caution. Apply the Patch via Core OPatch:
OPatchauto session log: /u01/app/oracle/product/19.3.0/dbhome_1/cfgtoollogs/opatchauto/opatchauto_2025-03-15_10-30-00.log Acquiring exclusive access to Oracle home... Exclusive access granted. Applying patch 72030 in non-rolling mode... Node1: Stopping services... Node2: Stopping services... Patch applied successfully. Restarting services... Releasing exclusive access. opatchauto72030 execute in nonrolling mode exclusive
In a shared home configuration, all nodes run from the same set of binaries. Because a "rolling" patch updates one node while others stay active, it is impossible to apply to a shared disk without affecting the active nodes. Step-by-Step Resolution 1. Preparation: Stop Services on All Nodes Unlike rolling patches, non-rolling mode requires the entire cluster stack to be down. Log in as the
To resolve this and execute correctly, follow these "exclusive" operational rules: Follow this structured protocol to bypass error 72030
: When opatchauto evaluates the environment patch properties, it detects the shared configuration alongside certain non-rolling patch attributes. This prompts the utility to enforce an Exclusive Non-Rolling Mode to prevent binary corruptions and cluster split-brain scenarios. 2. Strategic Prerequisites
Once the first node is finished, you must still run the command on the remaining nodes to update the local configuration and inventory, though the actual binary patching of the shared home is already done. $GRID_HOME/crs/install/rootcrs
Evaluate the patch prerequisites by running a simulation (dry run) as the root user:
If an Oracle home component or background process (like an orphaned tfactl or management agent process) keeps a file handle open, OPatchAuto will fail to overwrite binaries.
Always update the to the latest version before applying a Release Update (RU). Most opatchauto failures are caused by an outdated Opatch executable trying to parse new patch metadata. If you'd like to refine this for a specific environment: Tell me your Oracle version (e.g., 19c, 21c). Share any specific error codes you're seeing. Mention if you're using a Shared Oracle Home .