> I have not upgraded beyond 1.1.112 because we are currently using a
> JVM that only supports up to Java 1.4.2.
Did you try using Retrotranslator to convert the H2 jar file to Java
1.4? That should work.
http://retrotranslator.sourceforge.net
Regards,
Thomas
> However, I don't think this issue is resolved in the later builds.
There were quite many changes since version 1.1.112, but I'm not sure.
I'm afraid it will be quite hard to find out what the root cause is,
unless you have an application that can re-created such a corrupt
database... If you want, we can try to find out what could be the
problem. I have a few questions:
- What is your database URL?
- Did you use multiple connections?
- Do you use any settings or special features (for example, the setting
LOG=0, or two phase commit, linked tables, cache settings)?
- Is the application multi-threaded?
- What operating system, file system, and virtual machine
(java -version) do you use?
- Is it (or was it at some point) a networked file system?
- Is the database usually closed normally, or is process terminated
forcefully or the computer switched off?
Regards,
Thomas