Large Waiting Times on Server Cleanup On Connection Close After Batch CLOB Insert with 19.3 JDBC
(Doc ID 2877706.1)
Last updated on JUNE 22, 2022
Applies to:JDBC - Version 19.3 and later
Information in this document applies to any platform.
Oracle Data Integrator (ODI) application using WebLogic 22.214.171.124.0 and JDBC 19.3 transfers CLOB data from one schema to another in a 12c Oracle database.
The application runs a SELECT statement on the table in source schema and then runs a batch INSERT statement on the table in target schema.
When ODI calls Commit Transaction, the thread takes a longer amount of time when closing the connection than it did using earlier versions of ODI and JDBC (this performance issue did not occur when using ODI 126.96.36.199 and JDBC 188.8.131.52).
The performance degradation appears to increase dramatically as the batch size increases.
1. Using the same parameters and data in 184.108.40.206 and 220.127.116.11 with row limits set to 50,000: 18.104.22.168, the execution time is 2.3 times faster than 22.214.171.124.
2. If the row limit is increased from 50,000 to 100,000, 12.2.13 execution time is 4.3 times faster than 126.96.36.199.
3. Testing with the following Java directive results in no performance improvement.
This setting reverts the driver to behave as it did with the 188.8.131.52 JDBC driver by disabling LOB free from being piggybacked.
Setting this parameter to true results in a server round-trip for every free() call.
Upgrade from ODI 184.108.40.206 to 220.127.116.11.0.
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