dhis2-users team mailing list archive

["Raminosoa Rabemanantsoa, Tantely" <traminosoa@xxxxxxxxxx>]

Thank you Knut for this valuable information! We are crossing our fingers
and hope that DHIS2 2.22 will be set up correctly.

Regards,

Tantely.


On Fri, Mar 25, 2016 at 11:21 AM, Knut Staring <knutst@xxxxxxxxx> wrote:

> Hi,
>  Bob wrote a nice step-by-step here:
> https://lists.launchpad.net/dhis2-users/msg08793.html
>
> I think the most tricky point may be around the shift in encryption
> mechanisms for passwords in 2.21, as described in the notes.
>
> With systematic  backups in the beginning and along the way, and starting
> and stopping of Tomcat etc, and checking that things are ok, it may take
> few hours.
>
> Good luck,
> Knut
>
> On Fri, Mar 25, 2016 at 7:26 AM, Raminosoa Rabemanantsoa, Tantely <
> traminosoa@xxxxxxxxxx> wrote:
>
>> Hello everyone,
>>
>>
>> We are using DHIS2 2.19 and we are planning to upgrade to the 2.22
>> version. We have been informed about the upgrade script like the one
>> mentioned here
>> https://github.com/dhis2/dhis2-utils/blob/master/resources/sql/upgrade-220.sql
>> and we would like to ask if there is an upgrade procedure for us to follow
>> in order to keep all the components for the new version (data values, data
>> elements, data sets, indicators…). Do you have some idea on how long this
>> procedure may take?
>>
>>
>> Regards,
>>
>>
>> Tantely
>>
>> *This message and its attachments are confidential and solely for the
>> intended recipients. If received in error, please delete them and notify
>> the sender via reply e-mail immediately.*
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-users
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>
>
> --
> Knut Staring
> Dept. of Informatics, University of Oslo
> Norway: +4791880522
> Skype: knutstar
> http://dhis2.org
>

-- 
*This message and its attachments are confidential and solely for the 
intended recipients. If received in error, please delete them and notify 
the sender via reply e-mail immediately.*