Hello. 1. H2 is a small database engine and doesn't have an automatic upgrade procedure for database files. Unfortunately, latest releases also didn't mark their files as incompatible with older versions, so if you tried to open a database file created by one version in another it may lead to database corruption. In some cases these files can still be opened by the old version, but if you can open them, you should export the file to SQL immediately and create a new database with that SQL. The next version of H2 will mark its files as incompatible with older versions explicitly to avoid such issues.
The normal upgrade procedure for H2 is SCRIPT TO 'filename.sql' with the OLD version, creation of a new database file with the NEW version and execution of RUNSCRIPT FROM 'filename.sql' in it. https://h2database.com/html/tutorial.html#upgrade_backup_restore If you use the same database file in multiple applications, make sure they all have the same version of H2. 2. Unfortunately, 1.4.200 has some storage problems, it is less reliable than 1.4.199 in that area and may potentially corrupt database file by itself in some cases. If you have a backup copy, just use it. If it was created by another version, use SCRIPT / RUNSCRIPT to copy data to the new database. If you don't have it, you can try to use the recover tool: https://h2database.com/html/advanced.html#using_recover_tool If database file was somehow used by different versions of H2, you may want to try the all (but make a copy of existing corrupted file and use a new copy for each experiment for more safety). Your application normally should invoke the online backup command from time to time: https://h2database.com/html/commands.html#backup -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/5deccc9c-1214-424e-a47a-1d31a0d71df8n%40googlegroups.com.
