APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to 12.1]

Information in this document applies to any platform.

***Checked for relevance on 03-Jul-2013*** 

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