ORA-00600: , ,  Without Current SQL Indicated in Trace File
(Doc ID 1565771.1)
Last updated on FEBRUARY 26, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
The error below is reported consistently in he alert log
ORA-00600: internal error code, arguments: , , , , , , , 
You may find some or all of the following function codes in the 'Call Stack' section of the incident trace file:
kdlfkd kdlxgsd ktsplbfmb ktsplbrecl ktspgsp_cbk1 kdlgsp_init
Error, call stack match
Bug 11814891 - ORA-600    [<lob block rdba>] / ORA-1555 double allocated LOB block [ID 11814891.8]
However, there is no Current SQL Statement in the trace file and also there are no accompanying errors such as ora-1555, ora-22922,etc
You may have attempted to run the scripts from these notes:
<NOTE:293515.1> - ORA-1578 ORA-26040 in a LOB segment - Script to solve the errors
<Document:11814891.8> - Bug 11814891 - ORA-600    [<lob block rdba>] / ORA-1555 double allocated LOB block
If so, find_lob.sql script and bad_rows script return no results
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