-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error after upgrade to 3.15.00 #518
Comments
Jeremy - There is a migration tool mentioned that you might want to try https://www.h2database.com/html/migration-to-v2.htmlSent from my iPhoneOn Aug 28, 2023, at 5:15 PM, RSCCD-JeremyCollins ***@***.***> wrote:
After upgrade from 3.14.00 to 3.15.00 following the procedure in the release notes, I get a 503 error in the browser. The logs have a message "org.h2.mvstore.MVStoreException: The write format 2 is smaller than the supported format 3 [2.2.220/5]" which Google tells me is a H2 DB wrong version message. I'm guessing there was a H2 DB format change from in H2 between 2.1.210 and 2.2.220 that the bastillion-upgrade-4.00.01.jar isn't upgrading far enough to make version 2.2.220 work.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
@RSCCD-JeremyCollins have you been able to fix the 503? If so, do you remember what you did to fix it? |
@skavanagh The H2 developers increased the database format version once more for H2 version 2.2.220+ (see the corresponding PR). Since the 3.15.00 release of Bastillion contains the update to H2 2.2.220, updating Bastillion will once again require a database migration. The
The migration tool should support upgrading to the new write format, but I could not get it to work. Would it be possible for you to update the bastillion-upgrade tool to support upgrading to the new write format? As far as I understand the process should stay the same - export with old driver and import with new driver, right? On another note: H2 2.2.220 apparently had a race condition which could cause DB corruption - this was fixed in 2.2.222. H2 2.2.222 had a performance regression fixed in 2.2.224. I don't know if these issues affect the Bastillion DB, but it might be better to update H2 to 2.2.224 to be on the safe side. |
After upgrade from 3.14.00 to 3.15.00 following the procedure in the release notes, I get a 503 error in the browser. The logs have a message "org.h2.mvstore.MVStoreException: The write format 2 is smaller than the supported format 3 [2.2.220/5]" which Google tells me is a H2 DB wrong version message. I'm guessing there was a H2 DB format change from in H2 between 2.1.210 and 2.2.220 that the bastillion-upgrade-4.00.01.jar isn't upgrading far enough to make version 2.2.220 work.
The text was updated successfully, but these errors were encountered: