Alan,
As you are aware, it is not recommended to delete the log fils manually.
The logCorruptedException has another nestedException and it is because
the value read from the log records is not matched with required
appropriate data.
But, Did you observe any sort of inconsistencies in your database when
you boot again after you delete the files. ?
How often do you (or did you ever) run the compress table routines ??
Do you see the log corrupted when you boot the db or during some
transactions ??
any more information which you think is relevant ??
Mayuresh
BALDWIN, ALAN J [AG-Contractor/1000] wrote:
More info:
Windows XP
JVM 1.5 and JVM 1.4.2
I don't see any exceptions being thrown in our application before any of the
corruption cases that would indicate that something in the app had gone
awry.
Also, attached is my derby.log file.
-Alan-
-----Original Message-----
From: BALDWIN, ALAN J [AG-Contractor/1000]
Sent: Thursday, November 16, 2006 9:42 AM
To: [email protected]
Subject: java.sql.SQLException: Log Corrupted, has invalid data in the log
stream.
Hi all,
We are having log corruption issues with Derby inside of a java swing
application.
Here is the error:
java.sql.SQLException: Log Corrupted, has invalid data in the log stream.
We have about 1000 users using this software, and I would guess that at any
given time we see 4-5 with log corruption. Deleting "logXXX.dat" files from
within the log folder fixes the problem for the time being, but I would like
to get at the root of the problem. Is this safe to do as an interim
solution? I assume these are transaction logs, so it doesn't seem like a
good idea to delete them, but that is the only thing that seems to work.
Also, anecdotally, this seems to be more prevalent in version 10.2 since we
upgraded from 10.1.3 a few weeks ago.
I'm also going to dig around on JIRA to seem if I come up with anything.
Any ideas?
Thanks,
