I don’t get the same issue with the 2.22 version – is there a specific postgres version requirement for 2.23 that I somehow missed, or is the demo data file corrupt, or have I missed something?
Kind Regards,
Jason Phillips
Information Systems / Infrastructure**
Health Information Systems Program
I don’t get the same issue with the 2.22 version – is there a specific postgres version requirement for 2.23 that I somehow missed, or is the demo data file corrupt, or have I missed something?
Kind Regards,
Jason Phillips
Information Systems / Infrastructure**
Health Information Systems Program
____________________________________**
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.
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 am afraid they were so many and so fast my Putty buffer ran out!
I suppose it is possible – but surely whether PostGIS is installed/configured or not, the postgres commands for table creation and data upload should still work?
Kind Regards,
Jason Phillips
Information Systems / Infrastructure**
Health Information Systems Program
···
On Fri, Jun 17, 2016, 15:46 Jason Phillips jason@hisp.org wrote:
I don’t get the same issue with the 2.22 version – is there a specific postgres version requirement for 2.23 that I somehow missed, or is the demo data file corrupt, or have I missed something?
Kind Regards,
Jason Phillips
Information Systems / Infrastructure**
Health Information Systems Program
____________________________________**
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.
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.
Well, it’s really hard to say unless you can provide some error log. Pipe the restore to a log file and then maybe we can help?
···
On Fri, Jun 17, 2016, 16:10 Jason Phillips jason@hisp.org wrote:
Hi Jason,
I am afraid they were so many and so fast my Putty buffer ran out!
I suppose it is possible – but surely whether PostGIS is installed/configured or not, the postgres commands for table creation and data upload should still work?
Kind Regards,
Jason Phillips
Information Systems / Infrastructure**
Health Information Systems Program
____________________________________**
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.
From: Jason Pickering [mailto:jason.p.pickering@gmail.com] Sent: Friday, 17 June 2016 4:00 PM To: Jason Phillips; DHIS 2 Users list Subject: Re: [Dhis2-users] 2.23 Demo Data Fault?
What are the errors specifically? Are they related to Postgis?
On Fri, Jun 17, 2016, 15:46 Jason Phillips jason@hisp.org wrote:
I don’t get the same issue with the 2.22 version – is there a specific postgres version requirement for 2.23 that I somehow missed, or is the demo data file corrupt, or have I missed something?
Kind Regards,
Jason Phillips
Information Systems / Infrastructure**
Health Information Systems Program
____________________________________**
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.
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.
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.
