Up until now we have been using H2-1.4.200 in production with multiple thousands of (mostly smallish) databases. Every now and then we get database corruptions. In all but one case, corrupted databases throw an exception during opening of the database. Since the recover-tool seems to open a database the same way as our application does recovering a corrupted database never worked for us since it throws the exact same exceptions...
EXCEPT!!! In all but a few cases opening the corrupted databases worked flawlessly using H2-1.4.196. I do not know why that is and just discovered it by accident. Therefore I was mostly able to recover/recreate the corrupted databases with H2-1.4.196 and from then on use them with H2-1.4.200 as if nothing ever happened. Problem solved! We are now using H2-2.1.214 in our development and test environments. It has improved a lot in comparison to H2-1.4.200 and we would like to migrate more databases to this version. However, also with the new version we have run into some database corruptions (probably mostly due to how we abuse Java processes during development). Just as before with H2-1.4.200 the recover tool would not open the corrupted databases so the data was lost indefinitely. Can the recover tool be manipulated to open a database in some form of "safe mode"? Or is there any other way to read a database file with the sole purpose of dumping the content of its tables? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/fbe6b35b-7b14-4bd5-abc3-96c1def6e8e8n%40googlegroups.com.
