| Risk | Impact | Mitigation Strategy | | :--- | :--- | :--- | | | High | If CRS fails to stop, the patching aborts. Pre-check for hung processes or locked files. | | Patch Failure | Critical | If patching fails after shutdown, the environment may be left in an inconsistent state. Be prepared to manually restore the GI Home from backup. | | Diskgroup Mount Failure | High | If ASM patches are involved, ASM must come up in the new version. Check ASM alert logs immediately if startup hangs. | | Datapatch Errors | Medium | The binary patch may succeed, but SQL updates might fail. Monitor the datapatch log files post-startup. |
Ensure that the Grid Infrastructure cluster stack is operational on the primary local deployment node (e.g., Node 1). For non-rolling patches, the local node infrastructure must remain active initially to let the installer query parameters from the local cluster registry. Step 3: Bring Down Remote Targets
If you've encountered the error , you aren't alone. This typically occurs during Oracle Grid Infrastructure (GI) patching when the utility detects a configuration that is incompatible with the default "rolling" mode. What is Error OPATCHAUTO-72030?
Because a non-rolling patch requires taking down the entire cluster stack across all nodes, it triggers system-wide downtime. Complete these preparatory tasks before executing the fix: opatchauto72030 execute in nonrolling mode exclusive
: If your patch bundle permits, decouple the Grid Infrastructure patching from the Database patching to isolate infrastructure issues from database workloads.
This article will dissect this command, explain exactly when and why you would use it, walk through the step-by-step execution, and highlight the risks and best practices associated with it.
This error is usually a "wrapper" for a deeper underlying issue. Common culprits include: | Risk | Impact | Mitigation Strategy |
: Run the patch application using the -nonrolling option as the root user: # opatchauto apply -nonrolling Use code with caution. Copied to clipboard
Shuts down the entire cluster before patching.
Always perform a backup of the CRS Home and OCR before applying patches in non-rolling mode. Be prepared to manually restore the GI Home from backup
# As grid user on Node 1 cluvfy comp software -n all -verbose
This is the specific Oracle patch number. In this case, Oracle Patch 72030 is a hypothetical placeholder (though actual patches follow this numeric format). In real-world scenarios, this would be a known Release Update (e.g., RU 19.20.0.0.0) or a One-off patch addressing a specific bug. The number informs opatchauto which set of instructions ( *.xml metadata) to follow.
Always remember: The -exclusive flag locks others out. The -nonrolling flag locks your database out. Plan accordingly, test rigorously, and keep your crsctl commands ready.