ps -ef | grep opatch Navigate to the Grid home (or whichever home owns the CRS stack). Typically, opatchauto is run from the Grid home to patch the cluster.
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. opatchauto72030 execute in nonrolling mode exclusive
Introduction In the high-stakes world of Oracle Database administration, patching is a necessary yet often dreaded task. The complexity increases exponentially when dealing with Oracle Grid Infrastructure (GI) and Real Application Clusters (RAC). Oracle provides the opatchauto utility to streamline this process, but within its syntax lies a specific, powerful, and potentially disruptive command: opatchauto72030 execute in nonrolling mode exclusive . ps -ef | grep opatch Navigate to the
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: and keep your crsctl commands ready.
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.
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.