分享程序员开发的那些事...
更新时间：2022-08-28 17:45:18
【故障处理】CRS-1153错误处理
升级PSU的时候有错误，需要回退patch，但是报错了：
错误信息：
|
HQNHL-ALHR-R01:/oracle/app/12.1.0/grid/crs/install # rootcrs.pl -prepatch Using configuration parameter file: /oracle/app/12.1.0/grid/crs/install/crsconfig_params Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [0]. PROC-28: Oracle Cluster Registry already in current version CRS-1153: There was an error setting Oracle Clusterware to rolling patch mode. CRS-4000: Command Start failed, or completed with errors. 2016/11/23 18:45:40 CLSRSC-430: Failed to start rolling patch mode
Died at crspatch.pm line 783. HQNHL-ALHR-R01:/oracle/app/12.1.0/grid/crs/install # |
根据MOS:
CAUSE
The issue happens if the cluster is already in rolling patch mode, it's due to unpublished bug:
BUG 19499021 - 12.1.0.2.1GIPSU: OPATCHAUTO HIT CLSRSC-430: FAILED TO START ROLLING PATCH MODE
SOLUTION
The fix is included in 12.1.0.2 GI PSU1, the workaround is to stop rolling patch and re-run opatchauto:
# crsctl stop rollingpatch
解决：
|
HQNHL-ALHR-R01:~ # /oracle/app/12.1.0/grid/bin/crsctl stop rollingpatch CRS-1169: The cluster is consistent and the cluster active patch level is [0]. CRS-4000: Command Stop failed, or completed with errors. HQNHL-ALHR-R01:~ # HQNHL-ALHR-R01:~ # oerr crs 1169 1169, 0, "The cluster is consistent and the cluster active patch level is [%u]." // *Cause: The cluster has already completed the rolling patch procedure. // *Action: None. HQNHL-ALHR-R01:~ # |
重新执行/oracle/app/12.1.0/grid/crs/install/rootcrs.pl -prepatch命令打PUS补丁即可。
附录：MOS 1943498.1 CRS-1153: There was an error setting Oracle Clusterware to rolling patch mode. (文档 ID 1943498.1)
In this Document
| Symptoms |
| Cause |
| Solution |
Applying patch with opatchauto fails with the following:
[root@racnode1 19392646]# /ocw/c102/OPatch/opatchauto apply -oh /ocw/c102 -ocmrf /mnt/OP/ocm.rsp
....
Configuration Validation: Successful
Patch Location: /mnt/OP/C102PSU1/19392646
Grid Infrastructure Patch(es): 19303936 19392590 19392604
RAC Patch(es): 19303936 19392604
Patch Validation: Successful
Stopping CRS ... Failed
Command "/ocw/c102/perl/bin/perl -I/ocw/c102/perl/lib -I/ocw/c102/crs/install /ocw/c102/crs/install/rootcrs.pl -prepatch" execution failed:
Died at /ocw/c102/crs/install/crspatch.pm line 751.
For more details, please refer to the log file "/ocw/c102/cfgtoollogs/opatchauto/19392646/opatch_gi_2014-10-19_11-41-35_deploy.debug.log".
Apply Summary:
Following patch(es) failed to be installed:
GI Home: /ocw/c102: 19303936, 19392590, 19392604
opatchauto failed with error code 2.
From the forementioned log file:
2014-10-19_11-42-02 :
Executing command:
/ocw/c102/perl/bin/perl -I/ocw/c102/perl/lib -I/ocw/c102/crs/install /ocw/c102/crs/install/rootcrs.pl -prepatch
2014-10-19_11-42-08 :
COMMAND EXECUTION FAILURE :
Using configuration parameter file: /ocw/c102/crs/install/crsconfig_params
Oracle Clusterware active version on the cluster is [12.1.0.2.0]. The cluster upgrade state is [ROLLING PATCH]. The cluster active patch level is [0].
PROC-28: Oracle Cluster Registry already in current version
CRS-1153: There was an error setting Oracle Clusterware to rolling patch mode.
CRS-4000: Command Start failed, or completed with errors.
2014/10/19 11:42:06 CLSRSC-430: Failed to start rolling patch mode
ERROR:
Died at /ocw/c102/crs/install/crspatch.pm line 751.
2014-10-19_11-42-08 :
Failed to run this command :
/ocw/c102/perl/bin/perl -I/ocw/c102/perl/lib -I/ocw/c102/crs/install /ocw/c102/crs/install/rootcrs.pl -prepatch
oracle.opatch.gi.RunExecutionSteps.runGenericShellCommands(RunExecutionSteps.java:874)
oracle.opatch.gi.RunExecutionSteps.processAllSteps(RunExecutionSteps.java:197)
oracle.opatch.gi.GIPatching.processPatchingSteps(GIPatching.java:756)
oracle.opatch.gi.OPatchautoExecution.main(OPatchautoExecution.java:125)
Command "/ocw/c102/perl/bin/perl -I/ocw/c102/perl/lib -I/ocw/c102/crs/install /ocw/c102/crs/install/rootcrs.pl -prepatch" execution failed:
Died at /ocw/c102/crs/install/crspatch.pm line 751.
The issue happens if the cluster is already in rolling patch mode, it's due to unpublished bug:
BUG 19499021 - 12.1.0.2.1GIPSU: OPATCHAUTO HIT CLSRSC-430: FAILED TO START ROLLING PATCH MODE
The fix is included in 12.1.0.2 GI PSU1, the workaround is to stop rolling patch and re-run opatchauto:
|
|
