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.
before the session begins. Only the local node where you execute the command should have its stack up initially, though some documentation suggests stopping all nodes for a clean session. Verify Prerequisites : Ensure you have the latest version of OPatch (often downloaded via Patch 6880880). Execute the Command opatchauto command as the user from your primary node, adding the -nonrolling # opatchauto apply -nonrolling Use code with caution. Copied to clipboard Handle SQL Patching : For non-rollable patches, opatchauto72030 execute in nonrolling mode high quality
I understand you're looking for high-quality, full-content guidance on executing opatchauto for Oracle Grid Infrastructure/Home version 12.2.0.2.3? (72030 likely refers to patch 72030? Let me clarify the correct usage. Beginning with Oracle 12c, non-rolling patching requires the
$ORACLE_HOME/OPatch/ocm/bin/emocmrsp -output /tmp/ocm.rsp before the session begins
Execute the post-patch configuration script with the force unlock flag to clear orphaned execution variables: