My Oracle Support Banner

ORA-00600 [kxtotolc_lobopt] When Getting An Explain For a Statement With Bind Variables (Doc ID 1050592.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.1.0.7 [Release 10.2 to 11.1]
Information in this document applies to any platform.

Symptoms

You could be attempting to get an Explain Plan for a SQL statement that have bind variables, and getting an ORA-00600 [kxtotolc_lobopt]. For example:

SQL> explain plan for UPDATE TABLE SET COLUMN1=:B2 WHERE COLUMN2=891;
explain plan for UPDATE TABLE SET COLUMN1=:B2 WHERE COLUMN2=891
*
ERROR at line 1:
ORA-600: internal error code, arguments: [kxtotolc_lobopt], [], [], [], [], [], [], [], [], [], [], []

But without the bind variables, it works fine:

SQL> explain plan for UPDATE TABLE SET COLUMN1=1234 WHERE COLUMN2=891;
.
Explained.

The call stack trace could look like:

kxtotolc <- kxtoropn <- kxtorab <- VInfreq__kxtopre <- updLoadTriggers
<- updpre0 <- qkadml <- qkastmt <- qkadrv <- opitca<- PGOSF360__kksFull <- TypeCheck <- rpiswu2 <- kksSetBindType <- kksfbc

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

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