ORA-00600 [krctcr_4]

Corruption in the block change tracking file - scn in this file doesn't match the scn in the database.

rman记录的文件信息与数据库中的信息不一致，最后导致数据库直接不能open。关闭block change tracking就可以解决。

 

ORA-00600: internal error code, arguments: [krctcr_4]
Posted on August 30, 2011 by Yogesh Bhandarkar
Recently seen this ORA-600 error at the time of opening the database.

Errors in file /u01/app/oracle/diag/rdbms/dbg/dbg02q/trace/dbg02q_ora_1802320.trc:
ORA-00600: internal error code, arguments: [krctcr_4], [80597120678], [80597148147], [], [], [], [], [], [], [], [], []
ORA-600 signalled during: ALTER DATABASE OPEN…
Mon Jul 18 07:42:08 2011
NOTE: Deferred communication with ASM instance
NOTE: deferred map free for map id 141

This error is caused by corrupt change tracking file. Solution is to disable the change tracking and re-enable it.

SQL> startup mount
SQL> alter database disable block change tracking;
SQL> alter database open;

 

 _________________

 

MOS原文如下：

 

 

Down Database After Server Crashed [ID 553009.1]转到底部

---

修改时间:2008-5-23类型:PROBLEM状态:PUBLISHED优先级:3注释 (0)

In this Document
  Symptoms
  Cause
  Solution

---

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1.0
This problem can occur on any platform.

Symptoms

Server crashed, and on database startup getting an ora-600[krctcr_4] which is preventing the database from opening.

Cause

This database has block change tracking enabled.

Corruption in the block change tracking file - scn in this file doesn't match the scn in the database.

From trace file see:

Successfully allocated 3 recovery slaves
Using 367 overflow buffers per recovery slave
Thread 1 checkpoint: logseq 1049, block 2, scn 17269705
cache-low rba: logseq 1049, block 81668
on-disk rba: logseq 1049, block 81830, scn 17287404
*** 2008-02-11 16:34:20.525
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [krctcr_4], [16736542], [0], [17269705], [0], [], [], []
Current SQL statement for this session:
ALTER DATABASE OPEN

Solution

To implement the solution, please execute the following steps:

SQL> startup mount
SQL> alter database disable block change tracking;
SQL> alter database open;

Take a backup, restart the DB and enable block change tracking.

This will reset the block change tracking file and allow the database to open.

---

相关内容

…

产品

…

• Oracle Database Products > Oracle Database > Oracle Database > Oracle Database - Enterprise Edition > RDBMS > ORA-600 by dbase unrelated to another product or component

关键字

…

SCN;SERVER CRASHES;START INSTANCE

错误

…