Reading a 3 GB BLOB with JDBC 220.127.116.11 Fails With "ORA-22925: operation would exceed maximum size allowed for a LOB value"
(Doc ID 1101087.1)
Last updated on MARCH 13, 2019
Applies to:JDBC - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 11.2]
Oracle Database - Standard Edition - Version 126.96.36.199 to 188.8.131.52 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Add ***Checked for relevance on 28-Feb-2013***
A java application reads BLOBs from a database and writes them to a file using the code:
When using JDBC 184.108.40.206 to read a 4 GB or larger BLOB from a 10.2.0.3 database, the ORA-22925 error also occurs.
However, when using JDBC 220.127.116.11 to read a 4 GB or larger BLOB from an 18.104.22.168 database, the output is truncated without an error. See <Note 1101163.1> Silent (No Error) Truncation Reading a 4 GB or Larger BLOB with JDBC 22.214.171.124 for details.
When using JDBC 126.96.36.199 to read the same 3GB, 4GB and larger BLOBs, the ORA-22925 does not occur. Nor does truncation occur.
The ORA-22925 occurred after upgrading JDBC 188.8.131.52 to JDBC 184.108.40.206.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!