Beginning with Oracle 12c, non-rolling patching requires the GI stack to be up on the local node when the command is invoked. However, the patching process itself involves shutting down all Oracle services as it progresses through each node. Some documentation states "all nodes (including the local node) must be stopped" because the automated process will handle the shutdown as part of its orchestration.
Opatchauto is a powerful tool used in Oracle environments to automate the application of patches to Oracle databases and other Oracle products. It simplifies the patching process, making it more efficient and reducing the risk of human error. One of the key features of opatchauto is its ability to execute in non-rolling mode, which is particularly useful in certain scenarios. In this article, we will explore the concept of executing opatchauto in non-rolling mode, its benefits, and provide a step-by-step guide on how to do it with high quality.
: The GI stack must be up on the local node where you execute the command.
: Always ensure you are using the latest OPatch utility version (e.g., 12.2.0.1.30+ for Oracle 19c) before starting. opatchauto72030 execute in nonrolling mode high quality
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.
Always execute opatchauto apply /path/ -analyze at least 48 hours before the scheduled maintenance window. This catches inventory mismatches and credential issues without causing downtime.
: Check the session logs for any warnings, particularly regarding datapatch or sqlpatch . Beginning with Oracle 12c, non-rolling patching requires the
Monitor the stack initialization until all services show an ONLINE status: /u01/app/19.0.0/grid/bin/crsctl stat res -t Use code with caution.
When you see this in your logs, it indicates that opatchauto is enforcing a full cluster shutdown (non-rolling) to ensure data integrity during the update of Oracle Grid Infrastructure. High-Quality Execution Steps for Non-Rolling Patching
Once the cluster is stable, start your databases if they are not configured to auto-start: # As oracle user srvctl start database -d ORCL Use code with caution. Troubleshooting Ongoing Non-Rolling Failures Opatchauto is a powerful tool used in Oracle
When managing Oracle Grid Infrastructure and Database environments, ensuring a secure and up-to-date system is critical. Oracle provides opatchauto to automate the patching process across multiple Oracle homes, such as Grid Infrastructure (GI) and Database homes. However, scenarios arise—particularly with complex configurations, specific patch requirements, or severe node constraints—where applying patches in a rolling fashion isn't possible.
# $ORACLE_HOME/OPatch/opatchauto apply /path/to/patch/directory -nonrolling Use code with caution.
— Oracle recommends rehearsing patching procedures in a test environment that mirrors production configuration
: For non-rollable patches, databases must be brought back up so you can manually run the Datapatch Utility on the last node to load modified SQL files into the database.