OracleDatabase - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 11.2 to12.1]
Informationin this document applies to any platform.
***Checked for relevance on 03-Jul-2013***
If OCR is located on ASM diskgroup, following shows inASM alert log ($ORACLE_BASE/diag/asm/+asm/+ASMn/trace/alert_+ASMn.log)
after ASM mounted all diskgroup successfully whilestarting 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 withCRSD/OHASD)
Or after ASM dismounted all diskgroup successfullywhile shutting down clusterware:
SUCCESS:ALTER DISKGROUP ALL DISMOUNT /* asm agent */
Sun Feb07 11:11:13 2010
WARNING:failed to offline diskgroup resource ora.GI.dg (unable to communicate withCRSD/OHASD)
In contrast to previous version of CRS, 11gR2 ASM doesnot depend on CRSD anymore; rather if OCR is located on ASM, ASM will startbefore CRSD while clusterware is coming up, and stops
after CRSD whileclusterware is going down. Due to the new startup sequence, ASM can not updatediskgroup resource status in CRSD either during clusterware startup orshutdown, thus above message is logged.
The message can be ignored, the status of diskgroupand diskgroup resource will be synchronize by oraagent once clusterware isfully up.
To find out diskgroup resource status:
$GRID_HOME/bin/srvctl status diskgroup -gdiskgroupname -a
To start or sync diskgroup resource:
$GRID_HOME/bin/srvctl start diskgroup -g diskgroupname