db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald McLean <dmclea...@gmail.com>
Subject Re: XJ073 The data in this BLOB or CLOB is no longer available
Date Thu, 31 Dec 2009 01:23:39 GMT
This condition is very frequently caused when the user has autocommit
set to true. BLOBs and CLOBs can only be used inside a transaction
(i.e. autocommit set to false). Don't forget to commit the transaction
after you have finished with the BLOB/CLOB.

On Tue, Dec 29, 2009 at 5:15 PM, geoffrey hendrey <geoff@nextdb.net> wrote:
> On Derby I see the following error. "ERROR XJ073: The data in this
> BLOB or CLOB is no longer available.  The BLOB/CLOB's transaction may be
> committed, or its connection is closed." Are there any known issues around
> this? It occurs intermittently, and I've never seen in happen twice in a
> row. I don't think I'm prematurely closing the connection. I found a Jira
> issue around this, but it seemed like the discussion concluded it was user
> error. Thought I would ping the list to see if there are any known bugs on
> this.
Family photographs are a critical legacy for
ourselves and our descendants. Protect that
legacy with a digital backup and recovery plan.

Join the photo preservation advocacy Facebook group:

View raw message