Hi David/Devs,
Did you get this problem sorted out.
We also have the same problem after updating one of our instances from 2.19 > 2.20 but strangely enough another instance updated to 2.20 runs analytics perfectly fine.
Here is the build version we updated to and an extract from the analytics log that gave errors.
We don’t have the SQL views mentioned in the log as SQLviews in our database thus it must be part of the Core code.
Can someone assist with what is wrong please?
Regards,
Elmarie Claasen
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: elmarie@hisp.org
Skype: elmarie.claasen52
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.
ERROR analytics ishp_s.docx (14.4 KB)
···
From: Dhis2-users [mailto:dhis2-users-bounces+elmarie=hisp.org@lists.launchpad.net] On Behalf Of Marko David Garcia
Sent: 24 July 2015 08:56 PM
To: dhis2-users@lists.launchpad.net
Subject: [Dhis2-users] Analytics error
Hello all.
After migrate from 2.19 to 2.20 version, the analytics process generate an error.
ERROR: column “de” does not exist
Why this error might occur?.
Attach the catalina.out file.
Thank you very much.
Best regards.
Mag. (c). Marko David Garcia M.
Ingeniería Telemática
Universidad del Cauca
Skype: marko_david
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.