数据库启动在mount状态，无任何报错-优快云博客

数据库版本：11.1.0.7.0

操作系统版本：linux6

数据库启动在mount状态，后台日志无报错，显示正在做recovery，hang住：

Mon Nov 18 09:30:08 2013
alter database open
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
319186 redo blocks read, 37950 data blocks need recovery

通过对数据库进行10046tracce分析、hanganalyze分析均无结果。

最后对数据文件进行dbv，发现有坏块：

DBVERIFY - 开始验证: FILE = /dev/raw/raw104
页 353108 标记为损坏
Corrupt block relative dba: 0x10856354 (file 66, block 353108)
Completely zero block found during dbv:

页 353109 标记为损坏
Corrupt block relative dba: 0x10856355 (file 66, block 353109)
Completely zero block found during dbv:

页 353110 标记为损坏
Corrupt block relative dba: 0x10856356 (file 66, block 353110)
Completely zero block found during dbv:

DBVERIFY - 验证完成

检查的页总数: 2048000
处理的页总数 (数据): 1391015
失败的页总数 (数据): 0
处理的页总数 (索引): 627655
失败的页总数 (索引): 0
处理的页总数 (其它): 29327
处理的总页数 (段) : 0
失败的总页数 (段) : 0
空的页总数: 0
标记为损坏的总页数: 3
流入的页总数: 0
加密的总页数 : 0
最高块 SCN : 2578500721 (0.2578500721)

对数据库进行标记后，数据库自动进行recovery，后台日志：
Hex dump of (file 66, block 353108) in trace file /opt/oracle/diag/rdbms/log2db/log2db/trace/log2db_ora_20638.trc
Corrupt block relative dba: 0x10856354 (file 66, block 353108)
Completely zero block found during crash/instance recovery
Reread of rdba: 0x10856354 (file 66, block 353108) found same corrupted data
Hex dump of (file 66, block 353109) in trace file /opt/oracle/diag/rdbms/log2db/log2db/trace/log2db_ora_20638.trc
Corrupt block relative dba: 0x10856355 (file 66, block 353109)
Completely zero block found during crash/instance recovery
Reread of rdba: 0x10856355 (file 66, block 353109) found same corrupted data
Hex dump of (file 66, block 353110) in trace file /opt/oracle/diag/rdbms/log2db/log2db/trace/log2db_ora_20638.trc
Corrupt block relative dba: 0x10856356 (file 66, block 353110)

Completely zero block found during crash/instance recovery
Reread of rdba: 0x10856356 (file 66, block 353110) found same corrupted data
Mon Nov 18 09:30:20 2013
Started redo application at
Thread 1: logseq 3452, block 3714433
Recovery of Online Redo Log: Thread 1 Group 2 Seq 3452 Reading mem 0
Mem# 0: /dev/raw/raw3
Completed redo application of 97.67MB
Mon Nov 18 09:30:32 2013
Completed crash recovery at
Thread 1: logseq 3452, block 4033619, scn 2578535648
37950 data blocks read, 37950 data blocks written, 319186 redo blocks read
Mon Nov 18 09:30:34 2013
Thread 1 advanced to log sequence 3453 (thread open)
Thread 1 opened at log sequence 3453
Current log# 3 seq# 3453 mem# 0: /dev/raw/raw4
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Nov 18 09:30:34 2013
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is ZHS16GBK
Opening with internal Resource Manager plan : on 2 X 8 NUMA system
Mon Nov 18 09:30:43 2013
Starting background process FBDA
Mon Nov 18 09:30:43 2013
FBDA started with pid=9, OS id=21068
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Mon Nov 18 09:30:47 2013
QMNC started with pid=28, OS id=21073
Mon Nov 18 09:33:19 2013
Completed: alter database open