That's strange, do you have a reproducible test case, or could you
send me the database where this occurs?
Regards,
Thomas
> i'll send you a copy of database on monday.
Thanks a lot! Unfortunately, I will be on vacation for two weeks, so
I'm not sure if I will have time to look at it until then.
> Do you need java class, too?
Yes, that would be nice.
Regards,
Thomas
I can't really explain currently how the database came into this
state, but I found a way to automatically correct it. So the next
version of H2 will be able to open this database and run the ALTER
TABLE statement.
But I would like to understand how the database came into this state,
so I have a few questions:
- What is your database URL?
- Do you use temporary tables?
- Did you use LOG=0 or LOG=1?
- Did the application run out of memory (once, or multiple times)?
- Do you use any settings or special features (for example cache settings,
two phase commit, linked tables)?
- Do you use any H2-specific system properties?
- Is the application multi-threaded?
- What operating system, file system, and virtual machine
(java -version) do you use?
- How did you start the Java process (java -Xmx... and so on)?
- 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?
- Are there any other exceptions (maybe in the .trace.db file)?
Could you send them please?
- Do you still have any .trace.db files, and if yes could you send them?
Regards,
Thomas