The tool expects the GI stack to be in a specific state (usually down or ready for transition). If a resource is stuck or a process refuses to terminate, opatchauto fails.
cd $ORACLE_HOME (Grid home) $ORACLE_HOME/OPatch/opatchauto apply /stage/72030 -nonrolling -exclusive
# As grid user on Node 1 cluvfy comp software -n all -verbose opatchauto72030 execute in nonrolling mode exclusive
The "exclusive" option in non-rolling mode ensures that the patch is applied exclusively to the specified instance, without affecting other instances in a multi-instance environment. This option is particularly useful in RAC (Real Application Clusters) environments where multiple instances of the database are running.
: Run the patch application using the -nonrolling option as the root user: # opatchauto apply -nonrolling Use code with caution. Copied to clipboard The tool expects the GI stack to be
If the patch requires a completely stopped stack, ensure you have run: crsctl stop crs -f on the target nodes. Check Log Files for Specific Conflicts
Cleanup and validation:
Shuts down the entire cluster before patching.
The GI stack must be UP on the node where you initiate the command. This option is particularly useful in RAC (Real
You are instructing the utility to: