Metabase upgrade failure from 0.43.7.3 to 0.44.7.3

Get Help
1

Hi all, i encountered the below error when upgrading from 0.43.7.3 to 0.44.7.3.

I am new to metabase, any help offered will be appreciated.

Database: (EnterpriseDB Advanced Server 12.22.27)
java:Openjdk version "17.0.18" 2026-01-20 LTS
OS: Centos stream 9

-Xms1024m -Xmx12g

May 02 22:28:03 localhost.localdomain java[1555131]: 2026-05-02 22:28:03,113 INFO db.setup :: Liquibase is ready.
May 02 22:28:03 localhost.localdomain java[1555131]: 2026-05-02 22:28:03,114 INFO db.liquibase :: Checking if Database has unrun migrations...
May 02 22:28:03 localhost.localdomain java[1555131]: 2026-05-02 22:28:03,882 ERROR metabase.core :: Metabase Initialization FAILED
May 02 22:28:03 localhost.localdomain java[1555131]: liquibase.exception.LiquibaseException: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
May 02 22:28:03 localhost.localdomain java[1555131]: at liquibase.changelog.ChangeLogIterator.run(ChangeLogIterator.java:126)
May 02 22:28:03 localhost.localdomain java[1555131]: at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:289)
May 02 22:28:03 localhost.localdomain java[1555131]: at liquibase.Liquibase$16.run(Liquibase.java:1988)
May 02 22:28:03 localhost.localdomain java[1555131]: at liquibase.Scope.lambda$child$0(Scope.java:180)
May 02 22:28:03 localhost.localdomain java[1555131]: at liquibase.Scope.child(Scope.java:189)
May 02 22:28:03 localhost.localdomain java[1555131]: at liquibase.Scope.child(Scope.java:179)

2

That is an old version of Metabase, 3 years old.

I didn’t find anyone else with a similar issue. ArrayIndexOutOfBoundsExceptions in Liquibase usually stem from SQL errors.

Best I can suggest is to try jumping to a newer version, say 0.45.x, and try that. Make sure you have a backup of your app database first (and make sure 0.43 still starts up okay) before making any more changes.

The general procedure is to upgrade one major upgrade at a time, to the latest minor version of each major version. This reduces the database migration transaction size. This gets especially important when you get to around 0.49 where there is a major permissions reorganization that can take a long time to run if you have a large number of users/tables.

Be aware of a couple of other changes that will crop up:

  • Metabase 53 requires Java 21.
  • PostgreSQL 12 stops being supported along the way. I don’t know if there is anything that needs newer features, but in very recent 0.59 there is a version check that will block the upgrade if you are running anything earlier than PostgreSQL 14. Best I can tell, EDB Advanced Server 12 support has ended, so it’s time to upgrade that anyway.

For our info, if you can start up 0.43 again and post the diagnostic info from Admin, that will let us know some of your environment details.