暂无图片
暂无图片
暂无图片
暂无图片
暂无图片

关于CLSRSC-431:Failed to stop rolling patch mode报错的探究

DBA缓缓说 2019-11-17
3191

使用opatchauto升级补丁后,发生Failed to stop rolling patch mode报错。


    [root@dbn02 ~]# opatchauto apply u01/psu/25385515


    OPatchauto session is initiated at Thu Aug 29 17:02:32 2019


    System initialization log file is u01/app/12.2.0/grid/cfgtoollogs/opatchautodb/systemconfig2019-08-29_05-02-41PM.log.


    会话日志文件是/u01/app/12.2.0/grid/cfgtoollogs/opatchauto/opatchauto2019-08-29_05-04-03PM.log
    此会话的 ID 为 QNF8


    Executing OPatch prereq operations to verify patch applicability on home u01/app/12.2.0/grid


    Executing OPatch prereq operations to verify patch applicability on home u01/app/oracle/product/12.2.0/db
    Patch applicability verified successfully on home u01/app/oracle/product/12.2.0/db


    Patch applicability verified successfully on home u01/app/12.2.0/grid




    Verifying SQL patch applicability on home u01/app/oracle/product/12.2.0/db
    No step execution required.........



    Preparing to bring down database service on home u01/app/oracle/product/12.2.0/db
    Successfully prepared home u01/app/oracle/product/12.2.0/db to bring down database service




    Bringing down CRS service on home u01/app/12.2.0/grid
    Prepatch operation log file location: u01/app/grid/crsdata/dbn02/crsconfig/crspatch_dbn02_2019-08-29_05-04-45PM.log
    CRS service brought down successfully on home u01/app/12.2.0/grid




    Performing prepatch operation on home u01/app/oracle/product/12.2.0/db
    Perpatch operation completed successfully on home u01/app/oracle/product/12.2.0/db




    Start applying binary patch on home u01/app/oracle/product/12.2.0/db
    Binary patch applied successfully on home u01/app/oracle/product/12.2.0/db




    Performing postpatch operation on home u01/app/oracle/product/12.2.0/db
    Postpatch operation completed successfully on home u01/app/oracle/product/12.2.0/db




    Start applying binary patch on home u01/app/12.2.0/grid
    Binary patch applied successfully on home u01/app/12.2.0/grid




    Starting CRS service on home /u01/app/12.2.0/grid
    Postpatch operation log file location: /u01/app/grid/crsdata/dbn02/crsconfig/crspatch_dbn02_2019-08-29_05-10-43PM.log
    Failed to start CRS service on home /u01/app/12.2.0/grid


    未能执行 [GIStartupAction] 补丁程序操作, 有关详细信息, 请查看日志。故障:
    Patch Target : dbn02->/u01/app/12.2.0/grid 类型 [crs]
    Details: [
    ---------------------------Patching Failed---------------------------------
    Command execution failed during patching in home: /u01/app/12.2.0/grid, host: dbn02.
    Command failed: /u01/app/12.2.0/grid/perl/bin/perl -I/u01/app/12.2.0/grid/perl/lib -I/u01/app/12.2.0/grid/OPatch/auto/dbtmp/bootstrap_dbn02/patchwork/crs/install /u01/app/12.2.0/grid/OPatch/auto/dbtmp/bootstrap_dbn02/patchwork/crs/install/rootcrs.pl -postpatch
    Command failure output:
    Using configuration parameter file: /u01/app/12.2.0/grid/OPatch/auto/dbtmp/bootstrap_dbn02/patchwork/crs/install/crsconfig_params
    The log of current session can be found at:
    /u01/app/grid/crsdata/dbn02/crsconfig/crspatch_dbn02_2019-08-29_05-10-43PM.log
    2019/08/29 17:10:58 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector.
    2019/08/29 17:11:17 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector.
    2019/08/29 17:11:23 CLSRSC-329: Replacing Clusterware entries in file 'oracle-ohasd.conf'
    CRS-4123: 正在启动 Oracle 高可用性服务管理的资源
    CRS-2672: 尝试启动 'ora.mdnsd' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.evmd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.mdnsd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.evmd' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.gpnpd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.gpnpd' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.gipcd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.gipcd' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.cssdmonitor' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.cssdmonitor' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.cssd' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.diskmon' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.diskmon' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.cssd' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.cluster_interconnect.haip' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.ctssd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.ctssd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.cluster_interconnect.haip' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.asm' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.asm' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.storage' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.storage' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.crf' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.crf' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.crsd' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.crsd' (在 'dbn02' 上)
    CRS-6017: 正在处理以下服务器的资源自动启动: dbn02
    CRS-2672: 尝试启动 'ora.ASMNET1LSNR_ASM.lsnr' (在 'dbn02' 上)
    CRS-2673: 尝试停止 'ora.dbn02.vip' (在 'dbn01' 上)
    CRS-2672: 尝试启动 'ora.chad' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.ons' (在 'dbn02' 上)
    CRS-2677: 成功停止 'ora.dbn02.vip' (在 'dbn01' 上)
    CRS-2672: 尝试启动 'ora.dbn02.vip' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.chad' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.dbn02.vip' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.ASMNET1LSNR_ASM.lsnr' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.LISTENER.lsnr' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.ons' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.LISTENER.lsnr' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.asm' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.asm' (在 'dbn02' 上)
    CRS-2672: 尝试启动 'ora.DATA.dg' (在 'dbn02' 上)
    CRS-2676: 成功启动 'ora.DATA.dg' (在 'dbn02' 上)
    CRS-2664: 资源 'ora.dbn.db' 已在 'dbn01' 上运行
    CRS-2672: 尝试启动 'ora.dbn.db' (在 'dbn02' 上)
    CRS-2664: 资源 'ora.DATA.dg' 已在 'dbn02' 上运行
    CRS-2664: 资源 'ora.FRA.dg' 已在 'dbn02' 上运行
    CRS-2664: 资源 'ora.OCR.dg' 已在 'dbn02' 上运行
    CRS-2664: 资源 'ora.dbn.db' 已在 'dbn01' 上运行
    CRS-2664: 资源 'ora.mgmtdb' 已在 'dbn01' 上运行
    CRS-2676: 成功启动 'ora.dbn.db' (在 'dbn02' 上)
    CRS-6016: 服务器 dbn02 的资源自动启动已完成
    CRS-6024: 已完成启动 Oracle 集群就绪服务管理的资源
    CRS-4123: Oracle 高可用性服务已启动。
    CRS-8503: Oracle Clusterware 进程 CRSCTL (具有操作系统进程 ID 8021) 遇到致命信号或异常错误代码 11
    Failure with signal 6 from command: /u01/app/12.2.0/grid/bin/crsctl stop rollingpatch
    2019/08/29 17:16:07 CLSRSC-431: Failed to stop rolling patch mode


    After fixing the cause of failure Run opatchauto resume


    ]
    OPATCHAUTO-68061: 业务流程引擎失败。
    OPATCHAUTO-68061: 业务流程引擎失败, 返回代码为 1
    OPATCHAUTO-68061: 有关详细资料, 请查看日志。
    OPatchAuto 失败。


    OPatchauto session completed at Thu Aug 29 17:16:29 2019
    Time taken to complete the session 13 minutes, 58 seconds


    opatchauto failed with error code 42



    【根因分析】:


    解释一下上面的报错:关于stop rolling 报错,建议您在另一个节点也安装一下补丁,然后查看以下输出是否为NORMAL。

    [root@dbn02 28163133]# crsctl query crs activeversion -f

    Oracle Clusterware active version on the cluster is [12.2.0.1.0]. The cluster upgrade state is [NORMAL]. The cluster active patch level is [1440767577].

    如果输出的是NORMAL,那么这个报错可以忽略的,原因是你在滚动升级。



    【关于MOS中的解释】:


    MOS 1943498.1: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


    Q:是所有的滚动升级下,一个节点已经成功了,在打另外一个节点时,都会有这样的报错吗?


     A:是的, 滚动升级的设计就是,一个一个升级。如果我们在多个节点执行opatchauto 就会出这样的报错,可以忽略






    本文分享自微信公众号 - DBA缓缓说,如有侵权,请联系 service001@enmotech.com 删除。
    最后修改时间:2019-12-18 15:21:15
    文章转载自DBA缓缓说,如果涉嫌侵权,请发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。

    评论