In a non-rolling patching session, the patch is applied by taking the entire cluster offline. The process, especially from 12c onward, is orchestrated in phases:
Ensure the system configurations are coherent across the cluster.
In non‑rolling mode, the utility will stop the entire stack, but you can also pre‑stop:
: Change to the directory where patch 72030 is located.
If a previous rolling attempt failed with OPATCHAUTO-72030, the central inventory lock might still be active. opatchauto72030 execute in nonrolling mode
A desynchronized Central Inventory ( oraInventory ) across the cluster nodes causes the pre-check validation to flag false mismatches.
The entire cluster or specific multi-node services must be shut down simultaneously. The patch is applied across all nodes at the same time. Certain patches—such as major clusterware upgrades, specific operating system changes, or structural database updates—mandate non-rolling execution.
The command opatchauto72030 execute in nonrolling mode seems to be a simplified query for applying patch 72030 using opatchauto in non-rolling mode. By following the steps outlined above, you should be able to apply the patch effectively. Always refer to the official Oracle documentation for the most accurate and detailed instructions.
Run opatch apply (following the patch readme instructions for manual steps). Run the necessary post-install scripts. In a non-rolling patching session, the patch is
You must use non-rolling mode when the Patch README explicitly states that the patch is not RAC-rolling applicable. This is common for: Major Grid Infrastructure updates. Security patches that modify shared resources. Complex bugs requiring a complete cluster restart. 2. Prerequisites for Non-Rolling Patching
Oracle frequently updates the patching engine to handle complex non-rolling transitions.
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
If you see the error OPATCHAUTO-72085 , it is because the patch cannot be applied in rolling mode. Simply add -nonrolling to your existing command. If a previous rolling attempt failed with OPATCHAUTO-72030,
If you are encountering specific error codes (like "opatchauto72030") or need help with a particular version of the database, please provide the error logs, and I can assist with a more specific solution. 12c Patching Resume with Nonrolling Option While Analyze
Remember:
Look for a line that says: “Rolling mode is not possible. Only non‑rolling mode is supported.”
Log in as the user. Navigate to the directory where the patch is unzipped. Execute opatchauto using the -nonrolling parameter.
Back up your existing OPatch directory inside both the GI Home and DB Home.