Diskgroup resource shows status offline after restart even it is mounted in ASM instance
Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.1.0 - Release: 11.2
Information in this document applies to any platform.
Symptoms
After restart the 11.2 HAS stack, the diskgroup (.dg) resource is showing "OFFLINE" status, but diskgroup is mounted in the ASM instance.
For example:
$ crsctl stat res ora.DATA.dg
NAME=ora.DATA.dg
TYPE=ora.diskgroup.type
TARGET=OFFLINE, ONLINE
STATE=OFFLINE, ONLINE on host1
From ASM when you query , the diskgroup shows as mounted.
SQL> conn / as sysdba
Connected.
SQL> select name,state from v$asm_diskgroup;
NAME STATE
------------------------------ -----------
DATA MOUNTED
Changes
From the crsd.log:
2010-02-05 16:05:09.988: [AGFW][56] ora.DATA.dg host1 1 received state from probe request. Old state = UNKNOWN, New state = OFFLINE
From oraagent_oracle.log:
2010-02-05 16:05:09.799: [AGFW][9] ora.DATA.dg host1 1 state changed from: UNKNOWN to: OFFLINE
Cause
This is caused by an unpublished bug 8663101 11.2 DG RES OFFLINE, BUT DISKGROUP MOUNTED AFTER RESTART HAS STACK
The diskgroup is mounted in asm before crsd is up so crsd is never notified of the diskgroup resource start.
Solution
The bug has been fixed in 11.2.0.2 patchset.
Two workarounds available:
1. Manually start the diskgroup:
srvctl start diskgroup -g [-n ""]
或者：
2. Modify the attribute AUTO_START to "always"
crsctl modify resource ora..dg -attr AUTO_START=always