For many DBAs, this string of keywords looks like a cryptic incantation. However, understanding each component— opatchauto , 72030 , execute , nonrolling , mode , and exclusive —is critical for successful patching, especially when applying Database Release Updates (RUs) or Bundle Patches.
tail -f $GRID_HOME/cfgtoollogs/opatchauto/opatchauto-*.log After the command completes successfully: opatchauto72030 execute in nonrolling mode exclusive
Always remember: The -exclusive flag locks others out. The -nonrolling flag locks your database out. Plan accordingly, test rigorously, and keep your crsctl commands ready. For many DBAs, this string of keywords looks
When used correctly—following rigorous pre-checks, backups, and vendor guidelines—it is a powerful tool to apply complex, cross-node patches that rolling mode cannot handle. When used carelessly, it is a fast track to a weekend-long outage. The -nonrolling flag locks your database out
OPatchauto session is acquiring exclusive mode... Successfully acquired exclusive lock on home. Validation in progress... Shutting down Oracle Clusterware stack on all nodes... Node1: CRS stopped. Node2: CRS stopped. Executing postpatch SQL scripts in exclusive mode... Patch 72030 executed successfully. opatchauto creates a log directory: $GRID_HOME/cfgtoollogs/opatchauto/ Tail the most recent log:
Before your next patch cycle, practice this command in a lab, analyze the logs, and document exactly how long the execute phase takes for your specific workload. Your future self will thank you during the next critical security update. Disclaimer: Oracle, RAC, and Grid Infrastructure are trademarks of Oracle Corporation. Always refer to the official Oracle Support document for your specific patch number.
cd $ORACLE_HOME (Grid home) $ORACLE_HOME/OPatch/opatchauto apply /stage/72030 -nonrolling -exclusive – notice I changed execute to apply . Why? In modern Oracle versions (12.2+), the execute command is often deprecated or merged into apply . The apply command with nonrolling exclusive will run the scripts automatically. However, if the patch documentation explicitly says opatchauto execute , then use it exactly as documented.