# Syntax for applying the patch to both GI and DB homes in non-rolling mode /OPatch/opatchauto apply /path/to/patch_directory -nonrolling Use code with caution. Step 4: Validate the Execution
Once the environment is clean, the software homes are verified, and the stacks are down, execute the opatchauto command with proper syntax. Always execute this command as the user:
Unlike standard patching, the tool will perform the following automated actions across the cluster: opatchauto72030 execute in nonrolling mode
Unzip the patch files into a local directory on each node (e.g., /tmp/patch/ ) rather than using a shared ACFS or NFS mount, which can introduce locking latencies during non-rolling shutdowns.
Manually test passwordless SSH connection to all cluster nodes (including the local node itself using its short name, fully qualified domain name, and IP address): ssh node1 date ssh node2 date Use code with caution. # Syntax for applying the patch to both
Non-rolling mode requires flawless, passwordless SSH connectivity for the root user across all cluster nodes. If SSH prompts for a password, opatchauto will fail immediately.
Check the specific README documentation for the patch bundle you are trying to apply. Verify whether the patch explicitly mandates a non-rolling execution.If the README states that rolling mode is not supported for this specific update, you must explicitly tell the utility to run in non-rolling mode. Step 3: Analyze the Detailed Log Files Manually test passwordless SSH connection to all cluster
It then patches the remaining nodes () in parallel.