My Oracle Support Banner

ORA-600[PITL1] / ORA-600[kdt_bseg_srch_cbk PITL1] / ORA-700[PITL6] / ORA-700[kdt_bseg_srch_cbk PITL5] / ORA-700[kgegpa:parameter corruption] Errors in 12.1 and Above (Doc ID 2420831.1)

Last updated on JULY 12, 2022

Applies to:

Oracle Database - Enterprise Edition - Version and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A 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
Information in this document applies to any platform.


One or more errors of the following form are noted in the alert log:

ORA-00600 [PITL1]
ORA-00600 [kdt_bseg_srch_cbk PITL1]
ORA-00700: soft internal error, arguments: [PITL6]
ORA-00700: soft internal error, arguments: [kdt_bseg_srch_cbk PITL5]
ORA-00700: soft internal error, arguments: [kgegpa:parameter corruption]

The ORA-600 errors cause transaction failure. The ORA-700 errors do not cause transaction failure but can have temporary performance impact due to the number of errors reported. The last error is particular to the October 2018 Database Proactive Bundled Patch (DBBP), and is accompanied by junk characters in the alert log. There is no logical or physical corruption associated with it.

A typical call stack is:


Any of the following changes have occurred:

1) OLTP table compression is currently used or has been used in the past.

2) A patch for one of the following bugs has been applied (the first six have been superseded by the seventh and are no longer available) and any noted parameter changes made:

3) A quarterly bundled patch containing the fix for one of the above bugs has been applied

4) The database has been upgraded to version 19.1 or above


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
 The ORA-700 errors described in this document cause no lost data or corruption of any kind. They are strictly informational. If parallel DML is not in use and the fix for Bug 29782211 is installed, any inconsistency that they indicate may be safely ignored and table reorganization is not required.

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.