Last updated on SEPTEMBER 17, 2013
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Information in this document applies to any platform.
***Checked for relevance on 17-Sep-2013***
The following errors occurred in the alert.log under the following circumstances:
1. The failing statement was an insert.
2. The failing statement involved an object (XMLTYPE and a CLOB in this case).
3. ODP.NET was used, although this did not turn out to be a factor of the bug.
4. The call stack did not contain an entry point for koksipacv().
ORA-00600: internal error code, arguments: , [0xFFFFFFFF7B17BE00], , , , , , 
ORA-04088: error during execution of trigger
For example, the following insert triggered the error:
This was originally thought to be
<Bug 5676637> - ORA-00600  ON INSERT WHEN TRIGGER IS ENABLED
but the application was not using EMPTY_CLOB in the trigger.
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 hundreds of Community platforms