ORA-600[krccacp_badfile] Known Issues when Creating the Block Change Tracking file
(Doc ID 357915.1)
Last updated on JUNE 16, 2021
Applies to:Oracle Database Cloud Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.1 to 22.214.171.124 [Release 10.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
List known issues with Block Change Tracking File reporting ORA-600 [krccacp_badfile]
ORA-600: internal error code, arguments: [krccacp_badfile], ,, , , , , , , , , 
943163934 --->SCN in the checkpoint
943165981 --> SCN in the Block change tracking
- krccacp_badfile is almost always a symptom of underlying storage issues
- Another common cause of krccacp_badfile is that a cluster split-brain has occurred. It is often possible to spot a split-brain in the alert logs by
seeing that one instance all of a sudden tries to do instance recovery for another instance, but the other instance has not gone down.
Call stack :- krccdw <- krcptmo <- ksbcti <- ksbabs <- krcpabs <- ksbrdp
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1) Bug 5035040 ENABLING BLOCK CHANGE TRACKING FAILS WITH ORA-600 [KRCCACP_BADFILE]|
|2) Bug 18155634 - Oracle DataBase corruption|
|3)Bug 20576649 - INSTANCE CRASH AFTER ORA-00600: [KRCCACP_BADFILE], |
|4) Bug 12629006 - EXADATA X2-2:ORA 600 [KRCCACP_BADFILE] WHEN ASM INSTANCE DOWN|