My Oracle Support Banner

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

Last updated on FEBRUARY 17, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.3 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 17-Sep-2013***


NOTE: In the images and/or the document content below, the user information and data used represents fictitious data .Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

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

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.

Changes

 NONE

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.