One thought on “ORA-600 kcratr_nab_less_than_odr故障解决”

1. Applies to:
   Oracle Server - Enterprise Edition - Version: 11.2.0.1 to 11.2.0.2 - Release: 11.2 to 11.2
   Information in this document applies to any platform.
   Symptoms
   Trying to open a Database after a Crash caused by Storage Problems the Instance Recovery fails with :
   ORA-00600: internal error code, arguments: [kcratr_nab_less_than_odr], [1], [219], [25020], [25021], []
   The Database can't open at this Point. In the corresponding Tracefile we can find this Error Callstack:
   dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
   ----- Current SQL Statement for this session (sql_id=1h50ks4ncswfn) -----
   ALTER DATABASE OPEN
   ----- Call Stack Trace -----
   ksedst1 <- ksedst <- dbkedDefDump <- ksedmp <- dbgexPhaseII <- dbgexProcessError
   <- dbgePostErrorKGE  <- kgeasnmierr <- kcratr_odr_check  <- kcratr <- kctrec <-
   kcvcrv <- kcfopd <- adbdrv <- opiexe <- opiosq0 <- kpoal8 <- opiodr <- ttcpip
   <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real
   <-ssthrdmain <- main <- start
   Cause
   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-600.
   There are two possible Solutions:
   1. If you could restore your Storage Environment and the Online RedoLogs from
   the Time of the crash you can try a manual Recovery followed by a RESETLOGS:
   SQL> startup mount;
   SQL> recover database until cancel using backup controlfile;
   -> manually provide Online RedoLog containing the last (current) Sequence when asked, eg.
   ORA-00279: change 100000 generated at xx/xx/xxxx xx:xx:xx needed for thread 1
   ORA-00289: suggestion :
   /flash_recovery/archivelog/xxxx_xx_xx/o1_mf_1_100_%u_.arc
   ORA-00280: change 100000 for thread 1 is in sequence #100
   Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
   /ora/oradata/dbtest/redo04_1.rdo
   Log applied.
   Media recovery complete.
   SQL> alter database open resetlogs;
   2. If  step1. fails or you don't have the full Set of Files you have to
   restore and recover the Database from a recent Backup.
   

   回复

2. low rba ：在buffer cache中的数据块第一次数据改变所对应的RAB。 脏数据块在检查点 队列里面按照low rba排列。
   high rba ：在buffer cache中的数据块最近一次数据改变时所对应的RAB。
   checkpoint rba：在checkpint queue中（每次checkpoint queue被clean以后）第一个脏数据块第一次被修改对应的RAB,这个RBA之前的脏数据已经被全部写入磁盘。
   on-disk rba：是 lgwr 写日志文件的最末位置的地址。

   回复

3. lowrba ：在buffer cache中的数据块第一次数据改变所对应的RAB。 脏数据块在检查点 队列里面按照low rba排列。
   high rba ：在buffer cache中的数据块最近一次数据改变时所对应的RAB。
   checkpoint rba：在checkpint queue中（每次checkpoint queue被clean以后）第一个脏数据块第一次被修改对应的RAB,这个RBA之前的脏数据已经被全部写入磁盘。
   on-disk rba：是 lgwr 写日志文件的最末位置的地址。

   Redo Byte Address (RBA)
   the log file sequence number (4 bytes)
   the log file block number (4 bytes)
   the byte offset into the block at which the redo record starts (2 bytes)
   
   With respect to a dirty block in the buffer cache, the low RBA is the address of the redo for the first change that was applied to the block since it was last clean, and the high RBA is the address of the redo for the most recent change to have been applied to the block.
   Dirty buffers are maintained on the buffer cache checkpoint queues in low RBA order. The checkpoint RBA is the point up to which DBWn has written buffers from the checkpoint queues if incremental checkpointing is enabled — otherwise it is the RBA of last full thread checkpoint. The checkpoint RBA is copied into the checkpoint progress record of the controlfile by the checkpoint heartbeat once every 3 seconds. Instance recovery, when needed, begins from the checkpoint RBA recorded in the controlfile. The target RBA is the point up to which DBWn should seek to advance the checkpoint RBA to satisfy instance recovery objectives.
   The on-disk RBA is the point up to which LGWR has flushed the redo thread to the online log files. DBWn may not write a block for which the high RBA is beyond the on-disk RBA. Otherwise transaction recovery (rollback) would not be possible, because the redo needed to undo a change is always in the same redo record as the redo for the change itself.
   The term sync RBA is sometimes used to refer to the point up to which LGWR is required to sync the thread. However, this is not a full RBA — only a redo block number is used at this point.

   回复

4. 你重建控制文件的目的是什么

   回复

5. VMCD,
   1.ORA-00600[kcratr_nab_less_than_odr]错误的本质就是rba不能恢复到on-disk rba位置，可能的原因就断电的时候，使得redo中记录的rba没有达到控制文件中的on-disk rba，这个问题的解决办法，一般都是利用备份控制文件恢复，现在没有备份控制文件，只能利用重建控制文件解决
   
   2.根据上面的完全恢复和不完全恢复的提示，也可以考虑重建控制文件后再尝试恢复

   回复

6. CREATE CONTROLFILE ??
   ???? ‘rfb’ ??? db_name ‘orcl’ ???
   执行到最后一步出现这个错误，是怎么回事

   回复

7. scott,
   你创建控制文件里面写的dbname和参数文件里面的不匹配

   回复