JDBC Driver for SQL/MX Programmer's Reference

when LOB data is involved, autocommit is enabled, and an external transaction does not exist:

Clob.setAsciiStream●

Clob.setCharacterStream●

Blob.setBinaryStream●

If an SQL/MX or FS exception occurs while the base table and LOB table are being updated,

the internal transaction used for this operation is rolled back, and an exception is thrown.

When an SQL/MX or file system exception occurs while JDBC/MX mimics autocommit mode

for the base table and the insert or update operations on a LOB table, the internal transaction

used for this operation is rolled back and the following exception is thrown:

Transaction error {0} - {1} while updating LOB tables

For the description, see the message information under sqlcode 29070.

The JDBC/MX driver reserves data locators in its own transaction to improve the concurrency

among the different processes trying to reserve the data locators.

For more information, see Transactions.

Access Considerations for Clob and

Blob Objects

The JDBC/MX driver allows all the valid operations on the current Clob object or Blob

object, called a LOB object. LOB objects are current as long as the row that contains these LOB

objects is the current row. The JDBC/MX driver throws an SQLException, issuing the

following message, when the application attempts to perform operations on a LOB object that is

not current:

Lob object {object-id} is not current

Only one InputStream or Reader and one OutputStream or Writer can be associated

with the current LOB object.

When the application obtains the InputStream or Reader from the LOB object, the

JDBC/MX driver closes the InputStream or Reader that is already associated with

the LOB object.

●

Similarly, when the application obtains the OutputStream or Writer from the LOB

object, the JDBC/MX driver closes the OutputStream or Writer that is already

associated with the LOB object.

●