ORA-600 [17114] and ORA-600 [17147] on Insert or Merge (Doc ID 549397.1)

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***

Symptoms

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().

Errors:

ORA-00600: internal error code, arguments: [17114], [0xFFFFFFFF7B17BE00], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [17147], [0xFFFFFFFF7B17BE00], [], [], [], [], [], []
ORA-04088: error during execution of trigger

For example, the following insert triggered the error:

INSERT INTO LV_FOLDERS (FOLDER_ID, PARENT_ID, CREATE_ID, CREATE_DT, MODIFY_ID, MODIFY_DT, VIEW_ORDER, FOLDER_SORT_METHOD, FOLDER_SORT_DIRECTION, DOCUMENT_SORT_METHOD, DOCUMENT_SORT_DIRECTION, PROPERTIES, TEMPLATE_ID, FOLDER_NAME) values (305, 304, 'LANV', SYSDATE, 'LANV', SYSDATE, NULL, NULL, NULL, NULL, NULL, :param0, 4081, :param1)


This was originally thought to be
<Bug 5676637> - ORA-00600 [17114] ON INSERT WHEN TRIGGER IS ENABLED
but the application was not using EMPTY_CLOB in the trigger.

Cause

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