My Oracle Support Banner

JDBC Creates Many Child Cursors Due To Bind Mismatch On Timestamp Data Type (Doc ID 2418191.1)

Last updated on JULY 05, 2018

Applies to:

JDBC - Version and later
Information in this document applies to any platform.


JDBC Driver version,, and creates many child cursors due to bind mismatch on timestamp data type. Two different binds for the timestamp variable will be seen: one with scale 9 and one with scale <null>.  
This happens when the application inserts null timestamps and then updates them.
The JDBC driver creates multiple child cursor and after a certain threshold is reached, mutex issue and performance degrade is experienced.

The issue does not occur with JDBC


<ChildNode><ChildNumber>54</ChildNumber><ID>40</ID><reason>Bind mismatch(14)




To view full details, 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 a vibrant support community of peers and Oracle experts.