JDBC 11.2.0.3 Creates Many Child Cursors Due To Bind Mismatch On Timestamp Data Type

Last updated on JULY 05, 2018

Applies to:

Symptoms

JDBC Driver version 11.2.0.3, 11.2.0.4, and 12.1.0.2 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 11.2.0.1.

ERROR
-------------

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

Changes

Cause