dhis2-users team mailing list archive

[Victor Garcia <vgarciabnz@xxxxxxxxx>]

Hi Elmarie,

Based on the log I cannot say that it is the same issue, but we have
experienced some similar problems with servers in different time zones,
mainly when the timezone has daylight saving and it falls at midnight
(0:00:00.000). Our guess was that DHIS2 sets by default the hour to
midnight when only a date is provided. And it seems that Java date parser
has problems with that.

Regards,

Víctor

On Wed, 11 Jul 2018 at 13:21, Elmarie Claasen <elmarie@xxxxxxxx> wrote:

> Hi all,
>
>
>
> We have a particular issue with a Namibian instance (war 2.27) which was
> initially installed with a South African locale on the server and data
> captured using this time. After a few years it was now changed by the
> Ministry to Namibian locale when they took over hosting of the instance on
> their network infrastructure. There is a 1hr difference between the 2
> locales.
>
>
>
> We now find issues with generating resource tables and have narrowed it
> down to failing on the _periodstructure table
>
>
>
>
>
>
>
> When we restore the same database back on a server with SA locale
> everything runs fine so can only conclude that it is the locale change
> which  makes some periods invalid but we have done numerous data checks on
> all relevant tables, but have found no apparent issues with any of the
> periods or data.
>
>
>
> Does anyone have experience with moving database locales or what the
> problem could be?
>
>
>
> Regards,
>
>
>
> *Elmarie Claasen*
>
> [image: Hisp logo]
>
> Project Manager
>
> Health Information Systems Program
>
> Tel:      041-367 1027
>
> Cell:     082 374 2209
>
> E-mail: elmarie@xxxxxxxx
>
> Skype:  elmarie.claasen52
>
>
>
> *This message and any attachments are subject to a disclaimer published at
> http://www.hisp.org/policies.html#comms_disclaimer
> <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@xxxxxxxx
> <disclaimer@xxxxxxxx> 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.*
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>