Monitor the session logs closely. The non-rolling flag changes the orchestration logic: opatchauto will connect to remote nodes via SSH. It will shutdown GI services globally.
export OPATCH_DEBUG=TRUE
When patching a multi-node Oracle Grid Infrastructure or RAC environment, the automation provided by opatchauto is usually a lifesaver. However, encountering can bring your maintenance window to a grinding halt.
To execute successfully in this mode, specific node availability conditions must be met: opatchauto72030 execute in nonrolling mode
Patches one node at a time while others remain active. This minimizes downtime.
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
Look for patch 72030 in the output.
If the execution fails with a binary conflict, you may need to use the opatchauto apply -analyze flag to identify if an existing interim patch must be rolled back before the new RU can be applied.
: Some specific infrastructure patches or configuration changes mandate a non-rolling execution because they cannot coexist with older versions on other nodes. Troubleshooting Common Issues Permission Denied : Ensure the command is executed as root .
# Stop all databases managed by the cluster srvctl stop database -d # Alternatively, let opatchauto manage the GI stack directly Use code with caution. Step 3: Run OPatchAuto with the Non-Rolling Flag Monitor the session logs closely
Non-rolling mode requires Oracle Clusterware (GI) stack components to be stopped completely on the target nodes before certain phases execute. Residual processes (like ohasd.bin or crsd.bin ) cause failures.
In the world of Oracle Database administration, the error OPATCHAUTO-72030: Execute in non-rolling mode
: If a critical error occurs, use the opatchauto rollback command with the -nonrolling flag to revert the changes across the cluster. Non-Rolling upgrade in RAC using opatchauto - Oracle Forums This minimizes downtime