My Oracle Support Banner

ORA-00600 [17273] After DML on Table with Trigger (Doc ID 1342968.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.3 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 12-Dec-2013***

Symptoms

You are attempting to insert, update or delete in/from a table containing a before INSERT or UPDATE or DELETE trigger that also is executing a PL/SQL procedure and that fails with:

ORA-00600: internal error code, arguments: [17273], [0x70000045191B038], [0],[<x>], [], [], [], [], [], [], [], []

Note: In the above error message <x> can be 1 or 2.

The call stack in the trace file will show functions similar to the following:

... kgiind <- pfri8_inst_spec <- pfri1_inst_spec <- pfrrun <- plsql_run <- peicnt <- peiet_execute_trigger <- kkxtexe <- kxtExecuteTriggerRecursive <- rpiswu2 <- kxtExecuteTriggerReal <- kxtexe <- delrts <- delexe <- opiexe <- kpoal8 <- opiodr <- ttcpip <- opitsk <- opiino <- opiodr <- opidrv <- sou2o <- opimai_real <- ssthrdmain <- main <- start

Changes

This is happening when renaming a trigger and then renaming it back to its original name before doing the statement that is firing it.

NOTES:
1. If renaming the trigger then the fourth argument (<x>) is 1.
2. If renaming the table and trigger to new names and reverting back to original names the fourth argument (<x>) is 2.

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


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