Oracle数据库断电致使控制文件不一致的恢复方法

一. 数据库断电致使控制文件不一致的恢复方法
数据库服务器意外断电出现ORA-00600[kcratr_nab_less_than_odr],不能open数据库
1.open数据库报ORA-00600[kcratr_nab_less_than_odr]

SQL> ALTER DATABASE OPEN; 
ALTER DATABASE OPEN 
*1 行出现错误: 
ORA-00600: 内部错误代码, 参数: [kcratr_nab_less_than_odr], [1], [99189], 
[43531], [43569], [], [], [], [], [], [], [] 

2.查看alert日志

Wed Jan 11 13:56:16 2012 
ALTER DATABASE OPEN 
Beginning crash recovery of 1 threads 
parallel recovery started with 2 processes 
Started redo scan 
Completed redo scan 
read 54591 KB redo, 0 data blocks need recovery 
Errors in file d:\dbdms\diag\rdbms\dbdms\dbdms\trace\dbdms_ora_3108.trc  (incident=818557): 
ORA-00600: 内部错误代码, 参数: [kcratr_nab_less_than_odr], [1], [99189], [43531], [43569], [], [], [], [], [], [], [] 
Incident details in: d:\dbdms\diag\rdbms\dbdms\dbdms\incident\incdir_818557\dbdms_ora_3936_i818557.trc 
Aborting crash recovery due to error 600 
Errors in file d:\dbdms\diag\rdbms\dbdms\dbdms\trace\dbdms_ora_3108.trc: 
ORA-00600: 内部错误代码, 参数: [kcratr_nab_less_than_odr], [1], [99189], [43531], [43569], [], [], [], [], [], [], [] 
Errors in file d:\dbdms\diag\rdbms\dbdms\dbdms\trace\dbdms_ora_3108.trc: 
ORA-00600: 内部错误代码, 参数: [kcratr_nab_less_than_odr], [1], [99189], [43531], [43569], [], [], [], [], [], [], [] 
ORA-600 signalled during: ALTER DATABASE OPEN... 
Trace dumping is performing id=[cdmp_20120110214555] 

3.查看trace文件

Trace file d:\dbdms\diag\rdbms\dbdms\dbdms\trace\dbdms_ora_3108.trc 
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production 
With the Partitioning, OLAP, Data Mining and Real Application Testing options 
Windows NT Version V6.1 Service Pack 1 
CPU                 : 2 - type 8664, 2 Physical Cores 
Process Affinity    : 0x0x0000000000000000 
Memory (Avail/Total): Ph:2250M/4060M, Ph+PgF:5868M/8119M 
Instance name: dbdms 
Redo thread mounted by this instance: 1 
Oracle process number: 17 
Windows thread id: 3108, image: ORACLE.EXE (SHAD) 
………………………… 
WARNING! Crash recovery of thread 1 seq 99189 is 
ending at redo block 43531 but should not have ended before 
redo block 43569 
Incident 826550 created, dump file: d:\dbdms\diag\rdbms\dbdms\dbdms\incident\incdir_826550\dbdms_ora_3108_i826550.trc 
ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [99189], [43531], [43569], [], [], [], [], [], [], [] 

ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [99189], [43531], [43569], [], [], [], [], [], [], [] 
ORA-00600: ??????, ??: [kcratr_nab_less_than_odr], [1], [99189], [43531], [43569], [], [], [], [], [], [], [] 

通过alert和trace中的内容可以知道,数据库需要恢复到rba到43569,但是因为某种原因实例恢复的时候,只能利用1 thread 99189 seq#,恢复rba到43531。从而导致数据库无法正常open

This Problem is caused by Storage Problem of the Database Files. The
Subsystem (eg. SAN) crashed while the Database was open. The Database
then crashed since the Database Files were not accessible anymore.
This caused a lost Write into the Online RedoLogs and so Instance
Recovery is not possible and raising the ORA

4.解决方法
Sql代码

SQL> SELECT STATUS FROM V$INSTANCE;  
   
STATUS  
------------  
MOUNTED  

–尝试直接recover database

SQL> RECOVER DATABASE ;  
ORA-00283: 恢复会话因错误而取消  
ORA-00264: 不要求恢复  

–提示不用恢复

–再打开数据库,还是kcratr_nab_less_than_odr错误警告

SQL> ALTER DATABASE OPEN;  
ALTER DATABASE OPEN  
*1 行出现错误:  
ORA-00600: 内部错误代码, 参数: [kcratr_nab_less_than_odr], [1], [99189],  
[43531], [43569], [], [], [], [], [], [], []  

–尝试不完全恢复

SQL> RECOVER DATABASE UNTIL CANCEL;  
ORA-10879: error signaled in parallel recovery slave  
ORA-01547: 警告: RECOVER 成功但 OPEN RESETLOGS 将出现如下错误  
ORA-01152: 文件 1 没有从过旧的备份中还原  
ORA-01110: 数据文件 1: 'D:\DBDMS\DATA\SYSTEM01.DBF'  

–重建控制文件

SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'D:/1.TXT';  

数据库已更改。

SQL> SHUTDOWN IMMEDIATE;  
ORA-01109: 数据库未打开  
   
   
已经卸载数据库。  
ORACLE 例程已经关闭。  
SQL> STARTUP NOMOUNT;  
ORACLE 例程已经启动。  

Total System Global Area  417546240 bytes  
Fixed Size                  2176328 bytes  
Variable Size             268438200 bytes  
Database Buffers          138412032 bytes  
Redo Buffers                8519680 bytes  
SQL> CREATE CONTROLFILE REUSE DATABASE "DBDMS" NORESETLOGS  NOARCHIVELOG  
  2      MAXLOGFILES 16  
  3      MAXLOGMEMBERS 3  
  4      MAXDATAFILES 100  
  5      MAXINSTANCES 8  
  6      MAXLOGHISTORY 18688  
  7  LOGFILE  
  8    GROUP 1 'D:\DBDMS\LOG\REDO01.LOG'  SIZE 50M BLOCKSIZE 512,  
  9    GROUP 2 'D:\DBDMS\LOG\REDO02.LOG'  SIZE 50M BLOCKSIZE 512,  
 10    GROUP 3 'D:\DBDMS\LOG\REDO03.LOG'  SIZE 50M BLOCKSIZE 512  
 11  DATAFILE  
 12    'D:\DBDMS\DATA\SYSTEM01.DBF',  
 13    'D:\DBDMS\DATA\SYSAUX01.DBF',  
 14    'D:\DBDMS\DATA\RBSG01.DBF',  
 15    'D:\DBDMS\DATA\DATA01.DBF',  
 16    'D:\DBDMS\DATA\INDX01.DBF',  
 17    'D:\DBDMS\DATA\DATA02.DBF',  
 18    'D:\DBDMS\DATA\DATA03.DBF',  
 19    'D:\DBDMS\DATA\DATA04.DBF',  
 20    'D:\DBDMS\DATA\INDX02.DBF',  
 21    'D:\DBDMS\DATA\SYSTEM02.DBF'  
 22  CHARACTER SET ZHS16GBK  
 23  ;  

控制文件已创建。

--继续尝试恢复  
SQL> RECOVER DATABASE ;  
完成介质恢复。  
SQL> ALTER DATABASE OPEN;  
   
数据库已更改。  
--open成功  

SQL> SELECT STATUS FROM V$INSTANCE;
 
STATUS
------------
MOUNTED

在这次恢复中,主要就是重建控制文件,然后直接恢复成功,如果redo有损坏,那么可能需要使用不完全恢复,然后使用resetlogs打开数据库!