You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
Thank you Elmarie for the quick and very helpful response. I have downloaded the upgrade scripts, where can I find the upgrade procedure documentation? Or do I just run the upgrade script and then replace the war file with the newer version?
···
On Wed, Oct 3, 2018 at 9:31 AM Elmarie Claasen elmarie@hisp.org wrote:
Hi Walusiki,
You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
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.
On Wed, Oct 3, 2018 at 7:59 AM Walusiku Muyunda jomuwalu@gmail.com wrote:
Thank you Elmarie for the quick and very helpful response. I have downloaded the upgrade scripts, where can I find the upgrade procedure documentation? Or do I just run the upgrade script and then replace the war file with the newer version?
On Wed, Oct 3, 2018 at 9:31 AM Elmarie Claasen elmarie@hisp.org wrote:
Hi Walusiki,
You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
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.
When I execute the script in postgresql query window I get a result in 1sec with only 1 row affected. That does not seem to be good. The documentation next to the download only show what has been moved.
Looks like the upgrade script run just fine, but is there a way to verify that everything upgraded correctly besides waiting for users to report something thats not working?
There is a little bit of trickery involved with the upgrade from 2.29 to 2.30. It has been discussed earlier in this group I believe. It is related to the loading of the postgis extension.
So it is quite important to understand which user you connect the database to run the upgrade.sql script, which user owns the database and its contents and which user is being used in dhis.conf to connect to the database. If you can let us know these I can alert you to some potential problems.
Generally, look at the log file while the dhis2 is starting up and see if there are any issues flagged there. It is not foolproof, but a good start.
Looks like the upgrade script run just fine, but is there a way to verify that everything upgraded correctly besides waiting for users to report something thats not working?
Thank you.
On Wed, Oct 3, 2018 at 3:38 PM Walusiku Muyunda jomuwalu@gmail.com wrote:
Using PostgreSQL query window. What am I supposed to use?
When I execute the script in postgresql query window I get a result in 1sec with only 1 row affected. That does not seem to be good. The documentation next to the download only show what has been moved.
On Wed, Oct 3, 2018 at 7:59 AM Walusiku Muyunda jomuwalu@gmail.com wrote:
Thank you Elmarie for the quick and very helpful response. I have downloaded the upgrade scripts, where can I find the upgrade procedure documentation? Or do I just run the upgrade script and then replace the war file with the newer version?
On Wed, Oct 3, 2018 at 9:31 AM Elmarie Claasen elmarie@hisp.org wrote:
Hi Walusiki,
You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
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.
Thank you Bob for the insight. Am currently trying to upgrade from 2.28 to 2.29(since its recommended to for the sequential releases) then later when am sure the upgrade was successful, I’ll upgrade to 2.30 and I’ll keep your comments in mind. Am using the dhis user to connect to the data and its the same as in the config file.
Watching the log file showed some error with a missing analytics table repeated a number of times, could be be other errors I may have missed.
There is a little bit of trickery involved with the upgrade from 2.29 to 2.30. It has been discussed earlier in this group I believe. It is related to the loading of the postgis extension.
So it is quite important to understand which user you connect the database to run the upgrade.sql script, which user owns the database and its contents and which user is being used in dhis.conf to connect to the database. If you can let us know these I can alert you to some potential problems.
Generally, look at the log file while the dhis2 is starting up and see if there are any issues flagged there. It is not foolproof, but a good start.
Looks like the upgrade script run just fine, but is there a way to verify that everything upgraded correctly besides waiting for users to report something thats not working?
Thank you.
On Wed, Oct 3, 2018 at 3:38 PM Walusiku Muyunda jomuwalu@gmail.com wrote:
Using PostgreSQL query window. What am I supposed to use?
When I execute the script in postgresql query window I get a result in 1sec with only 1 row affected. That does not seem to be good. The documentation next to the download only show what has been moved.
On Wed, Oct 3, 2018 at 7:59 AM Walusiku Muyunda jomuwalu@gmail.com wrote:
Thank you Elmarie for the quick and very helpful response. I have downloaded the upgrade scripts, where can I find the upgrade procedure documentation? Or do I just run the upgrade script and then replace the war file with the newer version?
On Wed, Oct 3, 2018 at 9:31 AM Elmarie Claasen elmarie@hisp.org wrote:
Hi Walusiki,
You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
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.
Upgrading from 2.28 to 2.29 should be smooth enough. At least I haven’t heard of issues. There a few hazards with the next step as I indicated. What operating system platform are you on?
Thank you Bob for the insight. Am currently trying to upgrade from 2.28 to 2.29(since its recommended to for the sequential releases) then later when am sure the upgrade was successful, I’ll upgrade to 2.30 and I’ll keep your comments in mind. Am using the dhis user to connect to the data and its the same as in the config file.
Watching the log file showed some error with a missing analytics table repeated a number of times, could be be other errors I may have missed.
There is a little bit of trickery involved with the upgrade from 2.29 to 2.30. It has been discussed earlier in this group I believe. It is related to the loading of the postgis extension.
So it is quite important to understand which user you connect the database to run the upgrade.sql script, which user owns the database and its contents and which user is being used in dhis.conf to connect to the database. If you can let us know these I can alert you to some potential problems.
Generally, look at the log file while the dhis2 is starting up and see if there are any issues flagged there. It is not foolproof, but a good start.
Looks like the upgrade script run just fine, but is there a way to verify that everything upgraded correctly besides waiting for users to report something thats not working?
Thank you.
On Wed, Oct 3, 2018 at 3:38 PM Walusiku Muyunda jomuwalu@gmail.com wrote:
Using PostgreSQL query window. What am I supposed to use?
When I execute the script in postgresql query window I get a result in 1sec with only 1 row affected. That does not seem to be good. The documentation next to the download only show what has been moved.
On Wed, Oct 3, 2018 at 7:59 AM Walusiku Muyunda jomuwalu@gmail.com wrote:
Thank you Elmarie for the quick and very helpful response. I have downloaded the upgrade scripts, where can I find the upgrade procedure documentation? Or do I just run the upgrade script and then replace the war file with the newer version?
On Wed, Oct 3, 2018 at 9:31 AM Elmarie Claasen elmarie@hisp.org wrote:
Hi Walusiki,
You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
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.
Upgrading from 2.28 to 2.29 should be smooth enough. At least I haven’t heard of issues. There a few hazards with the next step as I indicated. What operating system platform are you on?
Thank you Bob for the insight. Am currently trying to upgrade from 2.28 to 2.29(since its recommended to for the sequential releases) then later when am sure the upgrade was successful, I’ll upgrade to 2.30 and I’ll keep your comments in mind. Am using the dhis user to connect to the data and its the same as in the config file.
Watching the log file showed some error with a missing analytics table repeated a number of times, could be be other errors I may have missed.
There is a little bit of trickery involved with the upgrade from 2.29 to 2.30. It has been discussed earlier in this group I believe. It is related to the loading of the postgis extension.
So it is quite important to understand which user you connect the database to run the upgrade.sql script, which user owns the database and its contents and which user is being used in dhis.conf to connect to the database. If you can let us know these I can alert you to some potential problems.
Generally, look at the log file while the dhis2 is starting up and see if there are any issues flagged there. It is not foolproof, but a good start.
Looks like the upgrade script run just fine, but is there a way to verify that everything upgraded correctly besides waiting for users to report something thats not working?
Thank you.
On Wed, Oct 3, 2018 at 3:38 PM Walusiku Muyunda jomuwalu@gmail.com wrote:
Using PostgreSQL query window. What am I supposed to use?
When I execute the script in postgresql query window I get a result in 1sec with only 1 row affected. That does not seem to be good. The documentation next to the download only show what has been moved.
On Wed, Oct 3, 2018 at 7:59 AM Walusiku Muyunda jomuwalu@gmail.com wrote:
Thank you Elmarie for the quick and very helpful response. I have downloaded the upgrade scripts, where can I find the upgrade procedure documentation? Or do I just run the upgrade script and then replace the war file with the newer version?
On Wed, Oct 3, 2018 at 9:31 AM Elmarie Claasen elmarie@hisp.org wrote:
Hi Walusiki,
You should always run sequential upgrades to the next version as there may be upgrade scripts for each version. After upgrade you need to start up the instance and then you can proceed to the next version.
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.