停机测试:我停止了CRS 测试

简介: <div style="font-family:'lucida Grande',Verdana,'Microsoft YaHei'; font-size:14px; line-height:23px"> <div>停机测试:</div> <div>问题 我停止了CRS 测试。</div> <div>[grid@m2 ~]$ crs_stat -t</div> <div>CRS-01
停机测试:
问题 我停止了CRS 测试。
[grid@m2 ~]$ crs_stat -t
CRS-0184: Cannot communicate with the CRS daemon.
在没有启动的时候都是,这样提示的。

[grid@m1 ~]$ crs_start -all
CRS-5702: Resource 'ora.DATA.dg' is already running on 'm1'
CRS-5702: Resource 'ora.FRA.dg' is already running on 'm1'
CRS-5702: Resource 'ora.OCRVOTING.dg' is already running on 'm1'
CRS-5702: Resource 'ora.asm' is already running on 'm1'
CRS-5702: Resource 'ora.cvu' is already running on 'm1'
CRS-2501: Resource 'ora.gsd' is disabled
CRS-5702: Resource 'ora.asm' is already running on 'm1'
CRS-2501: Resource 'ora.gsd' is disabled
CRS-5702: Resource 'ora.ons' is already running on 'm1'
CRS-5702: Resource 'ora.asm' is already running on 'm2'
CRS-2501: Resource 'ora.gsd' is disabled
CRS-5702: Resource 'ora.ons' is already running on 'm2'
CRS-5702: Resource 'ora.net1.network' is already running on 'm1'
CRS-5702: Resource 'ora.ons' is already running on 'm1'
Attempting to start `ora.m2.vip` on member `m2`
Attempting to start `ora.scan1.vip` on member `m1`
Attempting to start `ora.m1.vip` on member `m1`
Attempting to start `ora.m3.vip` on member `m2`
Attempting to start `ora.oc4j` on member `m1`
Start of `ora.scan1.vip` on member `m1` succeeded.
Start of `ora.m3.vip` on member `m2` succeeded.
Attempting to start `ora.LISTENER_SCAN1.lsnr` on member `m1`
Start of `ora.m1.vip` on member `m1` succeeded.
Attempting to start `ora.MACLEAN_LISTENER.lsnr` on member `m1`
Attempting to start `ora.LISTENER.lsnr` on member `m1`
Start of `ora.m2.vip` on member `m2` succeeded.
Attempting to start `ora.ASM_LISTENER.lsnr` on member `m2`
Attempting to start `ora.LISTENER.lsnr` on member `m2`
Attempting to start `ora.MACLEAN_LISTENER.lsnr` on member `m2`
Attempting to start `ora.NEW_ASM_LISTENER.lsnr` on member `m2`
Start of `ora.MACLEAN_LISTENER.lsnr` on member `m1` succeeded.
Start of `ora.LISTENER.lsnr` on member `m1` succeeded.
Start of `ora.LISTENER_SCAN1.lsnr` on member `m1` succeeded.
Start of `ora.NEW_ASM_LISTENER.lsnr` on member `m2` succeeded.
CRS-5702: Resource 'ora.NEW_ASM_LISTENER.lsnr' is already running on 'm2'
Start of `ora.ASM_LISTENER.lsnr` on member `m2` succeeded.
Start of `ora.MACLEAN_LISTENER.lsnr` on member `m2` succeeded.
CRS-5702: Resource 'ora.MACLEAN_LISTENER.lsnr' is already running on 'm2'
Start of `ora.LISTENER.lsnr` on member `m2` succeeded.
Attempting to stop `ora.mes.db` on member `m2`
CRS-5702: Resource 'ora.LISTENER.lsnr' is already running on 'm2'
Start of `ora.oc4j` on member `m1` succeeded.
Stop of `ora.mes.db` on member `m2` succeeded.
Attempting to start `ora.mes.db` on member `m2`
Start of `ora.mes.db` on member `m2` succeeded.
Attempting to start `ora.ASM_LISTENER.lsnr` on member `m1`
Attempting to start `ora.NEW_ASM_LISTENER.lsnr` on member `m1`
Start of `ora.ASM_LISTENER.lsnr` on member `m1` succeeded.
Start of `ora.NEW_ASM_LISTENER.lsnr` on member `m1` succeeded.
Attempting to start `ora.mes.db` on member `m1`
CRS-5702: Resource 'ora.NEW_ASM_LISTENER.lsnr' is already running on 'm1'
Start of `ora.mes.db` on member `m1` succeeded.
CRS-0223: Resource 'ora.DATA.dg' has placement error.

CRS-0223: Resource 'ora.FRA.dg' has placement error.

CRS-0223: Resource 'ora.LISTENER.lsnr m2 1' has placement error.

CRS-0223: Resource 'ora.MACLEAN_LISTENER.lsnr m2 1' has placement error.

CRS-0223: Resource 'ora.NEW_ASM_LISTENER.lsnr m1 1' has placement error.

CRS-0223: Resource 'ora.NEW_ASM_LISTENER.lsnr m2 1' has placement error.

CRS-0223: Resource 'ora.OCRVOTING.dg' has placement error.

CRS-0223: Resource 'ora.asm' has placement error.

CRS-0223: Resource 'ora.cvu' has placement error.

CRS-2660: Resource 'ora.gsd' or all of its instances are disabled

CRS-0223: Resource 'ora.m1.ASM1.asm' has placement error.

CRS-2660: Resource 'ora.m1.gsd' or all of its instances are disabled

CRS-0223: Resource 'ora.m1.ons' has placement error.

CRS-0223: Resource 'ora.m2.ASM2.asm' has placement error.

CRS-2660: Resource 'ora.m2.gsd' or all of its instances are disabled

CRS-0223: Resource 'ora.m2.ons' has placement error.

CRS-0223: Resource 'ora.net1.network' has placement error.

CRS-0223: Resource 'ora.ons' has placement error.

待解决:
请留言。
目录
相关文章
|
6月前
|
消息中间件 运维 Kafka
运维排查 | Systemd 之服务停止后状态为 failed
运维排查 | Systemd 之服务停止后状态为 failed
|
运维 Java 调度
预发部署时机器总是重启两次的“简单”排查
本文只是总结下线上问题的排查过程,不讲方法论,没有大道理,行文会较为随意,注重的是排查思路,希望对同学们日常研发工作有所帮助~
107832 25
|
存储 Kubernetes API
优雅退出和零停机部署
如何在 Kubernetes 中使用优雅退出,使得业务具备零停机、无中断的部署发布。
238 1
我是如何完美解决WIN10崩溃无法自动恢复启动问题的
用U盘启动盘启动电脑,检查硬盘状态。确认硬盘状态良好。但是我注意到一件事情,就是我的c盘盘符下不是启动盘内容了;之前C盘下启动盘内容盘符变成了G盘;
我是如何完美解决WIN10崩溃无法自动恢复启动问题的
|
Python C语言 开发工具
想知道什么是零停机重启工具?Huptime教帮你 !
前言Huptime (High uptime)是零停机重启实用程序,不需要修改你的程序。 虽然很多应用支持运行的时候重载配置,但是一个零停机重启允许升级应用代码,不需要停止任何活动。 基础示例 终端: huptime --exec python -m SimpleHTTPServer & PID=.
868 0
|
测试技术 数据库 数据库连接
Confluence 6 从生产环境中恢复一个测试实例
请参考 Restoring a Test Instance from Production 页面中的内容获得更多完整的说明。
1140 0
|
JavaScript Perl
一次RAC VIP漂移的结果诊断及修复
背景概述 客户的10G数据库VIP出现宕,引起VIP负载到另一个节点 事件支持细节 04:29:56.378 一号机器VIP 出现 went OFFLINE unexpectedly,当天出现这个VIP漂移的故障后为检查VIP宕掉的原因, 对VIP资源启动DEBUG 5模式:./crsctl debug log res "orahostname1.vip:5" 04:38:36.047 一号节点VIP 出现 went OFFLINE unexpectedly。
2037 0
下一篇
无影云桌面