Re: [Dhis2-devs] Moving directly from 2.18 to 2.20

2015-09-04 Thread Pamod Amarakoon
Thank you for the confirmation On Thu, Sep 3, 2015 at 8:40 PM, Victor Garcia wrote: > Thank you both for the comments. They are reassuring ;-) > > On 3 September 2015 at 09:46, Jason Pickering > wrote: > > And, be sure to remove everything in the tomcat/webapps/dhis directory > (or > > your loc

Re: [Dhis2-devs] Moving directly from 2.18 to 2.20

2015-09-03 Thread Victor Garcia
Thank you both for the comments. They are reassuring ;-) On 3 September 2015 at 09:46, Jason Pickering wrote: > And, be sure to remove everything in the tomcat/webapps/dhis directory (or > your local equivalent happens to be). You do not want to upgrade the WAR > file without also removing the di

Re: [Dhis2-devs] Moving directly from 2.18 to 2.20

2015-09-03 Thread Jason Pickering
And, be sure to remove everything in the tomcat/webapps/dhis directory (or your local equivalent happens to be). You do not want to upgrade the WAR file without also removing the director prior to starting Tomcat. Making a backup copy of your database, of course, is smart as well. :) Regards Jason

Re: [Dhis2-devs] Moving directly from 2.18 to 2.20

2015-09-03 Thread Lars Helge Øverland
Hi, Also, is it required (or safer) to run >> before the Upgrade SQL scripts? >> > You should stop the server, run the scripts, upgrade the war file, and then start the server. Lars > >> Thanks, >> >> Víctor >> >> ___ >> Mailing list: https://laun

Re: [Dhis2-devs] Moving directly from 2.18 to 2.20

2015-09-03 Thread Lars Helge Øverland
Hi Victor, it should work well. Make sure you run both upgrade scripts (2.19 and 2.20). regards, Lars On Thu, Sep 3, 2015 at 9:35 AM, Victor Garcia wrote: > Hi all, > > we are planning to move from version 2.18 to 2.20 (without installing > 2.19) and we have some concerns about the risks. We

[Dhis2-devs] Moving directly from 2.18 to 2.20

2015-09-03 Thread Victor Garcia
Hi all, we are planning to move from version 2.18 to 2.20 (without installing 2.19) and we have some concerns about the risks. We are only using aggregated values (but we'll use trackedEntities in the future) and, looking at the upgrade notes, it seems that there is nothing to be worried about. Al