After Upgrade From JDBC 126.96.36.199 to JDBC 188.8.131.52 Using a Set Collection Type As A Bind Variable Is Very Slow
(Doc ID 1617091.1)
Last updated on FEBRUARY 19, 2021
Applies to:JDBC - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11.2]
Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
JDBC application that creates a Struct object from the JDBC connection gets a major performance hit when using the JDBC 126.96.36.199 driver. This is working fine with JDBC 188.8.131.52.
Using the following object: create or replace type TEST_OBJ as object (dummy varchar2(1));
Upgrade from JDBC 184.108.40.206 to 220.127.116.11.
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