OPATCHAUTO-72030 typically emerges when a Database Administrator attempts to apply an Oracle Grid Infrastructure (GI) patch in rolling mode on a shared CRS home. Because the Grid Infrastructure home is shared across multiple nodes, the standard "one-at-a-time" rolling method is logically impossible; the files on disk cannot be simultaneously patched and running for different nodes. The Patching Story: A Shift to Non-Rolling
The journey of resolving OPATCHAUTO-72030 often follows a predictable path for DBAs: The Default Attempt : Most administrators start with the standard opatchauto apply command, which defaults to rolling mode to avoid downtime. The Roadblock : The system triggers the error:
“Cannot execute in rolling mode, as CRS home is shared. Execute in non-rolling mode”
. This signifies that a cluster-wide outage is mandatory to update the shared binaries. Transition to Non-Rolling : To proceed, the administrator must stop the GI stack on Executing the Solution : The patch is applied using the -nonrolling # As root user
/u01/app/grid/OPatch/opatchauto apply
This command instructs OPatchAuto to handle the shared home correctly by assuming all services are down across the cluster. Key Technical Rules for Non-Rolling Mode Complete Outage
: Unlike rolling updates, a non-rolling update requires all databases and services using that home to be offline. Explicit Flag : You must manually add -nonrolling
to the command line; the utility will not automatically switch modes after a failure. Sequential vs. Parallel
: In a multi-node environment with a shared home, you typically run the non-rolling session from the local node, which may handle remote nodes if configured, but the stack must remain down globally. Shared Home Verification : This error is often a safeguard. If your environment is
supposed to be a shared home, you may need to investigate "Bug 31639069" or check your inventory configuration. exact command syntax for your specific Oracle version, or help reviewing the session logs to confirm why the rolling mode was rejected? Doc ID 2957442.1 OPATCHAUTO-72030 During Opatchauto
In the world of Oracle Database administration, OPATCHAUTO-72030 is a specific error that occurs when a DBA attempts to patch a shared Oracle Grid Infrastructure (GI) home in the default "rolling" mode. Here is the story of how a DBA resolves this challenge. The Midnight Maintenance
It was 2 AM on a Tuesday. Alex, a Senior DBA, was tasked with applying the latest Release Update to a 2-node RAC cluster. The goal was simple: use opatchauto to automate the heavy lifting. Alex typed the standard command: # opatchauto apply /u01/app/oracle/patches/35319490
Within seconds, the terminal spat back a wall of red text:OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared. The Realisation
Alex remembered the rule: shared Grid Infrastructure homes cannot be patched one node at a time while the others stay online. Unlike a standard setup where each node has its own local binaries, a shared home is an "all or nothing" situation. To proceed, the entire cluster had to go dark. The "Non-Rolling" Strategy
To fix this, Alex followed the Non-Rolling protocol, which requires a specific sequence to ensure the shared binaries are updated without corruption:
Preparation: Alex notified the application teams of a complete cluster outage.
Stopping Remote Nodes: Per Oracle’s strict requirements for non-rolling sessions, all remote nodes must be stopped. Alex logged into Node 2 and shut down the stack.
Local Node Status: Interestingly, starting with 12c, the local node (Node 1) must remain up to initiate the session, even in non-rolling mode.
The Correct Command: Alex re-ran the command, but this time added the critical flag:# opatchauto apply /u01/app/oracle/patches/35319490 -nonrolling Success and Verification
The orchestration engine hummed to life. Instead of trying to keep services alive, opatchauto systematically applied the bits across the shared infrastructure. Once the session completed, Alex verified the work:
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.
However, note: There is no standard patch 72030 for Oracle 12.2.0.2.3 in public documentation. You may mean a specific interim patch number or have a typo. I'll provide the generic high-quality procedure for opatchauto in non-rolling mode for a RAC cluster or standalone.
cd /softwares
unzip p36182763_190000_Linux-x86-64.zip
cd 36182763
72030 with your actual patch number.opatchauto (not opatch auto – that's deprecated).OPatchauto Session:
Session id: 12345
Patch location: /stage/72030
Mode: nonrolling
Analysis: passed
Apply: successful on all nodes
OPatchauto completed successfully.
sqlplus / as sysdba <<EOF select patch_id, status from dba_registry_sqlpatch; EOF
OPATCHAUTO-72030 typically emerges when a Database Administrator attempts to apply an Oracle Grid Infrastructure (GI) patch in rolling mode on a shared CRS home. Because the Grid Infrastructure home is shared across multiple nodes, the standard "one-at-a-time" rolling method is logically impossible; the files on disk cannot be simultaneously patched and running for different nodes. The Patching Story: A Shift to Non-Rolling
The journey of resolving OPATCHAUTO-72030 often follows a predictable path for DBAs: The Default Attempt : Most administrators start with the standard opatchauto apply command, which defaults to rolling mode to avoid downtime. The Roadblock : The system triggers the error:
“Cannot execute in rolling mode, as CRS home is shared. Execute in non-rolling mode”
. This signifies that a cluster-wide outage is mandatory to update the shared binaries. Transition to Non-Rolling : To proceed, the administrator must stop the GI stack on Executing the Solution : The patch is applied using the -nonrolling # As root user
/u01/app/grid/OPatch/opatchauto apply
This command instructs OPatchAuto to handle the shared home correctly by assuming all services are down across the cluster. Key Technical Rules for Non-Rolling Mode Complete Outage opatchauto72030 execute in nonrolling mode high quality
: Unlike rolling updates, a non-rolling update requires all databases and services using that home to be offline. Explicit Flag : You must manually add -nonrolling
to the command line; the utility will not automatically switch modes after a failure. Sequential vs. Parallel
: In a multi-node environment with a shared home, you typically run the non-rolling session from the local node, which may handle remote nodes if configured, but the stack must remain down globally. Shared Home Verification : This error is often a safeguard. If your environment is
supposed to be a shared home, you may need to investigate "Bug 31639069" or check your inventory configuration. exact command syntax for your specific Oracle version, or help reviewing the session logs to confirm why the rolling mode was rejected? Doc ID 2957442.1 OPATCHAUTO-72030 During Opatchauto
In the world of Oracle Database administration, OPATCHAUTO-72030 is a specific error that occurs when a DBA attempts to patch a shared Oracle Grid Infrastructure (GI) home in the default "rolling" mode. Here is the story of how a DBA resolves this challenge. The Midnight Maintenance Step 3
It was 2 AM on a Tuesday. Alex, a Senior DBA, was tasked with applying the latest Release Update to a 2-node RAC cluster. The goal was simple: use opatchauto to automate the heavy lifting. Alex typed the standard command: # opatchauto apply /u01/app/oracle/patches/35319490
Within seconds, the terminal spat back a wall of red text:OPATCHAUTO-72030: Cannot execute in rolling mode, as CRS home is shared. The Realisation
Alex remembered the rule: shared Grid Infrastructure homes cannot be patched one node at a time while the others stay online. Unlike a standard setup where each node has its own local binaries, a shared home is an "all or nothing" situation. To proceed, the entire cluster had to go dark. The "Non-Rolling" Strategy
To fix this, Alex followed the Non-Rolling protocol, which requires a specific sequence to ensure the shared binaries are updated without corruption:
Preparation: Alex notified the application teams of a complete cluster outage. EOF select patch_id
Stopping Remote Nodes: Per Oracle’s strict requirements for non-rolling sessions, all remote nodes must be stopped. Alex logged into Node 2 and shut down the stack.
Local Node Status: Interestingly, starting with 12c, the local node (Node 1) must remain up to initiate the session, even in non-rolling mode.
The Correct Command: Alex re-ran the command, but this time added the critical flag:# opatchauto apply /u01/app/oracle/patches/35319490 -nonrolling Success and Verification
The orchestration engine hummed to life. Instead of trying to keep services alive, opatchauto systematically applied the bits across the shared infrastructure. Once the session completed, Alex verified the work:
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.
However, note: There is no standard patch 72030 for Oracle 12.2.0.2.3 in public documentation. You may mean a specific interim patch number or have a typo. I'll provide the generic high-quality procedure for opatchauto in non-rolling mode for a RAC cluster or standalone.
cd /softwares
unzip p36182763_190000_Linux-x86-64.zip
cd 36182763
72030 with your actual patch number.opatchauto (not opatch auto – that's deprecated).OPatchauto Session:
Session id: 12345
Patch location: /stage/72030
Mode: nonrolling
Analysis: passed
Apply: successful on all nodes
OPatchauto completed successfully.
sqlplus / as sysdba <<EOF select patch_id, status from dba_registry_sqlpatch; EOF