My Oracle Support Banner

CREATE INDEX = ORA-600[ktuisc:xid] in a Multitenant Environment (Doc ID 2393664.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Information in this document applies to any platform.

Symptoms

A CREATE INDEX statement on a timestamp column such as:

CREATE INDEX <TableOwner>.<IndexName> ON <TableOwner>.<TableName> ("<TimestampColumn>")...

fails with the following error in SQL*Plus:          

ORA-00600: internal error code, arguments: [ktuisc:xid], [8], [14], [4139766], [335297], [], [], [], [], [], [], []

 

CREATE INDEX statements on columns other than timestamps are successful.

 

The Call Stack Track trace in the associated incident trace file shows:

ktuItlScanRecordCommitTimes <- ktuSegHdrExamFunc <- kcbgtcr <- ktuGetCommitTimesMain_Int <- ktuGetCommitTimesMain <- ktuGetCommitTimes <- ktbgcl1 <- ktrgcm <- ktrget2 <- kdst_fetch0 <- kdstf000110100001000km <- kdsttgr <- qertbFetch <- qersoProcessULS <- qersoFetchSimple <- qersoFetch <- qerliFetch <- kdicrws <- kdicdrv <- opiexe <- opiosq0 <- kpooprx <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main

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!


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