Oracle JDBC (MOSC)

MOSC Banner

High number of cursor permutations from fully bound SQL using java/jdbc thin

in Oracle JDBC (MOSC) 2 commentsAnswered

Our java based application is using an Oracle jdbc thin driver. The SQL insert is fully bound. Due to the variability of the input data, we get many different child cursor permutations due to bind upgradeable length. This is compounded by DDL partition drops and adds, which we are working on changing to a maintenance window. Aside from varchar2 data types, we also see various child cursors with using different RAW(n) and BLOB buckets based upon the max data length. We have also encountered an issue our timestamps. Sometimes the timestamp being passed via jdbc thin has no milliseconds

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center