ORA-600 [kkslpbp:1] When Using CURSOR_SHARING=similar (or force)

(Doc ID 747675.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 31-Dec-2013***


Symptoms

This incident was observed on Oracle 10.2.0.4 64-bit on a HP-UX Itanium server
RAC database, but the error can occur on single instance databases.
It can occur in any 10G release lower than 10.2.0.5


Problem description:
Some SQL statements are failing with internal errors.


The alert log shows the errors are occurring intermittently.

ORA-00600: internal error code, arguments: [kkslpbp:1], [], [], [], [], [], [], []


Other Symptoms:
- The trace file may show:  No current SQL statement being executed.
In this particular case, the errors were coming from a PL/SQL procedure that executed the statements.

- A search of the trace file for 'Current Cursor:' will show that there is a SQL statement in the
current cursor.  This particular case showed the SQL statement using the WITH clause, but this issue has been reported in cases where a WITH clause was not being used.

-The alert log will show that the database was started with cursor_sharing = SIMILAR or FORCE, or the PL/SQL procedure will show that cursor_sharing is being set within the procedure.
For example: EXECUTE IMMEDIATE 'ALTER SESSION SET CURSOR_SHARING = SIMILAR';


The function stack may look like the following:.

ksedst ksedmp ksfdmp kgerinv kgeasnmierr
$cold_kkslpbp kkspsc0 kksParseCursor opiosq0 opiall0 opikpr . .









Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms