mysql 磁盘组_存储精简卷导致asm磁盘组异常 – 提供7*24专业数据库(Oracle,SQL Server,MySQL等)恢复和Oracle技术服务@Tel:+86 13429648788 -...

有朋友在一个存储空间给asm使用，发生空间不足，然后使用另外一个存储中的lun给asm的data磁盘组增加asm disk,运行了大概1天之后,asm磁盘组直接dismount,数据库crash.然后就无法正常mount.包括这个存储上的几个其他磁盘组也无法正常mount.

数据库异常日志

Sun Oct 23 08:43:59 2016

SUCCESS: diskgroup DATA was dismounted

SUCCESS: diskgroup DATA was dismounted

Sun Oct 23 08:44:00 2016

Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lmon_79128.trc:

ORA-00202: control file: '+DATA/orcl/controlfile/current.278.892363163'

ORA-15078: ASM diskgroup was forcibly dismounted

Sun Oct 23 08:44:00 2016

Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lgwr_79174.trc:

ORA-00345: redo log write error block 15924 count 2

ORA-00312: online log 2 thread 1: '+DATA/orcl/onlinelog/group_2.274.892363167'

ORA-15078: ASM diskgroup was forcibly dismounted

ORA-15078: ASM diskgroup was forcibly dismounted

Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lgwr_79174.trc:

ORA-00202: control file: '+DATA/orcl/controlfile/current.278.892363163'

ORA-15078: ASM diskgroup was forcibly dismounted

Errors in file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_lgwr_79174.trc:

ORA-00204: error in reading (block 1, # blocks 1) of control file

ORA-00202: control file: '+DATA/orcl/controlfile/current.278.892363163'

ORA-15078: ASM diskgroup was forcibly dismounted

Sun Oct 23 08:44:00 2016

LGWR (ospid: 79174): terminating the instance due to error 204

Sun Oct 23 08:44:00 2016

opiodr aborting process unknown ospid (79742) as a result of ORA-1092

Sun Oct 23 08:44:01 2016

ORA-1092 : opitsk aborting process

Sun Oct 23 08:44:01 2016

ORA-1092 : opitsk aborting process

System state dump requested by (instance=1, osid=79174 (LGWR)), summary=[abnormal instance termination].

System State dumped to trace file /oracle/app/oracle/diag/rdbms/orcl/orcl1/trace/orcl1_diag_79118.trc

Instance terminated by LGWR, pid = 79174

很明显，数据库异常是由于asm diskgroup dismount,因此分析asm 日志

asm 日志

Sun Oct 23 07:00:31 2016

Time drift detected. Please check VKTM trace file for more details.<