Upgrade from 2.30 to 2.32 - to do

Hello @phil, if we want to upgrade from 2.30 to 2.32, would it be a straightforward 2.30 to 2.31.5 to 2.32 or would we have to do the incremental patches on 2.31 before the 2.32?


Hi Dr @ifeanyiokoye,

There is no need to upgrade the incremental patches. You can think of 2.31.x patches, for example, as just points in time along the 2.31 branch; the latest patch being the last point that we performed additional validation to ensure a stable point.

In fact, because database upgrades above 2.30 are handled by Flyway, you don’t even have to do the intermediate step to 2.31.5 at all - you can upgrade from 2.30 directly to 2.32.1! Flyway will take care of any/all of the incremental database upgrades through 2.31 and 2.32 in the correct order. It is done as a single transaction, so any problems during the upgrade will cause everything to be rolled back (of course, we still recommend having a backup etc.). The only problems people seem to have had during upgrades seem to be caused by not deleting SQL Views, or external functions in their DB, prior to the upgrade: So, if you have any issues you can search on this community, and if necessary reach out to us!.

Also, remember to check the Upgrade Note (dhis2-releases/README.md at master · dhis2/dhis2-releases · GitHub) for specific preparations for the 2.32 upgrade.

I hope that helps!
Kind regards,

P.S. 2.32.2 patch should be available in a couple of weeks! :wink:


@phil does this still hold for upgrades from 2.30 to 2.39? The documentation says “there is no need to upgrade to intermediate versions; in fact, it is not recommended,” is this applicable to this kind of jump? Hearing it from experts will be more comforting considering the time since 2.30 and flyway upgrades were introduced. :slight_smile:

1 Like

Thanks @WaluQ!

The Upgrading docs confirms that from at least 2.30 there is no need to “version-by-version, manually,” and it’s advised that from v2.30:

  1. Read all of the upgrade notes from your current version up to the target version on our releases site. Make sure your environment meets all of the requirements
  2. Make a copy of your database if you didn’t do so in step 1
  3. Drop any materialized SQL views from your database
  4. Stop the server
  5. Replace the war file with the target version (There is no need to upgrade to intermediate versions; in fact, it is not recommended)
  6. Start the server

You should now be ready to enjoy the new fixes and features.

:100: rest assured the docs are up to date with the same recommendation! Thanks @WaluQ for your post.

1 Like

Old topic post. Information is still relevant. Here’s the link to the docs: Upgrading - DHIS2 Documentation

If you have more questions please start a new topic post, and if you believe this topic post doesn’t need to be closed, please DM.

Thank you!