ORA-00600 kcratr_nab_less_than_odr

早上发现数据库报如下错误:

Successful mount of redo thread 1, with mount id 339694234
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE   MOUNT
Mon Jan 26 09:12:01 2015
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
Started redo scan
Completed redo scan
read 42 KB redo, 46 data blocks need recovery
ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [6], [15358], [15932], [], [], [], [], [], [], []
Incident details in: /opt/app/oracle/diag/rdbms/db11g/DB11G/incident/incdir_6153/DB11G_ora_1030_i6153.trc
Aborting crash recovery due to error 600
Errors in file /opt/app/oracle/diag/rdbms/db11g/DB11G/trace/DB11G_ora_1030.trc:
ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [6], [15358], [15932], [], [], [], [], [], [], []
Errors in file /opt/app/oracle/diag/rdbms/db11g/DB11G/trace/DB11G_ora_1030.trc:
ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [6], [15358], [15932], [], [], [], [], [], [], []

查看数据库需要恢复,但是数据库异常断电,导致LGWR写到日志文件失败。这里 [kcratr_nab_less_than_odr], [1], [6], [15358], [15932]
需要恢复序列号为6的日志到15932个快,但是目前只能到15358


在mount状态查看当前日志:

SQL> select * from v$log;
SQL> /

    GROUP#    THREAD#  SEQUENCE#      BYTES  BLOCKSIZE    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIM NEXT_CHANGE# NEXT_TIME
---------- ---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- --------- ------------ ---------
         1          1          4   52428800        512          2 NO  INACTIVE                913220 24-JAN-15       949149 25-JAN-15
         3          1          6   52428800        512          2 NO  CURRENT                 961046 25-JAN-15   2.8147E+14
         2          1          5   52428800        512          2 NO  INACTIVE                949149 25-JAN-15       961046 25-JAN-15
进行恢复:

SQL> recover database until cancel using backup controlfile;
ORA-00279: change 961046 generated at 01/25/2015 15:47:32 needed for thread 1
ORA-00289: suggestion : /opt/app/oracle/flash_recovery_area/DB11G/archivelog/2015_01_26/o1_mf_1_6_%u_.arc
ORA-00280: change 961046 for thread 1 is in sequence #6


Specify log: {=suggested | filename | AUTO | CANCEL}
/opt/app/oracle/oradata/DB11G/onlinelog/o1_mf_3_bd66d4k4_.log
Log applied.
Media recovery complete.
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-00603: ORACLE server session terminated by fatal error
ORA-00600: internal error code, arguments: [2662], [0], [969494], [0], [969702], [12583104], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [2662], [0], [969493], [0], [969702], [12583104], [], [], [], [], [], []
ORA-01092: ORACLE instance terminated. Disconnection forced
ORA-00600: internal error code, arguments: [2662], [0], [969491], [0], [969702], [12583104], [], [], [], [], [], []
Process ID: 1030
Session ID: 1 Serial number: 5
打开数据库发现scn又不一致,这里推进以下scn即可:

SQL> conn / as sysdba
Connected to an idle instance.
SQL>
SQL> startup mount; 
ORACLE instance started.

Total System Global Area  638853120 bytes
Fixed Size                  2213736 bytes
Variable Size             411043992 bytes
Database Buffers          222298112 bytes
Redo Buffers                3297280 bytes
Database mounted.
SQL> alter session set events 'IMMEDIATE trace name ADJUST_SCN level 1';

Session altered.

SQL> alter database open;

Database altered.
哈哈,终于打开数据库了。异常断电还是很坑爹的。



你可能感兴趣的:(Oracle,TroubleShooting)