同事前一陣子搬著桌上型電腦出去演示，回來時候，特豪邁地拔電源，裝車走人；回來後悲催地發現數據庫普通使用者登入失敗，資料庫首先出現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程式碼  

1. SQL> SELECT STATUS FROM V$INSTANCE;  
2. STATUS  
3. ------------
4. MOUNTED  
5. --嘗試直接recover database
6. SQL> RECOVER DATABASE ;  
7. ORA-00283: 恢復會話因錯誤而取消  
8. ORA-00264: 不要求恢復  
9. --提示不用恢復
10. --再開啟資料庫，還是kcratr_nab_less_than_odr錯誤警告
11. SQL> ALTERDATABASEOPEN;  
12. ALTERDATABASEOPEN
13. *  
14. 第 1 行出現錯誤:  
15. ORA-00600: 內部錯誤程式碼, 引數: [kcratr_nab_less_than_odr], [1], [99189],  
16. [43531], [43569], [], [], [], [], [], [], []  
17. --嘗試不完全恢復
18. SQL> RECOVER DATABASE UNTIL CANCEL;  
19. ORA-10879: error signaled in parallel recovery slave  
20. ORA-01547: 警告: RECOVER 成功但 OPEN RESETLOGS 將出現如下錯誤  
21. ORA-01152: 檔案 1 沒有從過舊的備份中還原  
22. ORA-01110: 資料檔案 1: 'C:\app\Administrator\oradata\pdip\SYSTEM01.DBF'
23. --重建控制檔案
24. SQL> ALTERDATABASE BACKUP CONTROLFILE TO TRACE AS'C:\app\Administrator\oradata\pdip\1.TXT';  
25. 資料庫已更改。  
26. SQL> SHUTDOWN IMMEDIATE;  
27. ORA-01109: 資料庫未開啟  
28. 已經解除安裝資料庫。  
29. ORACLE 例程已經關閉。  
30. SQL> STARTUP NOMOUNT;  
31. ORACLE 例程已經啟動。  
32. Total System Global Area  417546240 bytes  
33. Fixed Size                  2176328 bytes  
34. Variable Size             268438200 bytes  
35. Database Buffers          138412032 bytes  
36. Redo Buffers                8519680 bytes  
37. 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;
38. 注意上面log和DBF檔案是安裝資料庫例項的資料夾，保證上面檔案存在，temp01.DBF檔案除外。
    
39. 控制檔案已建立。
    
40. --繼續嘗試恢復
41. SQL> RECOVER DATABASE ;  
42. 完成介質恢復。  
43. SQL> ALTERDATABASEOPEN;  
44. 資料庫已更改。  
45. --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