My Oracle Support Banner

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

Last updated on JUNE 14, 2022

Applies to:

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


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.
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?



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

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