Follow these sequential steps to safely apply your Oracle Grid Infrastructure or RAC patch using non-rolling mode parameters. 1. Complete Critical Prerequisites
# As root user /export/home/grid/OPatch/opatchauto apply /path/to/72030 -analyze -nonrolling
: Ensure the GI stack and all databases are stopped on all nodes in the cluster. opatchauto72030 execute in nonrolling mode exclusive
To fully grasp the remedy for the 72030 error, it is necessary to understand the fundamental differences between rolling and non-rolling modes.
Stop all databases running out of the Oracle Homes across all nodes: srvctl stop database -d Use code with caution. Follow these sequential steps to safely apply your
$GRID_HOME/OPatch/opatch apply Use code with caution.
Note: These are generic steps; always follow the specific patch README. To fully grasp the remedy for the 72030
An existing interim patch is incompatible with the new bundle, causing the "exclusive" session to abort.
By default, opatchauto applies patches in , which allows nodes to be patched one by one without total cluster downtime. However, certain patches or configurations (such as shared CRS homes ) are not "rollable". When opatchauto detects this, it throws the following message:
To execute OPatchauto72030 in non-rolling mode exclusive, follow these steps:
: Confirm that the OPatch utility version matches or exceeds the minimum version specified in the patch bundle README . Resolution: Executing in Non-Rolling Mode