Just adding my experience to confirm Rob's scenario: my desktop app has thousands of users, uses H2 1.3.176, and also occasionally suffers from similar corruption. Customer databases occasionally become corrupted. The rate of corruption was much worse in earlier H2 versions. Customer databases are typically some gigabytes in size. As best I can tell from limited information, sudden loss of power is a major cause of the problem.
A couple of years ago I attempted to add a "CHECK DATABASE" to H2 command that would read each row in each table and index, but got overwhelmed by the task. I'm keen and available to help in any way to improve this corruption situation. I recently tried updating my desktop app to the the latest H2 1.4 update, albeit with MVSTORE disabled. The database corruption rate was much worse, and I needed to revert to 1.3.176. -- 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 h2-database+unsubscr...@googlegroups.com. To post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
