Email: service@parnassusdata.com 7 x 24 online support!
ORA-00600: [kccpb_sanity_check_2] During Instance Startup
If you cannot recover the data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.
Parnassusdata Software Database Recovery Team
Service Hotline: +86 13764045638 E-mail: service@parnassusdata.com
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.1 and later Information in this document applies to any platform.
***Checked for relevance on 18-Feb-2013***
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.