Hi, Is there any chance to find the problem without sendig the database? > I hope, because this is not the first time, that an error occured. >
I'm afraid it will be very hard without having a reproducible test case. However, there might be a way: you can run your application using the recovery-test option: To test recovery, append ;RECOVER_TEST=64 to the database URL. This will simulate an application crash after each 64 writes to the database file. A log file named databaseName.h2.db.log is created that lists the operations. The recovery is tested using an in-memory file system, that means it may require a larger heap setting. If you find problems when using this setting, please tell me. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
