I have a couple of 2.16 installations that should probably be brought up to date.
What are the major caveats I should be looking out for and what is the latest stable DHIS2 version that I should be aiming for? It’s critical that service be maintained for the client, I will run the upgrades on another box and validate them before updating live but I wondered if anyone had anything specific that comes to mind that I should look out for or be aware prior to upgrading. Do I need to upgrade incrementally?
Wow this is quite far back. We upgrading some instances from 2.20 now and everything is going fine, provided that you drop SQL views before the upgrade. SQL views often hold table updates effected through war upgrades. From 2.23 to 2.23 you need to read about changes required to sms config if used.
Read the upgrade documentation for each version, some has scripts which you must run, others execute an upgrade routine with first startup of the war file.
We have find issues when not upgrading incrementally and also starting up the server after each upgrade, so this is recommended. You may find it difficult to find the link to older war files but check the URL for download of newer versions and just change the version number in the war accordingly.
I would take care if any of the implementations are tracker because tracker got a major overhaul since then including changes in tables. You will find apps like individual records etc chenging to tracker and event capture.
Through learning some hard lessons we usually upgrade on a test instance first and test all existing functionality properly. Also had some issues with table or column updates so we download a Sierra Leone database of the same version and compare the tables and columns in that instance vs ours with a SQL view.
Good luck
Elmarie
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer. Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
I have a couple of 2.16 installations that should probably be brought up to date.
What are the major caveats I should be looking out for and what is the latest stable DHIS2 version that I should be aiming for? It’s critical that service be maintained for the client, I will run the upgrades on another box and validate them before updating live but I wondered if anyone had anything specific that comes to mind that I should look out for or be aware prior to upgrading. Do I need to upgrade incrementally?
Wow this is quite far back. We upgrading some instances from 2.20 now and everything is going fine, provided that you drop SQL views before the upgrade. SQL views often hold table updates effected through war upgrades. From 2.23 to 2.23 you need to read about changes required to sms config if used.
Read the upgrade documentation for each version, some has scripts which you must run, others execute an upgrade routine with first startup of the war file.
We have find issues when not upgrading incrementally and also starting up the server after each upgrade, so this is recommended. You may find it difficult to find the link to older war files but check the URL for download of newer versions and just change the version number in the war accordingly.
I would take care if any of the implementations are tracker because tracker got a major overhaul since then including changes in tables. You will find apps like individual records etc chenging to tracker and event capture.
Through learning some hard lessons we usually upgrade on a test instance first and test all existing functionality properly. Also had some issues with table or column updates so we download a Sierra Leone database of the same version and compare the tables and columns in that instance vs ours with a SQL view.
I have a couple of 2.16 installations that should probably be brought up to date.
What are the major caveats I should be looking out for and what is the latest stable DHIS2 version that I should be aiming for? It’s critical that service be maintained for the client, I will run the upgrades on another box and validate them before updating live but I wondered if anyone had anything specific that comes to mind that I should look out for or be aware prior to upgrading. Do I need to upgrade incrementally?
This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer . Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. If you cannot access the disclaimer, kindly send an email to disclaimer@hisp.org and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.
Regarding version you should be aiming for, you should always aim to
be not more than 3 versions back from latest release. As security
issues arise and get addressed they are usually backported as far as
is practical. But the developers only guarantee security support for
the last 3 versions.
···
On 16 July 2017 at 21:38, Edward Robinson <erobinson@projectbalance.com> wrote:
Some excellent tips, thank you Elmarie.
Regards
Ed
From: Elmarie Claasen [mailto:elmarie@hisp.org]
Sent: Sunday, 16 July 2017 3:00 PM
To: Edward Robinson <erobinson@projectbalance.com>
Cc: DHIS 2 Users list <dhis2-users@lists.launchpad.net>
Subject: Re: [Dhis2-users] Upgrading from 2.16
Hi Edward,
Wow this is quite far back. We upgrading some instances from 2.20 now and
everything is going fine, provided that you drop SQL views before the
upgrade. SQL views often hold table updates effected through war upgrades.
From 2.23 to 2.23 you need to read about changes required to sms config if
used.
Read the upgrade documentation for each version, some has scripts which you
must run, others execute an upgrade routine with first startup of the war
file.
We have find issues when not upgrading incrementally and also starting up
the server after each upgrade, so this is recommended. You may find it
difficult to find the link to older war files but check the URL for download
of newer versions and just change the version number in the war accordingly.
I would take care if any of the implementations are tracker because tracker
got a major overhaul since then including changes in tables. You will find
apps like individual records etc chenging to tracker and event capture.
Through learning some hard lessons we usually upgrade on a test instance
first and test all existing functionality properly. Also had some issues
with table or column updates so we download a Sierra Leone database of the
same version and compare the tables and columns in that instance vs ours
with a SQL view.
Good luck
Elmarie
On 16 Jul 2017 20:10, "Edward Robinson" <erobinson@projectbalance.com> > wrote:
I have a couple of 2.16 installations that should probably be brought up to
date.
What are the major caveats I should be looking out for and what is the
latest stable DHIS2 version that I should be aiming for? It’s critical that
service be maintained for the client, I will run the upgrades on another box
and validate them before updating live but I wondered if anyone had anything
specific that comes to mind that I should look out for or be aware prior to
upgrading. Do I need to upgrade incrementally?
This message and any attachments are subject to a disclaimer published at Home - HISP-SA. Please read the
disclaimer before opening any attachment or taking any other action in terms
of this electronic transmission. If you cannot access the disclaimer,
kindly send an email to disclaimer@hisp.org and a copy will be provided to
you. By replying to this e-mail or opening any attachment you agree to be
bound by the provisions of the disclaimer.