【故障处理】CRS-1153错误处理

简介: 【故障处理】CRS-1153错误处理   1  CRS-1153: There was an error setting Oracle Clusterware to rolling patch mode.

故障处理CRS-1153错误处理

 

1  CRS-1153: There was an error setting Oracle Clusterware to rolling patch mode.

升级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 #

 

1.1  MOS 1943498.1

wps453E.tmp

 

根据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


APPLIES TO:

Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.2 [Release 12.1]
Information in this document applies to any platform.

SYMPTOMS

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.

 

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:


 

    

wps453F.tmp

 

目录
相关文章
|
5月前
|
存储 缓存 网络协议
阿里云内存型实例规格性能、价格、适用场景与选型指南参考
阿里云服务器ECS(Elastic Compute Service)提供了多样化的内存型实例规格族,专为需要高性能内存资源的应用场景设计。从最新的r8a系列到经过优化的re6p系列,阿里云内存型实例旨在提供稳定、高效且安全的计算环境。这些实例不仅具备强大的计算性能与内存配比,还通过支持ESSD云盘和高效网络协议,显著提升了存储I/O能力和网络带宽,适用于大数据分析、高性能数据库、内存密集型应用等多种场景。本文将详细解析阿里云ECS中的多个内存型实例规格族,包括它们的核心特点、适用场景、实例规格及具体指标数据,为用户在选型时提供参考。
阿里云内存型实例规格性能、价格、适用场景与选型指南参考
|
2月前
|
SQL 关系型数据库 Apache
从 Flink 到 Doris 的实时数据写入实践 —— 基于 Flink CDC 构建更实时高效的数据集成链路
本文将深入解析 Flink-Doris-Connector 三大典型场景中的设计与实现,并结合 Flink CDC 详细介绍了整库同步的解决方案,助力构建更加高效、稳定的实时数据处理体系。
1009 0
从 Flink 到 Doris 的实时数据写入实践 —— 基于 Flink CDC 构建更实时高效的数据集成链路
|
存储 关系型数据库 MySQL
mysql数据库查询时用到的分页方法有哪些
【8月更文挑战第16天】在MySQL中,实现分页的主要方法包括:1)使用`LIMIT`子句,简单直接但随页数增加性能下降;2)通过子查询优化`LIMIT`分页,提高大页码时的查询效率;3)利用存储过程封装分页逻辑,便于复用但需额外维护;4)借助MySQL变量实现,可能提供更好的性能但实现较复杂。这些方法各有优缺点,可根据实际需求选择适用方案。
879 2
|
11月前
|
存储 弹性计算 固态存储
阿里云服务器ESSD Entry系统盘测评IOPS、IO读写和时延性能参数
ESSD Entry云盘是阿里云推出的新一代云盘,具备高IOPS、低延迟和企业级数据保护能力。适用于开发与测试场景,支持按量付费和包年包月计费模式。99元和199元的ECS经济型e实例和通用算力型u1实例均采用ESSD Entry系统盘,性价比高。详细性能参数和价格请参考阿里云官方页面。
438 0
|
11月前
|
弹性计算 Kubernetes Perl
k8s 设置pod 的cpu 和内存
在 Kubernetes (k8s) 中,设置 Pod 的 CPU 和内存资源限制和请求是非常重要的,因为这有助于确保集群资源的合理分配和有效利用。你可以通过定义 Pod 的 `resources` 字段来设置这些限制。 以下是一个示例 YAML 文件,展示了如何为一个 Pod 设置 CPU 和内存资源请求(requests)和限制(limits): ```yaml apiVersion: v1 kind: Pod metadata: name: example-pod spec: containers: - name: example-container image:
1383 2
|
文件存储 块存储 对象存储
对象存储、文件存储与块存储:了解基本差异
【6月更文挑战第3天】了解数据存储的“家”:对象存储如同杂物间,适合大量非结构化数据;文件存储像文件柜,便于管理结构化数据;块存储是积木箱,提供高性能、低延迟的存储空间。通过Python代码示例展示了三者使用场景。选择合适存储方式,让数据找到舒适“家”!
1222 4
|
SQL 关系型数据库 MySQL
在 MySQL 中使用 Exists
【8月更文挑战第11天】
1638 0
在 MySQL 中使用 Exists
|
存储 SQL 关系型数据库
MySQL数据库——存储过程-介绍以及基本语法(特点、创建、调用、查看、删除、示例)
MySQL数据库——存储过程-介绍以及基本语法(特点、创建、调用、查看、删除、示例)
1405 0
|
Oracle 关系型数据库 Linux
如果oracle用户下的$ORACLE_HOME bin oracle文件的属主或权限出了问题,那么该如何修复呢?
如果oracle用户下的$ORACLE_HOME bin oracle文件的属主或权限出了问题,那么该如何修复呢?
577 1