karimkkanji / kenyaemr-plus-issues

This is an External Issue Tracker for KenyaEMR Plus Issues Identified
Apache License 2.0
0 stars 0 forks source link

Error Starting KenyaEMR charts Module #3

Closed karimkkanji closed 3 years ago

karimkkanji commented 3 years ago

The Kenyaemr_etl and kenyaemr_datatools have been dropped and recreated using the following:

call create_etl_tables(); call sp_first_time_setup();

In mysql console and Tomcat restarted but the issue persists.

The following is an error observed in the console:

image

ngarivictor commented 3 years ago

you could try source a fresh 👇 kenyaemr_etl.zip

karimkkanji commented 3 years ago

Let me try again. Have tried deleting the databases and recreating them but the issue still persists

karimkkanji commented 3 years ago

The ETL Database shared has actually made it worse. Home Page graphs are now not appearing at all

karimkkanji commented 3 years ago

Running the following on MYSQL Shell might do the trick:

DROP DATABASE kenyaemr_etl;
DROP DATABASE kenyaemr_datatools;
USE openmrs;
CALL create_etl_tables();
CALL sp_first_time_setup();
ngarivictor commented 3 years ago

Let me know how it goes.

On Tue, 27 Jul 2021, 19:02 Karim K. Kanji, @.***> wrote:

Running the following on MYSQL Shell might do the trick:

DROP DATABASE kenyaemr_etl;DROP DATABASE kenyaemr_datatools; USE openmrs; CALL create_etl_tables(); CALL sp_first_time_setup();

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/karimkkanji/kenyaemr-plus-issues/issues/3#issuecomment-887636815, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADNRNNYLIL6ZDEORD6E26JTTZ3KBLANCNFSM5AYTDZLA .

karimkkanji commented 3 years ago

@ngarivictor It is a database issue. I have used the current database running in at the facility and it now works well. All modules work well. I had tried with the de-id database and the etl database you shared but that didn't work.

Issue: The openmrs Database might be having a schema issue or LIQUIBASE issue