Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.
I am sure someone eminently more qualified than myself will respond shortly, but I do have a couple of suggestions:
I wouldn’t attempt to migrate directly from 2.11 to 2.14; try upgrading in increments, one after the other – go to 2.12 and then 2.13 before making the move to 2.14. All you have to do is start up the instance on each version, then shut it down again once you have made sure it starts successfully. As each starts, it upgrades the database as required…
When moving from 2.3 to 2.14, make sure you have run the upgrade script on the database before starting the 2.14 instance. Refer to [http://www.dhis2.org/download/resources/convert-fixed-attributes-to-dynamic.sql](http://www.dhis2.org/download/resources/convert-fixed-attributes-to-dynamic.sql) and the documentation on dhis2.org.
This message may contain privileged and confidential information intended only for the person or entity to which it is addressed. Any review, retransmission, dissemination, copy or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient, is prohibited. If you received this message in error, please notify the sender immediately by e-mail, facsimile or telephone and thereafter delete the material from any computer. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the view of the entity transmitting the message.
Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.
Best
Marcio
–
Márcio Thomé
Coordenador
Departamento de Avaliação e Estatísticas
BEMFAM - Bem Estar Familiar no Brasil
Avenida Carlos Chagas Filho, 791. Ilha do Fundão.
Rio de Janeiro. 21941-599
Tel.: 55-21-30057207 R. 2408
The only way we can really help you is if you can include a copy of the logs from Tomcat when the exception occurs.I have upgraded from 2.10 to 2.14 directly, so it can be done. However, there were some issues related to duplicate orgunit groups which were very difficult to track down. Anyway, the logs may give a bit more insight.
Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.
Best
Marcio
Márcio Thomé
Coordenador
Departamento de Avaliação e Estatísticas
BEMFAM - Bem Estar Familiar no Brasil
Avenida Carlos Chagas Filho, 791. Ilha do Fundão.
Rio de Janeiro. 21941-599
Tel.: 55-21-30057207 R. 2408
Skype: Marcio-Deav
When you upgrade to 2.14, new column with the name attributeoptioncomboid will be created in datavalue table and it will populated with 0 by default. So you may run query to change this value from 0 to default categoryoptioncomboid (most of the cases it will be 1).
query will be some thing similar to: update datavalue set attributeoptioncomboid = 1 (here 1 is default categoryoptioncomboid)
Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.
Best
Marcio
Márcio Thomé
Coordenador
Departamento de Avaliação e Estatísticas
BEMFAM - Bem Estar Familiar no Brasil
Avenida Carlos Chagas Filho, 791. Ilha do Fundão.
Rio de Janeiro. 21941-599
Tel.: 55-21-30057207 R. 2408
Skype: Marcio-Deav
When you upgrade to 2.14, new column with the name attributeoptioncomboid will be created in datavalue table and it will populated with 0 by default. So you may run query to change this value from 0 to default categoryoptioncomboid (most of the cases it will be 1).
query will be some thing similar to: update datavalue set attributeoptioncomboid = 1 (here 1 is default categoryoptioncomboid)
Hi, this should happen automatically. Works on postgres, I guess what you are saying is that it does not work on mysql?
Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.
When you upgrade to 2.14, new column with the name attributeoptioncomboid will be created in datavalue table and it will populated with 0 by default. So you may run query to change this value from 0 to default categoryoptioncomboid (most of the cases it will be 1).
query will be some thing similar to: update datavalue set attributeoptioncomboid = 1 (here 1 is default categoryoptioncomboid)
Hi, this should happen automatically. Works on postgres, I guess what you are saying is that it does not work on mysql?
Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.
Thank you Bharath. It worked after runing the query to update datavalue set attributeoptioncomboid = 1! It is not being done automatically in MySQL, Lars. I can now visualize data entry done in 2.11 when running 2.14. But I am still having an exception error when running analytics.
I am attaching the Tomcat script with the erorr as suggested by Jason Pickering to see if you can help us sorting out why analytics is not working. it seems the application is stoping at the following error:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Too many keys specified; max 64 keys allowed
When you upgrade to 2.14, new column with the name attributeoptioncomboid will be created in datavalue table and it will populated with 0 by default. So you may run query to change this value from 0 to default categoryoptioncomboid (most of the cases it will be 1).
query will be some thing similar to: update datavalue set attributeoptioncomboid = 1 (here 1 is default categoryoptioncomboid)
Hi, this should happen automatically. Works on postgres, I guess what you are saying is that it does not work on mysql?
Is anyone out there that could help us in using DHIS2 2.14?
I am not being able to migrate from 2.11 to 2.14. I run DHIS2 2.14 with the old MySQL database but cannot visualize the data in data entry or in the reports. It is fine in 2.11. When I attempt to run Analytics I am confronted with an exception error. All the screen shots are attached. I am running on Apache Tomcat, MySQL, DHIS2 version 2.14 build 13815 and Version 2.11 build 10550.
Thank you for assisting. We are resisting in giving up on version 2.14 and hoping someone already had similar issues already resolved.