My Oracle Support Banner

Memory Corruption Errors (e.g. ORA-600 [17182] / [17147] / [17114] etc.) from Java Clients Using Query Change Notification (Doc ID 1673541.1)

Last updated on JULY 12, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 18.3.0.0.0 [Release 11.2 to 18]
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.

Symptoms

Memory corruption errors such as ORA-600 [17182], ORA-00600 [17147] or ORA-00600 [17114] etc. may be seen when using Query Change Notification in a Java client application after adding a column to a table.

The trace files will show memory corruption of the callback heap for chunks of label "ktcnqAllocObjco".
Therefore, if you search the related trace file for "ktcnqAllocObjco", you will likely find this label or similar ktcnq memory allocations (i.e. "ktcnq rid colin", "ktcnq row trans" & "ktcnq RIDCONT").

Some or all of the following function codes will likely be found in the 'Call Stack' section of the trace file:

... kghfrf ktcnqFreeObjectContainer ktgDestroyHashContents ktcnqFreeObjectContainers ktcnqIQIDestroy ktcnqUndoNotificationWalk ktcnqPrecommitProcessing ktcninvalidate xctend k2send xctctl xctCommitTxn ...

 

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