DB Instance Crashing With ORA-00600: Internal Error Code, Arguments: [ktsla_rbk_ins_chunk-1]
(Doc ID 2193159.1)
Last updated on AUGUST 25, 2023
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 11.2.0.4 and later
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.
Symptoms
1. Error logged in the alert log:
ORA-00600: internal error code, arguments: [ktsla_rbk_ins_chunk-1], [1], [56679496], [54632321], [], [], [], [], [], [], [], []
2. Incident trace might not contain any failing statement/cursor:
========= Dump for incident 9965 (ORA 600 [ktsla_rbk_ins_chunk-1]) ========
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- SQL Statement (None) -----
Current SQL information unavailable - no cursor.
3. Failing function stack:
(functions related to undo)
4. The following errors may be reported multiple times in the alert log .
ORACLE Instance DEV5O11 (pid = 14) - Error 600 encountered while recovering transaction (19, 24) on object 5083560.
ORACLE Instance DEV5O11 (pid = 14) - Error 600 encountered while recovering transaction (19, 24) on object 5083560. <<<< always the same object
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |