Thanks for the hints, but my main concern was not to recover the data. It turns out that only a few records out of almost 20 million in the original database was causing NPE. Those records could not be selected or deleted without causing NPE. I therefore copied all other records using a new table: "CREATE TABLE ParameterValueCopy AS (SELECT * FROM ParameterValue WHER id <> [brokenId])", and fortunately managed to recover all other data.
My main concern was to know if this is a known / fixed issue, or if it will be fixed. I'm sorry to say that we've had our share of problems with H2 corrupting our databases now. Even though we have worked around some problems (like auto detecting faulty ones and archiving them), we are now considering looking elsewhere for a solution to our data storage requirements. I really appreciate all hard work that Thomas has put in to this project, but data integrity is our most important requirement, and H2 just has not been as reliable as we had hoped in this regard. /Mikael On Tuesday, February 16, 2016 at 10:42:13 AM UTC+1, Noel Grandin wrote: > > Once a DB has been corrupted, there is not much that can be done. > > You can run the Recovery tool to generate a SQL dump, but its not at all > guaranteed that it will recover all of the data. > -- 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 https://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
