Run the following command from the patch directory on :
Oracle, opatchauto, and Grid Infrastructure are trademarks of Oracle Corporation. This article is for educational purposes and does not constitute official Oracle documentation.
During a non-rolling session, the console will report the following sequence: Init Phase : Validates requirements on all nodes. : Stops services on all nodes. : Applies binary patches while the stack is down. Startup/Online : Restarts services. : Runs post-patch actions like on the database. Oracle Help Center Troubleshooting Common Pitfalls OPATCHAUTO-72141: Execute opatchauto in non-rolling mode. opatchauto72030 execute in nonrolling mode high quality
tar -cvzf gi_home_backup.tar.gz /u01/app/19.0.0/grid tar -cvzf db_home_backup.tar.gz /u01/app/oracle/product/19.0.0/dbhome_1 tar -cvzf oraInventory_backup.tar.gz /u01/app/oraInventory Use code with caution.
Note: The command will apply the patch to both the Grid Infrastructure Home and the Database Home(s) in one session. Step 3: Monitor the Log Files Run the following command from the patch directory
Are you patching a or a Single-Node GI (Oracle Restart) setup?
# Verify the inventory applied patches $GI_HOME/OPatch/opatch lsinventory -detail # Start the cluster stack if it did not auto-start $GI_HOME/bin/crsctl start cluster -all # Check final functionality $GI_HOME/bin/crsctl check crs Use code with caution. Best Practices for "High-Quality" Non-Rolling Patching : Stops services on all nodes
Step 2: Binary PatchingIn non-rolling mode, you can apply the patch to the binaries while the services are down. Navigate to the directory where you unzipped the patch.
Because non-rolling mode updates the entire infrastructure together, manually stop all resources to prevent forced terminations.