[h2] Re: Corrupted databases with 1.4.199

2022-01-03 Thread Silvio
Download H2 1.4.196 and try to do a record of the database with that by running java -cp h2-1.4.196.jar org.h2.tools.Recover from the same directory as a copy of the database file. For me this works in 90% of all cases. If it does not and an exception is thrown then you are out of luck.

[h2] Re: Corrupted databases with 1.4.199

2019-04-15 Thread Silvio
Hmm, sorry for the confusion. This was a result of sloppy log copying. This is what happens now: 2019-04-12 09:24:17 database: flush org.h2.message.DbException: General error: "java.lang.IllegalStateException: Reading from nio:/path/to/database.mv.db failed; file length 488419328 read length

[h2] Re: Corrupted databases with 1.4.199

2019-04-12 Thread Evgenij Ryazanov
Hello. Error code 1.4.196/1 clearly indicates that exception was thrown by 1.4.196 and not by 1.4.199. You need to check your environment, it looks like you still use 1.4.196 somewhere. Maybe you have multiple jars in your classpath. However, it's reasonable to export your database into a SQL