The error OPATCHAUTO-72030 typically occurs during Oracle Grid Infrastructure (GI) patching when the system is unable to proceed in "rolling" mode (where nodes are patched one by one without total cluster downtime). This message indicates that a non-rolling mode execution is required, often due to a shared home configuration or specific patch requirements. Understanding Error OPATCHAUTO-72030
Root Cause: This error most frequently appears when the OPatchAuto utility detects a shared Grid Infrastructure (CRS) home or a patch that cannot be applied while other nodes are active.
Mechanism: In rolling mode, at least one remote node must be active; however, for shared homes, the utility cannot isolate the local node's binaries for patching without affecting the entire cluster. How to Execute in Non-Rolling Mode
To resolve this, you must stop all services across all nodes and use the -nonrolling flag with OPatchAuto.
Stop All Cluster Resources: Ensure the GI stack and all databases are stopped on all nodes in the cluster.
Execute the Patch Command: Run the command as the root user from the patch directory: # opatchauto apply Use code with caution. Copied to clipboard
Specific Home Option: If you only want to patch a specific home (like the GI home), include the -oh flag:
# opatchauto apply Use code with caution. Copied to clipboard Key Considerations for "Exclusive" Mode
The term "exclusive" in this context usually refers to an exclusive lock or state required for patching shared binaries. Rocky Linux release 8.8 19c rac ru安装 - 墨天轮
The opatchauto command with patch 72030 executed in non‑rolling mode exclusive means you are applying a patch to an Oracle Grid Infrastructure (GI) or Oracle RAC environment where all nodes in the cluster will be patched at the same time, and no other patching or maintenance operation can run concurrently.
Here’s a detailed breakdown:
| Aspect | Rolling mode | Non‑rolling exclusive | |----------------------|-----------------------|---------------------------| | Node downtime | One node at a time | All nodes at once | | Cluster availability | Partial (RAC remains) | Full outage | | Patching time | Longer (node by node) | Shorter (parallel) | | Lock on Oracle Home | Shared (per node) | Exclusive | | Risk | Lower (phased) | Higher (all eggs one basket) | opatchauto72030 execute in nonrolling mode exclusive
Would you like the exact sequence to safely apply patch 72030 in non‑rolling exclusive mode?
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
: Before running the command, manually bring down the GI/RAC stack and all databases on in the cluster. Run the Command : Execute the following as the
#
/u01/app/19.0.0/grid/OPatch/opatchauto apply /soft/35319490 -nonrolling Start the Stack
: Once the patching is complete on all nodes, bring the stack and databases back up. Why this happens Shared Homes
: If your Grid Infrastructure (GI) or Oracle Home is shared across multiple nodes, opatchauto
cannot perform a rolling upgrade because it cannot isolate the home for a single node. Non-Rollable Patches
: Some patches contain changes that are fundamentally incompatible with different nodes running different versions simultaneously (e.g., changes to ASM or shared drivers).
For further verification, you can check the session log file usually located in
The error OPATCHAUTO-72030 typically occurs when you attempt to patch a Shared Grid Infrastructure (GI) Home in "rolling" mode. Because a shared home resides on a shared file system (like ACFS or OCFS2), binaries cannot be updated node-by-node while other nodes are still running from that same home. opatchauto72030 – Likely a typo or specific alias/script
The "nonrolling mode exclusive" execution is the standard requirement for these environments to ensure the shared binaries are modified while the entire stack is down. 1. Error Breakdown: Why OPATCHAUTO-72030 Happens
Trigger: You likely ran opatchauto apply without specifying a mode. By default, opatchauto tries to use rolling mode.
The Conflict: Rolling mode requires shutting down one node, patching it, and bringing it back up while other nodes stay live. In a shared home, you cannot "patch" only one node's binaries because all nodes share the same physical files.
The Message: "Cannot execute in rolling mode, as CRS home is shared. Execute in non-rolling mode." 2. Execution Requirements for Non-Rolling Mode
To resolve this and execute correctly, follow these "exclusive" operational rules: Node Availability:
Local Node: The GI stack must be UP on the node where you initiate the command.
Remote Nodes: The GI stack must be DOWN on all other nodes in the cluster. Privileges: You must execute the command as the root user.
Command Syntax: You must explicitly include the -nonrolling flag:
# Use code with caution. Copied to clipboard (Reference:) 3. Strategic Steps for a Solid Execution Preparation:
Update OPatch to the latest version in both Grid and Database homes.
Check for conflicts using the -analyze flag first: opatchauto apply . Sequence: Stop the GI stack on all remote nodes: crsctl stop crs. Run the opatchauto command on the local node. execute – Instructs opatchauto to apply the patch
The utility will handle stopping the local stack, applying the binary patch to the shared home, and restarting the services. Completion:
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. 4. Key Limitations
Out-of-Place Patching: Note that the -nonrolling option is generally not supported for "out-of-place" patching (using -outofplace), where a new home is cloned.
Downtime: Non-rolling mode implies a complete outage for the duration of the patching on the first node.
Next Steps:If you're ready to proceed, I can help you verify your inventory status or provide the exact pre-check commands for your specific Oracle version. Are you currently on 12c, 19c, or 21c?
The phrase "opatchauto72030 execute in nonrolling mode exclusive" appears to be a specific command or log fragment related to Oracle Grid Infrastructure (GI) or Oracle Database patching using opatchauto (the automatic patching utility for Oracle Clusterware and RAC environments).
Here’s a breakdown of what each part likely means:
opatchauto72030 – Likely a typo or specific alias/script name. The standard command is opatchauto. 72030 might refer to a patch ID (e.g., Oracle patch 72030) or a log identifier. Possibly it's opatchauto run with a patch directory named 72030.
execute – Instructs opatchauto to apply the patch.
in nonrolling mode – For RAC or Oracle Clusterware, "nonrolling mode" means all nodes will be patched at the same time (cluster downtime required), as opposed to "rolling mode" (one node at a time with cluster still available).
exclusive – Likely refers to -exclusive flag or a mode where no other patching or configuration changes can occur simultaneously; often used for certain GI patches or when applying patches that affect clusterware binaries in a non‑rolling fashion.
$ORACLE_HOME/OPatch/opatch version
$ORACLE_HOME/OPatch/opatch lsinventory
$GRID_HOME/OPatch/opatchauto apply -oh $ORACLE_HOME -nonrolling