WARNING: failed to online diskgroup resource ora.DATA.dg (unable to communicate with CRSD/OHASD)

ASM实例启动时Alert日志中出现了如下告警提示：

WARNING: failed to online diskgroup resource ora.DATA.dg (unable to communicate with CRSD/OHASD)

我的环境为：AIX6L+11gR2+ASM+RAC 

在Metalink上找到如下文档，原来在11.2中，CRSD进程不再是RAC中最关键的进程之一，OHASD进程取代了CRSD进程变成了RAC环境中最关键的进程。

与先前版本的CRS相比，11gR2的ASM不在依赖CRSD进程，然后Oracle调整了ASM，使得OCR和VOT可以存储在ASM磁盘组中，那当Clusterware启动时ASM将会先于CRSD启动，而关闭时则后于CRSD关闭。由于这些新的启动顺序，在Clusterware启停是，ASM不能更新磁盘组资源的状态到CRSD进程中，因此才会出现这些错误提示，不过这些错误信息可以忽略。

也可以使用以下命令进行同步：

查看：

$GRID_HOME/bin/srvctl status diskgroup -g diskgroupname -a

启动或同步：

$GRID_HOME/bin/srvctl start diskgroup -g diskgroupname  

ALERT.LOG for ASM Shows "WARNING: failed to online diskgroup resource ora.GI.dg (unable to communicate with CRSD/OHASD)" [ID 1060920.1]

  修改时间 17-JAN-2012      类型 PROBLEM      状态 MODERATED

In this Document
  Symptoms
  Cause
  Solution

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later   [Release: 11.2 and later ]
Information in this document applies to any platform.

Symptoms

If OCR is located on ASM diskgroup, following shows in ASM alert log ( $ORACLE_BASE/diag/asm/+asm/+ASMn/trace/alert_+ASMn.log) after ASM mounted all diskgroup successfully while starting up Grid Infrastructure(CRS):

SQL> ALTER DISKGROUP ALL MOUNT /* asm agent */
..
SUCCESS: diskgroup GI was mounted
SUCCESS: ALTER DISKGROUP ALL MOUNT /* asm agent */
..
WARNING: failed to online diskgroup resource ora.GI.dg (unable to communicate with CRSD/OHASD)

Or after ASM dismounted all diskgroup successfully while shutting down clusterware:

..
SUCCESS: ALTER DISKGROUP ALL DISMOUNT /* asm agent */
Sun Feb 07 11:11:13 2010
WARNING: failed to offline diskgroup resource ora.GI.dg (unable to communicate with CRSD/OHASD)
..
freeing rdom 0

Cause

In contrast to previous version of CRS, 11gR2 ASM does not depend on CRSD anymore; rather if OCR is located on ASM, ASM will start before CRSD while clusterware is coming up, and stops after CRSD while clusterware is going down. Due to the new startup sequence, ASM can not update diskgroup resource status in CRSD either during clusterware startup or shutdown, thus above message is logged.

Solution

The message can be ignored, the status of diskgroup and diskgroup resource will be synchronize by oraagent once clusterware is fully up.

To find out diskgroup resource status:

$GRID_HOME/bin/srvctl status diskgroup -g diskgroupname -a

To start or sync diskgroup resource:

$GRID_HOME/bin/srvctl start diskgroup -g diskgroupname