ORA-600 [13030] On Update Statement
(Doc ID 744937.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.1.0.7 [Release 10.2 to 11.1]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
An update statement is failing with error ORA-600 [13030] and the table being updated has a trigger associated with it.
The call stack in the trace file is:
-----Call Stack ------
ksedmp <- ksfdmp <- kgeriv <- kgesiv <- ksesic1
<- updrow <- qerupRowProcedure <- qerupFetch <- updaul <- updThreePhaseExe
<- updexe <- opiexe <- opiall0 <- opial7 <- opiodr
<- ttcpip <- opitsk <- opiino <- opiodr <- opidrv
<- sou2o <- opimai_real <- opimai <- OracleThreadStart
Changes
NONE
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 |
Changes |
Cause |
Solution |
References |