ORA-00600[kcratr_nab_less_than_odr]故障解決

同事前一陣子搬着臺式機出去演示，回來時候，特豪邁地拔電源，裝車走人；回來後悲催地發現數據庫普通用戶登錄失敗，數據庫首先出現ORA-01033:ORACLE initialization or shutdown；然後按照網上指導
在DOS環境下
sqlplus /NOLOG
SQL>connect sys/sys as sysdba
SQL>shutdown normal
SQL>startup mount
SQL>alter database open;

然後 ，數據庫服務器出現ORA-00600[kcratr_nab_less_than_odr]，不能open數據庫

ORA-00600: 內部錯誤代碼, 參數: [kcratr_nab_less_than_odr], [1], [1984], [219……

遇到的錯誤是上面紅色部分，不完整，當時沒記錄，後面的數字好像沒什麼特殊，按照下面步驟做，一樣能完成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> 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: 'C:\app\Administrator\oradata\pdip\SYSTEM01.DBF'

--重建控制文件
SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'C:\app\Administrator\oradata\pdip\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 "PDIP" NORESETLOGS  NOARCHIVELOG  
      MAXLOGFILES 16  
       MAXLOGMEMBERS 3  
       MAXDATAFILES 100  
       MAXINSTANCES 8  
       MAXLOGHISTORY 18688  
    LOGFILE  
     GROUP 1 'C:\app\Administrator\oradata\pdip\REDO01.LOG'  SIZE 50M BLOCKSIZE 512,  
     GROUP 2 'C:\app\Administrator\oradata\pdip\REDO02.LOG'  SIZE 50M BLOCKSIZE 512,  
    GROUP 3 'C:\app\Administrator\oradata\pdip\REDO03.LOG'  SIZE 50M BLOCKSIZE 512  
  DATAFILE  
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\SYSTEM01.DBF',  
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\SYSAUX01.DBF',  
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\EXAMPLE01.DBF',  
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\JASFRAMEWORK.DBF',  
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\SDE.DBF',   
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\UNDOTBS01.DBF',  
    'C:\APP\ADMINISTRATOR\ORADATA\PDIP\USERS01.DBF'
     CHARACTER SET ZHS16GBK;
注意上面log和DBF文件是安裝數據庫實例的文件夾，保證上面文件存在，temp01.DBF文件除外。
控制文件已創建。
--繼續嘗試恢復
SQL> RECOVER DATABASE ;
完成介質恢復。
SQL> ALTER DATABASE OPEN;

數據庫已更改。
--open成功

      在這次恢復中，主要就是重建控制文件，然後直接恢復成功，如果redo有損壞，那麼可能需要使用不完全恢復，然後使用resetlogs打開數據庫

參考http://www.xifenfei.com/2012/01/ora-00600kcratr_nab_less_than_odr%e6%95%85%e9%9a%9c%e8%a7%a3%e5%86%b3.html