Note that the -nonrolling option is generally not supported for "out-of-place" patching (using -outofplace ), where a new home is cloned.
Ensure you are executing the command with root privileges from a directory where the home owner has write permissions. Analyze First: Always use the
Before proceeding in non-rolling mode, ensure all remote nodes are down. Check Patch Metadata: Review the Patch README to confirm if the patch is inherently non-rollable. Run as Root:
OPATCHAUTO-72030 typically occurs when you attempt to apply a patch in rolling mode, but the environment requires it to be applied in non-rolling mode . This most commonly happens because the CRS home is shared among nodes, which prevents patching one node at a time. To resolve this, you must explicitly use the -nonrolling flag with your opatchauto Oracle Forums Execution Steps Shutdown All Nodes
If you use Oracle ACFS (Advanced Cluster File System), verify that your operating system kernel version is fully certified with the specific RU version you are installing. Unloading incompatible ACFS kernel drivers is a primary cause of exclusive mode crashes. opatchauto72030 execute in nonrolling mode exclusive
To run OPatchAuto in non-rolling mode, you must explicitly specify the -nonrolling option.
The GI stack must be DOWN on all other nodes in the cluster. Privileges: You must execute the command as the root user.
If the analysis succeeds, you can proceed with the patch application. The command is nearly identical but without the -analyze flag.
To fix this, you must explicitly instruct the patch utility to run in combined with an exclusive cluster state. Note that the -nonrolling option is generally not
Because of the shared CRS home, you must halt all nodes to ensure no processes are accessing the shared files.
The opatchauto utility is the next-generation patching tool for Oracle Grid Infrastructure and RAC databases. Unlike the legacy opatch (which patches a single Oracle home), opatchauto understands cluster topologies. It can patch both the Grid home (CRS/ASM) and all database homes across all nodes in a cluster.
: Verify the central inventory is consistent across all nodes. 🚀 Execution Steps 1. Prepare the Software
The most detailed data lives in the Grid Infrastructure alert and trace directories. Check the automated script log: Check Patch Metadata: Review the Patch README to
If your patching session aborts with the 72030 error, follow this structured, production-tested workflow to resolve the issue. 1. Verify and Clean Up Abandoned Locks
The opatchauto utility is Oracle’s automation tool for patching GI (Grid Infrastructure) and RAC (Real Application Clusters) homes. It orchestrates the complex process of stopping services, applying binary patches, and restarting services across multiple nodes.
Note: Depending on your specific Oracle Grid Infrastructure version (e.g., 19c, 21c), the script might be rootcrs.sh instead of clsrsc.sh .
