rootcrs.pl -prepatch: CRS-1159: The cluster cannot be set to rolling patch mode because Oracle Clusterware is not active on at least one remote node.
(Doc ID 1600765.1)
Last updated on JULY 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterInformation in this document applies to any platform.
Symptoms
Applying a 12c GI patch with opatchauto, it fails to stop CRS:
# /ocw/c101/OPatch/opatchauto apply /home/grid/tmp/17272829 -oh /ocw/c101
....
Patch Validation: Successful
Stopping CRS ... Failed
Command "/usr/bin/perl /ocw/c101/crs/install/rootcrs.pl -prepatch" execution failed:
Died at /ocw/c101/crs/install/crspatch.pm line 666.
For more details, please refer to the log file "/ocw/c101/cfgtoollogs/opatchauto/17272829/opatch_gi_2013-11-03_19-51-49_deploy.debug.log".
Apply Summary:
Following patch(es) failed to be installed:
GI Home: /ocw/c101: 17027533, 17077442, 17303297
opatchauto failed with error code 2.
From /ocw/c101/cfgtoollogs/opatchauto/17272829/opatch_gi_2013-11-03_19-51-49_deploy.debug.log
COMMAND EXECUTION FAILURE :
Using configuration parameter file: /ocw/c101/crs/install/crsconfig_params
Oracle Clusterware active version on the cluster is [12.1.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [0].
CRS-1159: The cluster cannot be set to rolling patch mode because Oracle Clusterware is not active on at least one remote node.
CRS-4000: Command Start failed, or completed with errors.
2013/11/03 19:52:31 CLSRSC-430: Failed to start rolling patch mode
ERROR:
Died at /ocw/c101/crs/install/crspatch.pm line 666.
2013-11-03_19-52-32 :
Failed to run this command :
/usr/bin/perl /ocw/c101/crs/install/rootcrs.pl -prepatch
oracle.opatch.gi.RunExecutionSteps.runGenericShellCommands(RunExecutionSteps.java:724)
oracle.opatch.gi.RunExecutionSteps.processAllSteps(RunExecutionSteps.java:183)
oracle.opatch.gi.GIPatching.processPatchingSteps(GIPatching.java:747)
oracle.opatch.gi.OPatchautoExecution.main(OPatchautoExecution.java:101)
Command "/usr/bin/perl /ocw/c101/crs/install/rootcrs.pl -prepatch" execution failed:
Died at /ocw/c101/crs/install/crspatch.pm line 666.
From <GI_HOME>/cfgtoollogs/crsconfig/crspatch_<node>_<timestamp>.log
2013-11-03 19:52:31: Command output:
> CRS-1159: The cluster cannot be set to rolling patch mode because Oracle Clusterware is not active on at least one remote node.
> CRS-4000: Command Start failed, or completed with errors.
>End Command output
2013-11-03 19:52:31: Executing cmd: /ocw/c101/bin/clsecho -p has -f clsrsc -m 430
2013-11-03 19:52:31: Command output:
> CLSRSC-430: Failed to start rolling patch mode
>End Command output
2013-11-03 19:52:31: Executing cmd: /ocw/c101/bin/clsecho -p has -f clsrsc -m 430
2013-11-03 19:52:31: Command output:
> CLSRSC-430: Failed to start rolling patch mode
>End Command output
2013-11-03 19:52:31: CLSRSC-430: Failed to start rolling patch mode
2013-11-03 19:52:31: ###### Begin DIE Stack Trace ######
2013-11-03 19:52:31: Package File Line Calling
2013-11-03 19:52:31: --------------- -------------------- ---- ----------
2013-11-03 19:52:31: 1: main rootcrs.pl 211 crsutils::dietrap
2013-11-03 19:52:31: 2: crspatch crspatch.pm 666 main::__ANON__
2013-11-03 19:52:31: 3: crspatch crspatch.pm 612 crspatch::performPrePatch
2013-11-03 19:52:31: 4: crspatch crspatch.pm 114 crspatch::crsPrePatch
2013-11-03 19:52:31: 5: main rootcrs.pl 220 crspatch::new
2013-11-03 19:52:31: ####### End DIE Stack Trace #######
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |