Sometimes, opatchauto may fail, or a session may be improperly locked as "rolling" when it should be "non-rolling". If you encounter issues during patching, especially if the analyze phase fails or indicates wrong mode, you might need to modify the session info. Fixing "Invalid Non-Rolling Session" (e.g., Session F7ET)
The nonrolling mode took over. Instead of the delicate dance of one node at a time, opatchauto laid waste to the entire stack at once, updating the binaries across all nodes in parallel. By 1:30 AM, the terminal finally blinked a green success message. opatchauto72030 execute in nonrolling mode
Extract the new OPatch zip file into both homes as the respective software owner ( grid and oracle ). Verify the version: Sometimes, opatchauto may fail, or a session may
# Execute as root user # /u01/app/19.0.0/grid/OPatch/opatchauto apply /stage/patches/PATCH_ID -nonrolling -analyze Use code with caution. Instead of the delicate dance of one node
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.
Discrepancies within the Oracle Central Inventory ( oraInventory ) across different cluster nodes.
opatchauto /u01/app/ oracle/ product/12.2.0/dbhome_1 -patch 26112314 -nonrolling