ORA-600 [kti_memory_leak] when creating TEXT index in a 32K block_size tablespace
Last updated on JUNE 08, 2010
Applies to:Oracle Text - Version: 10.2.0.4
Information in this document applies to any platform.
Checked for relevance on 09-Jun-2010.
While creating CONTEXT indexes in a 32K blocksize tablespace, an error is logged in the alert.log:
ORA-00600: internal error code, arguments: [kti_memory_leak], , , , , , , 
Trace file shows:
INSERT /*+ SYS_DL_CURSOR */ INTO <owner>."DR$<index_name>$K" ("DOCID","TEXTKEY") VALUES
<- ktiassert <- ktiPoolOverflow <- kdilrub <- kdilroot_undoable
<- kdilcl0 <- kdblfx <- kdblfax <- kdblifl <- kdblfl
<- klafin <- kpodpfin <- kpodpmop <- opiodr
This error is generated while creating the second and subsequent TEXT indexes from the same session. For instance, if four (4) text indexes are being created consecutively from the same session, the 2nd, 3rd, and 4th TEXT index creation will EACH generate an ORA-600 [kti_memory_leak] in the alert.log. Note that although the error(s) occur, the TEXT indexes are created successfully with the status of VALID. This can be confirmed by querying USER_INDEXES as follows:
where ITYP_NAME = 'CONTEXT';
If creating more than nine (9) TEXT indexes consecutively from the same session, the 10th TEXT index creation will cause the user session to terminate with an ORA-3113. The first nine TEXT indexes are VALID while the 10th will have the status of INPROGS.
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