故障处理】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

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

# crsctl stop rollingpatch

About Me

...............................................................................................................................

● 本文作者:小麦苗,只专注于数据库的技术,更注重技术的运用

● 本文在itpub(http://blog.itpub.net/26736162)、博客园(http://www.cnblogs.com/lhrbest)和个人微信公众号(xiaomaimiaolhr)上有同步更新

● 本文itpub地址:http://blog.itpub.net/26736162/viewspace-2129163/

● 本文博客园地址:http://www.cnblogs.com/lhrbest/p/6106548.html

● 本文pdf版及小麦苗云盘地址:http://blog.itpub.net/26736162/viewspace-1624453/

● QQ群:230161599     微信群:私聊

● 联系我请加QQ好友(642808185),注明添加缘由

● 于 2016-11-24 15:00 ~ 2016-11-24 19:00 在农行完成

● 文章内容来源于小麦苗的学习笔记,部分整理自网络,若有侵权或不当之处还请谅解

● 版权所有,欢迎分享本文,转载请保留出处

...............................................................................................................................

手机长按下图识别二维码或微信客户端扫描下边的二维码来关注小麦苗的微信公众号:xiaomaimiaolhr,免费学习最实用的数据库技术。

【故障处理】CRS-1153错误处理的更多相关文章

  1. centos mysql 大量数据导入时1153 错误:1153 - Got a packet bigger than 'max_allowed_packet' bytes

    参考:http://stackoverflow.com/questions/93128/mysql-error-1153-got-a-packet-bigger-than-max-allowed-pa ...

  2. 【故障处理】IMP-00010错误 12C的dmp文件导入11G

    [故障处理]IMP-00010错误 12C的dmp文件导入11G 1  BLOG文档结构图 2  前言部分 2.1  导读和注意事项 各位技术爱好者,看完本文后,你可以掌握如下的技能,也可以学到一些其 ...

  3. 【故障处理】ORA-19809错误处理

    [故障处理]ORA-19809错误处理 一.1  BLOG文档结构图       一.2  前言部分 一.2.1  导读和注意事项 各位技术爱好者,看完本文后,你可以掌握如下的技能,也可以学到一些其它 ...

  4. 【故障处理】ORA-12162 错误的处理

    [故障处理]ORA-12162: TNS:net service name is incorrectly specified 一.1  场景 今天拿到一个新的环境,可是执行sqlplus / as s ...

  5. 【ASH】如何导出视图DBA_HIST_ACTIVE_SESS_HISTORY的查询结果数据

    [ASH]如何导出视图DBA_HIST_ACTIVE_SESS_HISTORY的查询结果数据 1.1  BLOG文档结构图 1.2  前言部分 1.2.1  导读和注意事项 各位技术爱好者,看完本文后 ...

  6. 《Google SRE》读后感

    注:这是去年国庆时的一篇读书笔记,最近线上故障频繁,重新读了下这篇读书笔记,觉得<Google SRE>非常棒,遂从简书再搬家到博客园,希望大家受益.我的简书地址:daoqidelv 国庆 ...

  7. 学习笔记:webpack

    http://wiki.jikexueyuan.com/project/webpack-handbook/ Webpack 中文指南 http://www.itzjt.cc/2017/04/09/we ...

  8. Grid Infrastructure 启动的五大问题 (文档 ID 1526147.1)

    适用于: Oracle Database - Enterprise Edition - 版本 11.2.0.1 和更高版本本文档所含信息适用于所有平台 用途 本文档的目的是总结可能阻止 Grid In ...

  9. 航空概论(历年资料,引之百度文库,PS:未调格式,有点乱)

    航空航天尔雅 选择题1. 已经实现了<天方夜谭>中的飞毯设想.—— A——美国2. 地球到月球大约—— C 38 万公里3. 建立了航空史上第一条定期空中路线—— B——德国4. 对于孔明 ...

随机推荐

  1. stl的优先级队列

    #include <iostream> #include <vector> #include <queue> using namespace std; class ...

  2. 分析SIX锁和锁分区导致的死锁

    什么是SIX锁? 官方文档锁模式中说到: 意向排他共享 (SIX):保护针对层次结构中某些(而并非所有)低层资源请求或获取的共享锁以及针对某些(而并非所有)低层资源请求或获取的意向排他锁. 顶级资源允 ...

  3. 关于WIndows内核自映射方案的通俗解释

    在一次操作系统课程上听老师说了这么一个有意思的东西,windows的自映射方案居然达到了把4K的页目录的线性地址“藏”在4M页表里的效果,感觉甚是奇特,于是乎就想着说怎么去算.光会算之后仍旧不满足,我 ...

  4. [Solution] 1分钟使用log4net

    log4net库是Apache log4j框架在Microsoft .NET平台的实现,是一个帮助程序员将日志信息输出到各种目标(控制台.文件.数据库等)的工具 官网:http://logging.a ...

  5. sprint3冲刺总结

    维持了一个多月的sprint3次总结终于结束了,我们小组也顺利的完成了我们的项目,总的来说这次完成的项目还是有一定的质量的,无论是外貌形象包装还是功能来说都达到了我们当初所设定的目标,美中不足的就是时 ...

  6. 【C#】属性(Attribute)

    如果程序员是猫,你是哪只猫? 这个是我一直都很喜欢的一个技术,不是很麻烦,也不是很难理解,和反射配合起来,只有你想不到没有做不到的用途(夸张了哈). 运用范围 程序集,模块,类型(类,结构,枚举,接口 ...

  7. c# Graphics使用方法(画圆写字代码)

    画填充圆: Graphics gra = this.pictureBox1.CreateGraphics(); gra.SmoothingMode = System.Drawing.Drawing2D ...

  8. eclipse新建maven项目(1)

    首先看一下eclipse版本,我用的是最新版Mars2. 下载地址自行搜索关键字:“eclipse官网”即可,注意下版本,32bit or 64bit. maven插件以及svn等相关插件安装设置问题 ...

  9. 最熟悉的陌生人-------MVC

          以前开发iOS程序的时候用的最多的是MVC的设计模式,这种软件架构的模式是由:模型(Model)[屏幕中展示的].视图(View)[如何展示的]和控制器(Controller)[程序的数据 ...

  10. Jaxb解析xml准换为javabean

    先说下这个的背景吧,前些日子,有个以前的小同事说刚接触webservice,想解析下xml,记得我学的时候还是dom4j,sax的解析方式,最近看别人的代码用的jaxb的方式,觉得注解起来很简练,所以 ...