Ok I updated to h2-1.4.192 and switched to the MV database format. Let's see if I'll get corruption again.
On Friday, June 10, 2016 at 11:53:54 AM UTC+2, Steve McLeod wrote: > > You should at the very least be using H2 1.3.176, the most recent stable > version. I suggest doing that and seeing if you get less corruption > problems. > > > > On Thursday, 9 June 2016 16:30:17 UTC+2, Paul Erdos wrote: >> >> Hello, >> I get very often corrupted H2 databases, I'm able to recover them with >> the recovery tool but this is getting annoying because while the database >> is corrupt all insertions fail. >> >> I'm using one of the latest H2 stable releases "h2-1.3.172.jar" yet the >> database gets corrupt, by analysing the database I realize somehow more >> than one row with the same unique id is inserted in a table with several >> thousands rows. >> Hence further insertions in the table fail. >> >> The database is shared between 2 windows machines running Java with the >> connection String >> "jdbc:h2:C:\HomeDir\db\mydb;create=true;AUTO_SERVER=TRUE;AUTO_RECONNECT=TRUE;TRACE_MAX_FILE_SIZE=3" >> >> The database would work well if it weren't for these sporadic corruptions >> which happen regularly every month or so. >> >> Thank you for your help. >> >> >> >> -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
