XMLType.createXML Versus T24JDBCConnection.createClob (Doc ID 2875798.1)

Last updated on JUNE 14, 2022

Applies to:

Goal

An extra SQL*Net round-trip is observed when inserting a small CLOB value compared to inserting the same value as an XMLTYPE from Java.
How to avoid that extra round-trip for CLOB inserts?
For example, when using a clob and method JDBCConnection.createClob() as below, an application is seeing some delay due to an extra round trip created by the clob client call.
1) LOBTMPCREATE
2) LOBWRITE
3) INSERT INTO --> actual insert.
This is not happening for XMLTYPE but only for CLOB types. Why are these extra calls (LOBTMPCREATE, LOBWRITE) required?
Is there a way to improve the insert clob operation?

Solution

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