Opatchauto Fails With Error - "CRS-1158: There was an error setting the cluster to rolling patch mode"
(Doc ID 2710630.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and laterInformation in this document applies to any platform.
Symptoms
Opatchauto fails as below when trying to apply 12.1.0.2 JUL 2020 PSU GI + DB on a RAC node in a 2node RAC config.
//From <GI_HOME>/ccfgtoollogs/optach/error_opatch.txt
====================
Bringing down CRS service on home /<GI_HOME>
Prepatch operation log file location: /<GI_HOME>/cfgtoollogs/crsconfig/crspatch_<Node1>_2020-09-11_01-27-01PM.log
Failed to bring down CRS service on home /<GI_HOME>
Execution of [GIShutDownAction] patch action failed, check log for more details. Failures:
Patch Target : <Node1>->/<GI_HOME> Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /<GI_HOME>, host: <Node1>.
Command failed: /<GI_HOME>/perl/bin/perl -I/<GI_HOME>/perl/lib -I/<GI_HOME>/opatchautocfg/db/dbtmp/bootstrap_<Node1>/patchwork/crs/install /<GI_HOME>/opatchautocfg/db/dbtmp/bootstrap_<Node1>/patchwork/crs/install/rootcrs.pl -prepatch
Command failure output:
Using configuration parameter file: /<GI_HOME>/opatchautocfg/db/dbtmp/bootstrap_<Node1>/patchwork/crs/install/crsconfig_params
Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [1856731013].
CRS-1158: There was an error setting the cluster to rolling patch mode.<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
CRS-4000: Command Start failed, or completed with errors.<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2020/09/11 13:27:03 CLSRSC-430: Failed to start rolling patch mode
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.
OPatchauto session completed at Fri Sep 11 13:27:05 2020
Time taken to complete the session 11 minutes, 5 seconds
//From <GI_HOME>/ccfgtoollogs/optach/crspatch_<Node1>_2020-09-11_01-27-01PM.log
/<GI_HOME>/bin/crsctl start rollingpatch>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2020-09-11 13:27:03: Command output:
> CRS-1158: There was an error setting the cluster to rolling patch mode.>>>>>>>>>>>>>>>>>>>>>>>
> CRS-4000: Command Start failed, or completed with errors.
>End Command output
2020-09-11 13:27:03: Executing cmd: /<GI_HOME>/bin/clsecho -p has -f clsrsc -m 430
2020-09-11 13:27:03: Executing cmd: /<GI_HOME>/bin/clsecho -p has -f clsrsc -m 430
2020-09-11 13:27:03: Command output:
> CLSRSC-430: Failed to start rolling patch mode
>End Command output
2020-09-11 13:27:03: CLSRSC-430: Failed to start rolling patch mode
2020-09-11 13:27:03: ###### Begin DIE Stack Trace ######
2020-09-11 13:27:03: Package File Line Calling
2020-09-11 13:27:03: --------------- -------------------- ---- ----------
2020-09-11 13:27:03: 1: main rootcrs.pl 267 crsutils::dietrap
2020-09-11 13:27:03: 2: crspatch crspatch.pm 808 main::__ANON__
2020-09-11 13:27:03: 3: crspatch crspatch.pm 727 crspatch::performPrePatch
2020-09-11 13:27:03: 4: crspatch crspatch.pm 207 crspatch::crsPrePatch
2020-09-11 13:27:03: 5: main rootcrs.pl 276 crspatch::new
2020-09-11 13:27:03: ####### End DIE Stack Trace #######
2020-09-11 13:27:03: ROOTCRS_PREPATCH checkpoint has failed
2020-09-11 13:27:03: ckpt: -ckpt -oraclebase /<ORA_BASE> -chkckpt -name ROOTCRS_PREPATCH
2020-09-11 13:27:03: Invoking "/<GI_HOME>/bin/cluutil -ckpt -oraclebase /<ORA_BASE> -chkckpt -name ROOTCRS_PREPATCH"
2020-09-11 13:27:03: trace file=/<ORA_BASE> /crsdata/<Node1>/crsconfig/cluutil6
//From incident node,softwarepatch query fails as below.
[+ASM2] crsctl query crs softwarepatch
CRS-4467: Error code 8 in retrieving the software patch level for host <Node2>>>>>>>>>>>>>>>>>>>>
CRS-1191: There was an error retrieving the Oracle Clusterware software patch level.
CRS-4000: Command Query failed, or completed with errors.
cluvfy comp software -n <Node1>,<Node2> -verbose
Verifying software
Check: Software
0 files verified>>>>>>>>>>>>>>>>>>>>>>>>>>
Software check passed
Verification of software was successful.
====================
Bringing down CRS service on home /<GI_HOME>
Prepatch operation log file location: /<GI_HOME>/cfgtoollogs/crsconfig/crspatch_<Node1>_2020-09-11_01-27-01PM.log
Failed to bring down CRS service on home /<GI_HOME>
Execution of [GIShutDownAction] patch action failed, check log for more details. Failures:
Patch Target : <Node1>->/<GI_HOME> Type[crs]
Details: [
---------------------------Patching Failed---------------------------------
Command execution failed during patching in home: /<GI_HOME>, host: <Node1>.
Command failed: /<GI_HOME>/perl/bin/perl -I/<GI_HOME>/perl/lib -I/<GI_HOME>/opatchautocfg/db/dbtmp/bootstrap_<Node1>/patchwork/crs/install /<GI_HOME>/opatchautocfg/db/dbtmp/bootstrap_<Node1>/patchwork/crs/install/rootcrs.pl -prepatch
Command failure output:
Using configuration parameter file: /<GI_HOME>/opatchautocfg/db/dbtmp/bootstrap_<Node1>/patchwork/crs/install/crsconfig_params
Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [1856731013].
CRS-1158: There was an error setting the cluster to rolling patch mode.<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
CRS-4000: Command Start failed, or completed with errors.<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
2020/09/11 13:27:03 CLSRSC-430: Failed to start rolling patch mode
After fixing the cause of failure Run opatchauto resume
]
OPATCHAUTO-68061: The orchestration engine failed.
OPATCHAUTO-68061: The orchestration engine failed with return code 1
OPATCHAUTO-68061: Check the log for more details.
OPatchAuto failed.
OPatchauto session completed at Fri Sep 11 13:27:05 2020
Time taken to complete the session 11 minutes, 5 seconds
//From <GI_HOME>/ccfgtoollogs/optach/crspatch_<Node1>_2020-09-11_01-27-01PM.log
/<GI_HOME>/bin/crsctl start rollingpatch>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2020-09-11 13:27:03: Command output:
> CRS-1158: There was an error setting the cluster to rolling patch mode.>>>>>>>>>>>>>>>>>>>>>>>
> CRS-4000: Command Start failed, or completed with errors.
>End Command output
2020-09-11 13:27:03: Executing cmd: /<GI_HOME>/bin/clsecho -p has -f clsrsc -m 430
2020-09-11 13:27:03: Executing cmd: /<GI_HOME>/bin/clsecho -p has -f clsrsc -m 430
2020-09-11 13:27:03: Command output:
> CLSRSC-430: Failed to start rolling patch mode
>End Command output
2020-09-11 13:27:03: CLSRSC-430: Failed to start rolling patch mode
2020-09-11 13:27:03: ###### Begin DIE Stack Trace ######
2020-09-11 13:27:03: Package File Line Calling
2020-09-11 13:27:03: --------------- -------------------- ---- ----------
2020-09-11 13:27:03: 1: main rootcrs.pl 267 crsutils::dietrap
2020-09-11 13:27:03: 2: crspatch crspatch.pm 808 main::__ANON__
2020-09-11 13:27:03: 3: crspatch crspatch.pm 727 crspatch::performPrePatch
2020-09-11 13:27:03: 4: crspatch crspatch.pm 207 crspatch::crsPrePatch
2020-09-11 13:27:03: 5: main rootcrs.pl 276 crspatch::new
2020-09-11 13:27:03: ####### End DIE Stack Trace #######
2020-09-11 13:27:03: ROOTCRS_PREPATCH checkpoint has failed
2020-09-11 13:27:03: ckpt: -ckpt -oraclebase /<ORA_BASE> -chkckpt -name ROOTCRS_PREPATCH
2020-09-11 13:27:03: Invoking "/<GI_HOME>/bin/cluutil -ckpt -oraclebase /<ORA_BASE> -chkckpt -name ROOTCRS_PREPATCH"
2020-09-11 13:27:03: trace file=/<ORA_BASE> /crsdata/<Node1>/crsconfig/cluutil6
//From incident node,softwarepatch query fails as below.
[+ASM2] crsctl query crs softwarepatch
CRS-4467: Error code 8 in retrieving the software patch level for host <Node2>>>>>>>>>>>>>>>>>>>>
CRS-1191: There was an error retrieving the Oracle Clusterware software patch level.
CRS-4000: Command Query failed, or completed with errors.
cluvfy comp software -n <Node1>,<Node2> -verbose
Verifying software
Check: Software
0 files verified>>>>>>>>>>>>>>>>>>>>>>>>>>
Software check passed
Verification of software was successful.
Changes
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 |
| Changes |
| Cause |
| Solution |