Do you mean the migration tool as UI? The database has already been migrated by exporting it to SQL and importing it with the FROM_1X appendix. So I do not expect any problems at this step. Importing from SQL should create a valid database file.
The current status is that I have one case where the BACKUP TO statement created database file that corrupts when executing a SHUTDOWN COMPACT on it. I could not reproduce it but I try to repeat creating backups with BACKUP TO and check if the database files are ok. [email protected] schrieb am Freitag, 10. Juni 2022 um 12:26:08 UTC+2: > Use the UI I sent to you. It takes care of those challenges. > > > > Sent from my Galaxy > > > -------- Original message -------- > From: Ulrich <[email protected]> > Date: 10/06/2022 12:21 (GMT+01:00) > To: H2 Database <[email protected]> > Subject: Re: [h2] Database corrupted after SHUTDOWN COMPACT > > Stop, I am silly. It overlooked that the file created by the BACKUP > command is a zip file. I tried to use it as database file... > > -- > 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/6cc93937-85e4-490d-aba9-78daf40cfc85n%40googlegroups.com > > <https://groups.google.com/d/msgid/h2-database/6cc93937-85e4-490d-aba9-78daf40cfc85n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/98d6611c-00d6-426e-ba24-5c5e4da116cdn%40googlegroups.com.
