My Oracle Support Banner

ORA-00600[17291] During an Update Statement (Doc ID 3002781.1)

Last updated on FEBRUARY 26, 2024

Applies to:

Oracle Database - Enterprise Edition - Version and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Gen 2 Exadata Cloud at Customer - Version All Versions and later
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Information in this document applies to any platform.


Update statement is failing with the following error :

Per functions from the call stack, there is a trigger that is fired during update and fails.

Looking in the incident trace file for the address:0x7F6D835B6BE0 (second argument from ORA-600) we can see the trigger name involved:

INSTANTIATION OBJECT: object=0x7f6d835b6be0
type="PL/SQL"[1] lock=0xd31e2af0 pn=(nil) handle=0xb7646f90 lkhandle=0xb7646f90 body=(nil) level=0
name=<owner>.<trigger_name>                                 -->trigger having 4 dependencies
flags=SHR/NST/LRU[1045] executions=1
kgiobses=0x1469d3710 kgiobuse=0x1469d3710
dependency# instantiation flags
----------- ------------- -------
0 (nil) [00]
1 (nil) [00]
2 (nil) [00]
3 0x7f6d83458468 [00] <owner>.<object>
PLIO: Trigger <trigger_name> pliospc=(nil) pliostfr=0x7f6d833c3db0 pliopflg=0x0080


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

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