My Oracle Support Banner

JDBC Timestamp Variable is Bound with Scale 9 or Null which Leads to Too Many Child Cursors in JDBC 12c (Doc ID 2427003.1)

Last updated on MARCH 04, 2019

Applies to:

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

Symptoms

Higher number of cursors are observed when using timestamp bind variable in INSERT or UPDATE statements. Two child cursors were created because of the mismatch of the scale value of the timestamp.
If for example, there are 13 timestamps in the statement, all possible permutations will be created. This means there will be 2^13 = 8192 child cursors for one statement just because of scale mismatch.

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.