資料庫啟動在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

資料庫啟動成功。

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/24996904/viewspace-1062901/，如需轉載，請註明出處，否則將追究法律責任。