Opatchauto72030 Execute In Nonrolling Mode - Exclusive
OPATCHAUTO-72030
The error typically occurs during Oracle Grid Infrastructure (GI) patching when opatchauto is executed in rolling mode but encounters a configuration that requires a non-rolling approach. This commonly happens when the Grid Infrastructure home is shared across nodes or when applying a patch that is inherently non-rollable. Direct Answer
Non-Rolling Mode Exclusive
$GI_HOME/OPatch/opatchauto72030 execute /path/to/72030 -nonrolling -exclusive opatchauto72030 execute in nonrolling mode exclusive
/u01/app/grid/OPatch/opatchauto apply /path/to/patch -oh /u01/app/grid -nonrolling Use code with caution. Copied to clipboard Always ensure you are using the latest OPatch utility (Patch 6880880) before starting. 3. Common Troubleshooting Tweaks opatchauto72030 execute in nonrolling mode exclusive
Before running in non-rolling mode, ensure the clusterware is ready to be stopped. Manually test the shutdown: # As root crsctl stop crs -f Use code with caution. opatchauto72030 execute in nonrolling mode exclusive
OPATCHAUTO-72030
The error typically occurs during Oracle Grid Infrastructure (GI) patching when opatchauto is executed in rolling mode but encounters a configuration that requires a non-rolling approach. This commonly happens when the Grid Infrastructure home is shared across nodes or when applying a patch that is inherently non-rollable. Direct Answer
Non-Rolling Mode Exclusive
$GI_HOME/OPatch/opatchauto72030 execute /path/to/72030 -nonrolling -exclusive
/u01/app/grid/OPatch/opatchauto apply /path/to/patch -oh /u01/app/grid -nonrolling Use code with caution. Copied to clipboard Always ensure you are using the latest OPatch utility (Patch 6880880) before starting. 3. Common Troubleshooting Tweaks
Before running in non-rolling mode, ensure the clusterware is ready to be stopped. Manually test the shutdown: # As root crsctl stop crs -f Use code with caution.