Insert Into Clob With Length Between 8K and 32K Produces An Empty Value. (Doc ID 2833292.1)

Last updated on JUNE 28, 2022

Applies to:

Symptoms

A Java application makes inserts into a specific field, of type CLOB, with null or non-empty string values.
After the upgrade to the database 19c, it is noticed that after the second or third insert in a CLOB being null, the value found to be inserted is an empty string.
The issue occurs with JDBC 12c and 21c.
If the application is restarted, the problem disappears but manifests itself again after 2 or 3 inserts.

The expected value is empty instead of null.

Changes

Cause

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