Tuesday, February 09, 2016

ORA-00600: internal error code when executing trigger

Always check out the original article at http://www.oraclequirks.com for latest comments, fixes and updates.

Here is another example of ORA-00600 where probably it makes no sense at all to contact Oracle Support because you can fix the problem by yourself.
ORA-00600: internal error code, arguments: 
[17273], [0x07A89CBA8], [0], [1], [], [], [], [], [], [], [], []
 ORA-04088: error during execution of trigger Y
I found out that SQLDeveloper version 4.1.1 (and later possibly, I couldn't verify), sometimes generates triggers' DDLs with one trailing (invalid) character that causes the Oracle session to crash in Oracle XE 11.

The funniest part in the story is in that such character is not to be seen anywhere when you copy and paste the DDL, so it goes through completely inadvertently and the code compiles without a hitch.
As soon as the trigger fires, the session crashes.
Luckily, when you open the trigger source code in SQLDeveloper, you'll notice a strange character in the last position.
Just remove it and recompile the trigger.

I ignore if the bug is in SQLDeveloper or at some lower level, if it affects only Oracle XE 11 or also different versions.

See message translations for ORA-00600 and search additional resources.

No comments:

yes you can!

Two great ways to help us out with a minimal effort. Click on the Google Plus +1 button above or...
We appreciate your support!

latest articles