I observed this error a few times during some experiments I did some
time ago. See DERBY-637. Not the same setting, though. Client/server,
30 GB database. When this started to occur, all my transaction fail
with this error. Restarting the database, made the error disappear.
--
Øystein
On Saturday 12 May 2007 01:47:30 Stanley Bradbury wrote:
A conglomerate is a data or index file in Derby. The message means
conglomerate number 113 was referenced but could not be found. It
appears the object was an index that was referenced in the cache but I
can't tell much else from the
On Monday 14 May 2007 10:04:33 Daniel Noll wrote:
I'll see if I can get access to the derby.log file.
Okay, now I have derby.log and the same error occurs twice. Once on
checkpoint, but it also happens earlier when trying to do a real query
(figures.)
Here's the lines which precede the
Daniel Noll wrote:
It was while running this statement...
CALL SYSCS_UTIL.SYSCS_CHECKPOINT_DATABASE()
That I got the following exception:
ERROR XSAI2: The conglomerate (113) requested does not exist.
at
It was while running this statement...
CALL SYSCS_UTIL.SYSCS_CHECKPOINT_DATABASE()
That I got the following exception:
ERROR XSAI2: The conglomerate (113) requested does not exist.
at
org.apache.derby.iapi.error.StandardException.newException(StandardException.java:311)
at
