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 NOVEMBER 18, 2015

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2 to 12.1]
Information in this document applies to any platform.


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



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