Shulou(Shulou.com)06/01 Report--

Database instance log:

Tue Mar 01 12:18:12 2016

SUCCESS: diskgroup ORADISKGRP1 was dismounted

SUCCESS: diskgroup ORADISKGRP1 was dismounted

Errors in file C:\ APP\ ORACLE\ PRODUCT\ 11.2.0\ diag\ rdbms\ bflex\ bflex1\ trace\ bflex1_ckpt_6376.trc:

ORA-00206: error in writing (block 3, # blocks 1) of control file

ORA-00202: controlfile:'+ ORADISKGRP1/bflex/controlfile/current.287.925642037'

ORA-15078: ASM diskgroup was forcibly dismounted

ORA-15078: ASM diskgroup was forcibly dismounted

Take a look at the asm log.

Tue Mar 01 12:18:12 2016

ASM Health Checker found 1 new failures

Dirty Detach Reconfiguration complete

Tue Nov 01 12:18:12 2016

WARNING: dirty detached from domain 1

NOTE: cache dismounted group 1/0x5DD073B7 (ORADISKGRP1)

SQL > alter diskgroup ORADISKGRP1 dismount force / * ASM SERVER:1573942199 * /

Tue Nov 01 12:18:12 2016

NOTE: cache deleting context for group ORADISKGRP1 1/0x5dd073b7

GMON dismounting group 1 at 6 for pid 30, osid 7684

NOTE: Disk ORADISKGRP1_0000 in mode 0x7f marked for de-assignment

NOTE: Disk ORADISKGRP1_0001 in mode 0x7f marked for de-assignment

NOTE: Disk ORADISKGRP1_0002 in mode 0x7f marked for de-assignment

SUCCESS: diskgroup ORADISKGRP1 was dismounted

SUCCESS: alter diskgroup ORADISKGRP1 dismount force / * ASM SERVER:1573942199 * /

SUCCESS: ASM-initiated MANDATORY DISMOUNT of group ORADISKGRP1

The asm log here is obviously forced to dismount the disk group because the asm disk cannot be accessed properly and the ORA-27072 error is reported. Generally speaking, most of the reasons for this failure are caused by human misoperation, such as the bare disk attached to machine An is hung to machine B, and then misformatted.

How to handle it:

Use kfed to recover the disk head first

C:\ Users\ Administrator > kfed repair'\.\ J:'kfbh.endian: C:\ Users\ Administrator > kfed read'\.\ J:'kfbh.endian: 1; 0x000: 0x01kfbh.hard: 130; 0x001: 0x82kfbh.type: 1; 0x002: KFBTYP_DISKHEADkfbh.datfmt: 1; 0x003: 0x01kfbh.block.blk: 254; 0x004: titled 0 NUMB=0xfekfbh.block.obj: 2147483654; 0x008: TYPE=0x8 NUMB=0x6kfbh.check: 717599272; 0x00c: 0x2ac5b228kfbh.fcn.base: 0; 0x010: 0x00000000kfbh.fcn.wrap: 0; 0x014: 0x00000000kfbh.spare1: 0; 0x018: 0x00000000kfbh.spare2: 0 0x01c: 0x00000000kfdhdb.driver.provstr: ORCLDISKDATA6; 0x000: length=13kfdhdb.driver.reserved [0]: 1096040772; 0x008: 0x41544144kfdhdb.driver.reserved [1]: 54; 0x00c: 0x00000036kfdhdb.driver.reserved [2]: 0; 0x010: 0x00000000kfdhdb.driver.reserved [3]: 0; 0x014: 0x00000000kfdhdb.driver.reserved [4]: 0; 0x018: 0x00000000kfdhdb.driver.reserved [5]: 0; 0x01c: 0x00000000

Use asmtool-list to view relevant disk information

Then use dbv to detect whether there are bad blocks, and it is easy to do without them. Fortunately, asm has a backup, so you can restore it with backup.

SQL > recover database; completes media recovery. The SQL > alter database open; database has changed.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.