JDBC 22.214.171.124 Creates Many Child Cursors Due To Bind Mismatch On Timestamp Data Type
Last updated on JULY 05, 2018
Applies to:JDBC - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
JDBC Driver version 188.8.131.52, 184.108.40.206, and 220.127.116.11 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 18.104.22.168.
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