ORA-00600[kccpb_sanity_check_2]

联系:手机(13429648788)  QQ(107644445)

链接:https://www.orasos.com/ora-00600kccpb_sanity_check_2.html

标题:ORA-00600[kccpb_sanity_check_2]

作者:惜分飞©版权所有[文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.]

alert日志出现如下错误
数据库在mount的时候,因为出现ORA-00600[kccpb_sanity_check_2]错误导致数据库不能正常被mount成功

--sqlplus中报错
SQL> startup nomount;
ORACLE instance started.
 
Total System Global Area 4294967296 bytes                                     
Fixed Size                  2273256 bytes                                     
Variable Size            1486573592 bytes                                     
Database Buffers         2801795072 bytes                                     
Redo Buffers                4325376 bytes                                     
  
SQL> alter database mount;
alter database mount
*
ERROR at line 1:
ORA-600: internal error code, arguments: [kccpb_sanity_check_2], [2825], 
[2824], [0x000000000], [], [], [], [] 

--alert日志
Mon Sep 24 16:35:37 2012
ALTER DATABASE   MOUNT
Mon Sep 24 16:35:41 2012
Errors in file /opt/app/oracle/admin/lhgk/udump/lhgk_ora_17034.trc:
ORA-00600: internal error code, arguments: [kccpb_sanity_check_2], [2825], [2824], [0x000000000], [], [], [], []
Mon Sep 24 16:35:41 2012
ORA-600 signalled during: ALTER DATABASE   MOUNT...

错误原因

ORA-600 [kccpb_sanity_check_2] indicates that the seq# of the last read block is
higher than the seq# of the control file header block. This is indication of
the lost write of the header block during commit of the previous cf
transaction.

解决方法

1) restore a backup of a controlfile and recover

OR

2) recreate the controlfile

OR

3) restore the database from last good backup and recover

NOTE:  If you do not have any special backup of control file to restore and you are using Multiple Control File 
copies in your pfile/init.ora/spfile you can attempt to mount the database using each control file one by one.  
If you are able to mount the database with any of these control file copies you can then issue 
'alter database backup controlfile to trace' to recreate controlfile.

One thought on “ORA-00600[kccpb_sanity_check_2]

  1. ORA-00600: [kccpb_sanity_check_2] During Instance Startup [ID 435436.1]

    Applies to:
    Oracle Server - Enterprise Edition - Version: 10.2.0.1 and later   [Release: 10.2 and later ]
    Information in this document applies to any platform.
    Symptoms
    
    The database is getting the following errors on Startup:
    
    ORA-00600: internal error code, arguments: [kccpb_sanity_check_2], [3621501], [3621462], [0x000000000]
    
    Changes
    In this case, the customer moved the box from one data center to another.
    
    Cause
    ORA-600 [kccpb_sanity_check_2] indicates that the seq# of the last read block is
    higher than the seq# of the control file header block. This is indication of
    the lost write of the header block during commit of the previous cf
    transaction.
    
    
    Solution
    1) restore a backup of a controlfile and recover
    
    OR
    
    2) recreate the controlfile
    
    OR
    
    3) restore the database from last good backup and recover
    
    NOTE:  If you do not have any special backup of control file to restore and you are using Multiple Control File 
    copies in your pfile/init.ora/spfile you can attempt to mount the database using each control file one by one.  
    If you are able to mount the database with any of these control file copies you can then issue 
    'alter database backup controlfile to trace' to recreate controlfile.
    

Comments are closed.