When executing opatchauto72030 execute in nonrolling mode, you may encounter:
<path_to_opatchauto> apply /stage/patches/72030 -nonrolling
Key Flags Explained:
Step 4: Monitor the Progress The tool will:
Monitor the logs located typically in:
$ORACLE_BASE/cfgtoollogs/opatchauto/
Step 5: Post-Execution Verification Once the command completes, verify the status of the cluster and the patch inventory.
When applying patches, opatchauto can operate in two main modes:
Navigate to the patch directory and run:
cd /u01/stage/72030
$ORACLE_HOME/OPatch/opatchauto apply . -nonrolling
Important: The correct flag is -nonrolling (not -nonrolling mode – the mode argument is implicit). Many DBAs mistakenly write execute in nonrolling mode, but the actual syntax is:
opatchauto apply <patch_location> -nonrolling
If you are running this without a shared filesystem (e.g., ACFS or NFS), ensure the patch location is accessible on all nodes, or copy the patch directory to each node and run opatchauto locally with the -local flag in addition to -nonrolling.
Use the -nonrolling flag explicitly. The command can be run from any node, but must target all nodes.
For detailed instructions specific to your environment, consult the Oracle documentation and Oracle Support resources. Oracle Support provides comprehensive notes on My Oracle Support (MOS) that guide you through patching processes.
Always follow best practices and consider consulting with Oracle experts or DBAs experienced in patch management for critical systems.
The error code OPATCHAUTO-72030 typically indicates that the utility cannot proceed in rolling mode because the configuration requires a complete cluster shutdown, often due to a shared Oracle Grid Infrastructure (GI) home or a non-rollable patch component. Overview of OPATCHAUTO-72030
When this error occurs, opatchauto explicitly requires the -nonrolling flag to proceed. Non-rolling mode means that the entire stack (GI and Database) will be offline simultaneously across the cluster, rather than being patched one node at a time. Key Requirements for Non-Rolling Mode
To execute successfully in this mode, specific node availability conditions must be met: opatchauto72030 execute in nonrolling mode
Remote Nodes: All remote nodes in the cluster must be stopped/down before starting the session on the local node.
Local Node: The local node where you initiate the command must remain up (the GI stack must be running).
Shared Homes: If your CRS/GI home is shared across nodes, opatchauto will always fail in rolling mode and force a non-rolling execution. Execution Procedure
To resolve the error and apply the patch, use the following syntax as the root user: Stop services on all other nodes in the cluster.
Execute the apply command with the explicit non-rolling flag:
# Use code with caution. Copied to clipboard
Example: /u01/app/19.0.0/grid/OPatch/opatchauto apply /tmp/patch_id -nonrolling. Troubleshooting Common Causes If you still encounter issues after adding the flag:
Cluvfy Issues: Sometimes an outdated cluvfy (Cluster Verification Utility) reports false connectivity failures, triggering this error. Upgrading cluvfy in the GI home can resolve these phantom blocks.
Single Node GI: In single-node Grid Infrastructure environments, Oracle 12.2 and later enforces the use of -nonrolling by default; omitting it will trigger a similar validation error (e.g., OPATCHAUTO-72141). Rocky Linux release 8.8 19c rac ru安装 - 墨天轮
OPatchAuto72030 typically occurs when you attempt to execute a patch in non-rolling
mode, but the environment or the specific patch metadata requires rolling execution (or vice versa).
This report outlines the cause, impact, and resolution for this issue. Executive Summary During the application of a patch using opatchauto , the utility failed with error
. This indicates a conflict between the execution mode specified in the command line and the patch's internal orchestration requirements. Problem Description Error Code: OPatchAuto72030
"The patch(es) do not support the specified execution mode." This usually happens when using the -nonrolling
flag on a patch designed only for rolling updates, or when the Grid Infrastructure (GI) stack state prevents non-rolling execution. Analysis of Causes Patch Metadata Constraints When executing opatchauto72030 execute in nonrolling mode ,
: Some Bundle Patches (BP) or Release Updates (RU) have internal flags that mandate a rolling fashion to maintain high availability. Stack State
: If the Oracle Clusterware is partially active or in a state that opatchauto deems incompatible with a "stop-all" non-rolling approach. Command Syntax : Incorrect use of -nonrolling
on patches that contain components (like JVM updates) which require specific sequences. Resolution Steps 1. Verify Patch Documentation file for the specific Patch ID.
Confirm if "Non-Rolling" is a supported install method for that version.
Note if specific prerequisite steps (like stopping certain services manually) are required. 2. Execute in Rolling Mode (Recommended)
Unless there is a specific architectural reason to down the entire cluster, use the default rolling mode: # Run without the -nonrolling flag ./opatchauto apply
If you must apply it non-rolling (e.g., during a complete blackout window), ensure all services are stopped and use the override if available, though this is generally discouraged for RU patches. 4. Update OPatch and OPatchAuto
Ensure you are using the latest version of the OPatch utility. Download the latest OPatch from My Oracle Support (MOS).
Incompatibility often arises from outdated patching tools trying to read new patch metadata. Conclusion
is a safety mechanism to prevent inconsistent patch states. To proceed, align the command-line arguments with the instructions found in the patch's README or default to a rolling application to ensure cluster integrity. Next Steps: Check your current OPatch version opatch version Review the patch README for the "Installation Method" section. Provide the if you need specific command syntax for that update.
The error code OPATCHAUTO-72030 indicates that opatchauto cannot proceed in the default rolling mode and must be executed in non-rolling mode
. This most commonly occurs because the Grid Infrastructure (GI) or CRS home is shared across nodes or because of specific patch requirements that necessitate a full stack shutdown. Understanding Non-Rolling Mode
Unlike rolling mode, which patches nodes one at a time to maintain availability, non-rolling mode requires a complete outage. Oracle Help Center Node Requirements local node (where the command is run) must have the GI stack remote nodes must have their GI stacks Sequential Order
: In a cluster, patching typically follows a specific sequence: patch the first node, then patch intermediate nodes (2 through ) in parallel, and finally patch the last node. Oracle Forums How to Execute in Non-Rolling Mode
To resolve this error and apply the patch, you must explicitly include the -nonrolling flag in your command. Procedure: Stop GI on Remote Nodes Key Flags Explained:
: Ensure the clusterware and database stacks are stopped on all nodes except the one where you are running opatchauto Run Command : Execute the utility as the user using the following syntax:
#
#
: If the CRS/GI home is installed on a shared file system, rolling updates are not physically possible. Non-Rollable Patches
: Some patches (like certain JVM updates or major configuration changes) are flagged in their metadata as "non-rollable," forcing this mode. Single-Node GI : In some versions (like 12.2.0.1.10+), opatchauto may require the -nonrolling
flag even on single-node environments due to specific bug fixes (e.g., Bug 26367944).
For more detailed troubleshooting, you can refer to the official Oracle Troubleshooting OPatchAuto guide pre-check commands
to verify your cluster status before starting the non-rolling session? Rocky Linux release 8.8 19c rac ru安装 - 墨天轮
A key feature of opatchauto when encountering the OPATCHAUTO-72030 error is its ability to enforce Non-rolling Mode for shared Oracle homes, which ensures cluster integrity by patching all nodes while the services are down. Key Feature: Shared Home Enforcement
In Oracle RAC environments, if the Grid Infrastructure (GI) home is shared across nodes, it cannot be patched using the default "rolling" method (one node at a time while others stay active). The opatchauto utility features a built-in safety check that triggers error OPATCHAUTO-72030 to prevent invalid execution.
To resolve this, you must explicitly use the -nonrolling flag. Benefits of Non-rolling Mode
Speed & Efficiency: Unlike rolling updates that patch sequentially, non-rolling mode allows for parallel patching of nodes two through , significantly reducing the overall maintenance window.
Compatibility: This mode is mandatory for "non-rollable" patches or configurations (like shared homes) where the patch metadata does not support active services on remote nodes.
Automation: Even in non-rolling mode, opatchauto automates the complex sequence of stopping services, applying binary patches, and restarting the stack across the cluster. Execution Requirements When running in non-rolling mode:
Little things worth knowing: what does opatchauto actually do?
This guide assumes a basic familiarity with Oracle patching processes and might need adjustments based on your specific situation. Always consult Oracle documentation or contact Oracle Support for detailed, version-specific instructions.