Server Side Leak With Call Statement & Null Numeric Bind When Timestamp Present

(Doc ID 1116688.1)

Last updated on JULY 05, 2017

Applies to:

Oracle Server - Enterprise Edition - Version: and later   [Release: 11.1 and later ]
Information in this document applies to any platform.


An OCCI application continuously loops through calling the same stored procedure. During the execution, the application memory remains constent but the memory associated with the DB process continues to grow. This is evident when the TimeStamp datatype is used.

The heap dump shows maximum "kkxmixcx : kgma" memory while re-executing stored procedure and rebinding of SQLT_TIMESTAMP type.


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