Complex CLOB Updates Fail With ORA-01461 After RDBMS Upgraded To 18.104.22.168
Last updated on MARCH 08, 2017
Applies to:JDBC - Version 10.2.0.1 to 22.214.171.124.0 [Release 10.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 15-Aug-2013***
When using various versions of the Oracle JDBC driver against an 126.96.36.199 RDBMS, attempts to update a CLOB column fail with the following error:
ORA-01461: can bind a LONG value only for insert into a LONG column
The following characteristics are observed:
* The problem reproduces with any version of the JDBC driver against an 188.8.131.52 database
* The problem does not reproduce with database versions older than 184.108.40.206
* The problem occurs when the variable length being updated exceeds 4000 characters (despite the fact that the field is a CLOB)
* The problem occurs when an UPDATE statement contains a sub-select statement; when the UPDATE statement does not contain a sub-select statement, the problem does not occur
An example of such an UPDATE statement containing a sub-select:
The problem occurs whether the Java code uses setCharacterStream() or setString().
The problem appears after installing or upgrading the database to version 220.127.116.11.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms