FW: Problem with Tracker program after updating to 2.20 stable

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    
  2.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

Regards,

Elmarie Claasen

Hisp logo

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.

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.

Analytics Error log.txt (18.8 KB)

Open Program error log.txt (14 KB)

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

image

···

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

Regards,

Elmarie Claasen

Hisp logo

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.

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.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot

Thanks a lot Abyot,

We ran this script after deleting 2 sql views which referenced this table as it would not run until we deleted the 2 sql views. A follow up question –could it be that this change did not execute because of the 2 sql views? We know that dhis2 drops sql views before running analytics but does it check/drop sql views before making changes to tables?

Regards,

Elmarie Claasen

Hisp logo

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.

···

From: Abyot Gizaw [mailto:abyota@gmail.com]
Sent: 30 July 2015 12:59 PM
To: Elmarie Claasen; dhis2-devs@lists.launchpad.net; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

Regards,

Elmarie Claasen

Hisp logo

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.

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.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot

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.

In addition; please look at the startup log of dhis2 (specifically under InitTableAlterator) and see if there’s any queries failing.

image

···

2015-07-30 12:59 GMT+02:00 Abyot Gizaw abyota@gmail.com:

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

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.

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.


Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Hi Halvdan,

I don’t see anything failing in the startup routine – here is the log of the first startup after the replaced the war file. Maybe the log should give an error if the tables was not successfully updated?

Can you assist in how we fix the problem with the analytics table which still has an incorrect fieldname – “de” instead of “dx”. The issue with the Program was resolved after running the script Abyot suggested but the analytics table is a temp table created during the analytics process or something since our db does not contain that table?

015-07-29 08:31:56,705 Executing startup routine [1 of 15, runlevel 1]: InitTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,906 Executing startup routine [2 of 15, runlevel 2]: PeriodTypePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,911 Executing startup routine [3 of 15, runlevel 2]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,961 Linked default category with default concept (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:57,171 Executing startup routine [4 of 15, runlevel 3]: TableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,337 Tables updated (TableAlteror.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,337 Executing startup routine [5 of 15, runlevel 3]: TrackerIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,704 Executing startup routine [6 of 15, runlevel 3]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,798 Executing startup routine [7 of 15, runlevel 4]: TrackedEntityTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,640 Executing startup routine [8 of 15, runlevel 4]: IdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,816 Executing startup routine [9 of 15, runlevel 5]: TableCreator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,880 Executing startup routine [10 of 15, runlevel 7]: MapViewUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,973 Executing startup routine [11 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,032 Update done, dropped table reporttable_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,041 Update done, dropped table reporttable_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,045 Update done, dropped table reporttable_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,049 Update done, dropped table reporttable_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,057 Update done, dropped table chart_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,061 Update done, dropped table chart_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,065 Update done, dropped table chart_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,069 Update done, dropped table chart_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,073 Update done, dropped table mapview_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,076 Update done, dropped table mapview_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,080 Update done, dropped table mapview_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,083 Update done, dropped table mapview_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,189 Executing startup routine [12 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,191 Upgraded custom case entry form identifiers (DataEntryFormUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,193 Executing startup routine [13 of 15, runlevel 8]: ExpressionUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,214 Executing startup routine [14 of 15, runlevel 9]: ConfigurationPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,218 Executing startup routine [15 of 15, runlevel 9]: I18nLocalePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,228 All startup routines done (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.HostConfig deployWAR

INFO: Deployment of web application archive /home/hisp/tomcat8-dhis2-2/webapps/staging.war has finished in 53,298 ms

Jul 29, 2015 8:32:12 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler [“http-nio-8081”]

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 53351 ms

Regards,

Elmarie Claasen

Hisp logo

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.

···

From: Halvdan Grelland [mailto:halvdanhg@gmail.com]
Sent: 30 July 2015 02:33 PM
To: Abyot Gizaw
Cc: Elmarie Claasen; DHIS 2 Developers list; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-devs] [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

In addition; please look at the startup log of dhis2 (specifically under InitTableAlterator) and see if there’s any queries failing.

2015-07-30 12:59 GMT+02:00 Abyot Gizaw abyota@gmail.com:

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

Regards,

Elmarie Claasen

Hisp logo

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.

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.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

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.

May be. I don’t think you can alter a table while you have views or user defined functions referring to the table.

image

···

On Thu, Jul 30, 2015 at 1:33 PM Elmarie Claasen elmarie@hisp.org wrote:

Thanks a lot Abyot,

We ran this script after deleting 2 sql views which referenced this table as it would not run until we deleted the 2 sql views. A follow up question –could it be that this change did not execute because of the 2 sql views? We know that dhis2 drops sql views before running analytics but does it check/drop sql views before making changes to tables?

Regards,

Elmarie Claasen

Hisp logo

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.

From: Abyot Gizaw [mailto:abyota@gmail.com]
Sent: 30 July 2015 12:59 PM
To: Elmarie Claasen; dhis2-devs@lists.launchpad.net; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

Regards,

Elmarie Claasen

Hisp logo

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.

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.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot

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.


Thank you,

Abyot

Hi,

Yes, the first issue seems to be fixed (and there is no indication of faults in the log as you say). Why it didn’t run properly before I don’t know.

As for the analytics: yes, analytics tables (named analytics_2014, analytics_2015 etc) er generated tables. If they do not exist, you might experience expections like the one posted. Analytics can be scheduled (recommended) to run regularly or triggered manually at https://your-dhis-server/dhis-web-reporting/displayDataMartForm.action (the process will take a lot of time to finish, depending on the server and the DB contents).

Try to run an analytics update and try again. It will probably solve the issue.

image

···

2015-07-30 15:17 GMT+02:00 Elmarie Claasen elmarie@hisp.org:

Hi Halvdan,

I don’t see anything failing in the startup routine – here is the log of the first startup after the replaced the war file. Maybe the log should give an error if the tables was not successfully updated?

Can you assist in how we fix the problem with the analytics table which still has an incorrect fieldname – “de” instead of “dx”. The issue with the Program was resolved after running the script Abyot suggested but the analytics table is a temp table created during the analytics process or something since our db does not contain that table?

015-07-29 08:31:56,705 Executing startup routine [1 of 15, runlevel 1]: InitTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,906 Executing startup routine [2 of 15, runlevel 2]: PeriodTypePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:31:56,911 Executing startup routine [3 of 15, runlevel 2]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:31:56,961 Linked default category with default concept (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])
  • INFO 2015-07-29 08:31:57,171 Executing startup routine [4 of 15, runlevel 3]: TableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,337 Tables updated (TableAlteror.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,337 Executing startup routine [5 of 15, runlevel 3]: TrackerIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,704 Executing startup routine [6 of 15, runlevel 3]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,798 Executing startup routine [7 of 15, runlevel 4]: TrackedEntityTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,640 Executing startup routine [8 of 15, runlevel 4]: IdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,816 Executing startup routine [9 of 15, runlevel 5]: TableCreator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,880 Executing startup routine [10 of 15, runlevel 7]: MapViewUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,973 Executing startup routine [11 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,032 Update done, dropped table reporttable_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,041 Update done, dropped table reporttable_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,045 Update done, dropped table reporttable_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,049 Update done, dropped table reporttable_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,057 Update done, dropped table chart_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,061 Update done, dropped table chart_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,065 Update done, dropped table chart_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,069 Update done, dropped table chart_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,073 Update done, dropped table mapview_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,076 Update done, dropped table mapview_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,080 Update done, dropped table mapview_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,083 Update done, dropped table mapview_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,189 Executing startup routine [12 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,191 Upgraded custom case entry form identifiers (DataEntryFormUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,193 Executing startup routine [13 of 15, runlevel 8]: ExpressionUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,214 Executing startup routine [14 of 15, runlevel 9]: ConfigurationPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,218 Executing startup routine [15 of 15, runlevel 9]: I18nLocalePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,228 All startup routines done (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.HostConfig deployWAR

INFO: Deployment of web application archive /home/hisp/tomcat8-dhis2-2/webapps/staging.war has finished in 53,298 ms

Jul 29, 2015 8:32:12 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler [“http-nio-8081”]

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 53351 ms

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.

From: Halvdan Grelland [mailto:halvdanhg@gmail.com]
Sent: 30 July 2015 02:33 PM
To: Abyot Gizaw
Cc: Elmarie Claasen; DHIS 2 Developers list; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-devs] [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

In addition; please look at the startup log of dhis2 (specifically under InitTableAlterator) and see if there’s any queries failing.

2015-07-30 12:59 GMT+02:00 Abyot Gizaw abyota@gmail.com:

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

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.

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.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

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.

Hi Halvdan,

No the analytics is still failing. Here is the log.

I don’t quite understand what is wrong. What I can see in the database is because analytics is failing the table Analytics_2015_temp remains after the analytics fails.

Regards,

Elmarie Claasen

Hisp logo

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.

ishp_s analytics(1).txt (18.8 KB)

···

From: Halvdan Grelland [mailto:halvdanhg@gmail.com]
Sent: 30 July 2015 03:32 PM
To: Elmarie Claasen
Cc: Abyot Gizaw; DHIS 2 Developers list; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-devs] [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

Hi,

Yes, the first issue seems to be fixed (and there is no indication of faults in the log as you say). Why it didn’t run properly before I don’t know.

As for the analytics: yes, analytics tables (named analytics_2014, analytics_2015 etc) er generated tables. If they do not exist, you might experience expections like the one posted. Analytics can be scheduled (recommended) to run regularly or triggered manually at https://your-dhis-server/dhis-web-reporting/displayDataMartForm.action (the process will take a lot of time to finish, depending on the server and the DB contents).

Try to run an analytics update and try again. It will probably solve the issue.

2015-07-30 15:17 GMT+02:00 Elmarie Claasen elmarie@hisp.org:

Hi Halvdan,

I don’t see anything failing in the startup routine – here is the log of the first startup after the replaced the war file. Maybe the log should give an error if the tables was not successfully updated?

Can you assist in how we fix the problem with the analytics table which still has an incorrect fieldname – “de” instead of “dx”. The issue with the Program was resolved after running the script Abyot suggested but the analytics table is a temp table created during the analytics process or something since our db does not contain that table?

015-07-29 08:31:56,705 Executing startup routine [1 of 15, runlevel 1]: InitTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,906 Executing startup routine [2 of 15, runlevel 2]: PeriodTypePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,911 Executing startup routine [3 of 15, runlevel 2]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,961 Linked default category with default concept (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:57,171 Executing startup routine [4 of 15, runlevel 3]: TableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,337 Tables updated (TableAlteror.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,337 Executing startup routine [5 of 15, runlevel 3]: TrackerIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,704 Executing startup routine [6 of 15, runlevel 3]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:01,798 Executing startup routine [7 of 15, runlevel 4]: TrackedEntityTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,640 Executing startup routine [8 of 15, runlevel 4]: IdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,816 Executing startup routine [9 of 15, runlevel 5]: TableCreator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,880 Executing startup routine [10 of 15, runlevel 7]: MapViewUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:05,973 Executing startup routine [11 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,032 Update done, dropped table reporttable_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,041 Update done, dropped table reporttable_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,045 Update done, dropped table reporttable_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,049 Update done, dropped table reporttable_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,057 Update done, dropped table chart_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,061 Update done, dropped table chart_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,065 Update done, dropped table chart_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,069 Update done, dropped table chart_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,073 Update done, dropped table mapview_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,076 Update done, dropped table mapview_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,080 Update done, dropped table mapview_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,083 Update done, dropped table mapview_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,189 Executing startup routine [12 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,191 Upgraded custom case entry form identifiers (DataEntryFormUpgrader.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,193 Executing startup routine [13 of 15, runlevel 8]: ExpressionUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,214 Executing startup routine [14 of 15, runlevel 9]: ConfigurationPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,218 Executing startup routine [15 of 15, runlevel 9]: I18nLocalePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:32:06,228 All startup routines done (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.HostConfig deployWAR

INFO: Deployment of web application archive /home/hisp/tomcat8-dhis2-2/webapps/staging.war has finished in 53,298 ms

Jul 29, 2015 8:32:12 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler [“http-nio-8081”]

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 53351 ms

Regards,

Elmarie Claasen

Hisp logo

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.

From: Halvdan Grelland [mailto:halvdanhg@gmail.com]
Sent: 30 July 2015 02:33 PM
To: Abyot Gizaw
Cc: Elmarie Claasen; DHIS 2 Developers list; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-devs] [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

In addition; please look at the startup log of dhis2 (specifically under InitTableAlterator) and see if there’s any queries failing.

2015-07-30 12:59 GMT+02:00 Abyot Gizaw abyota@gmail.com:

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

Regards,

Elmarie Claasen

Hisp logo

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.

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.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

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.

Hmm, yeah something doesn’t seem right here. Not really familiar with the detailed workings of the analytics table creation process, though (Lars would be the one to ask). What’s the schema for the left over analytics_temp_2015? Also, can you make sure to (manually) delete the temp table and re-run?

image

···

2015-07-30 16:53 GMT+02:00 Elmarie Claasen elmarie@hisp.org:

Hi Halvdan,

No the analytics is still failing. Here is the log.

I don’t quite understand what is wrong. What I can see in the database is because analytics is failing the table Analytics_2015_temp remains after the analytics fails.

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.

From: Halvdan Grelland [mailto:halvdanhg@gmail.com]
Sent: 30 July 2015 03:32 PM
To: Elmarie Claasen
Cc: Abyot Gizaw; DHIS 2 Developers list; dhis2-users@lists.launchpad.net

Subject: Re: [Dhis2-devs] [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

Hi,

Yes, the first issue seems to be fixed (and there is no indication of faults in the log as you say). Why it didn’t run properly before I don’t know.

As for the analytics: yes, analytics tables (named analytics_2014, analytics_2015 etc) er generated tables. If they do not exist, you might experience expections like the one posted. Analytics can be scheduled (recommended) to run regularly or triggered manually at https://your-dhis-server/dhis-web-reporting/displayDataMartForm.action (the process will take a lot of time to finish, depending on the server and the DB contents).

Try to run an analytics update and try again. It will probably solve the issue.

2015-07-30 15:17 GMT+02:00 Elmarie Claasen elmarie@hisp.org:

Hi Halvdan,

I don’t see anything failing in the startup routine – here is the log of the first startup after the replaced the war file. Maybe the log should give an error if the tables was not successfully updated?

Can you assist in how we fix the problem with the analytics table which still has an incorrect fieldname – “de” instead of “dx”. The issue with the Program was resolved after running the script Abyot suggested but the analytics table is a temp table created during the analytics process or something since our db does not contain that table?

015-07-29 08:31:56,705 Executing startup routine [1 of 15, runlevel 1]: InitTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • INFO 2015-07-29 08:31:56,906 Executing startup routine [2 of 15, runlevel 2]: PeriodTypePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:31:56,911 Executing startup routine [3 of 15, runlevel 2]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:31:56,961 Linked default category with default concept (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])
  • INFO 2015-07-29 08:31:57,171 Executing startup routine [4 of 15, runlevel 3]: TableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,337 Tables updated (TableAlteror.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,337 Executing startup routine [5 of 15, runlevel 3]: TrackerIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,704 Executing startup routine [6 of 15, runlevel 3]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:01,798 Executing startup routine [7 of 15, runlevel 4]: TrackedEntityTableAlteror (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,640 Executing startup routine [8 of 15, runlevel 4]: IdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,816 Executing startup routine [9 of 15, runlevel 5]: TableCreator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,880 Executing startup routine [10 of 15, runlevel 7]: MapViewUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:05,973 Executing startup routine [11 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,032 Update done, dropped table reporttable_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,041 Update done, dropped table reporttable_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,045 Update done, dropped table reporttable_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,049 Update done, dropped table reporttable_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,057 Update done, dropped table chart_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,061 Update done, dropped table chart_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,065 Update done, dropped table chart_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,069 Update done, dropped table chart_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,073 Update done, dropped table mapview_indicators (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,076 Update done, dropped table mapview_dataelements (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,080 Update done, dropped table mapview_dataelementoperands (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,083 Update done, dropped table mapview_datasets (FavoriteDataItemUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,189 Executing startup routine [12 of 15, runlevel 7]: FavoriteDataItemUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,191 Upgraded custom case entry form identifiers (DataEntryFormUpgrader.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,193 Executing startup routine [13 of 15, runlevel 8]: ExpressionUpgrader (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,214 Executing startup routine [14 of 15, runlevel 9]: ConfigurationPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,218 Executing startup routine [15 of 15, runlevel 9]: I18nLocalePopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • INFO 2015-07-29 08:32:06,228 All startup routines done (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.HostConfig deployWAR

INFO: Deployment of web application archive /home/hisp/tomcat8-dhis2-2/webapps/staging.war has finished in 53,298 ms

Jul 29, 2015 8:32:12 AM org.apache.coyote.AbstractProtocol start

INFO: Starting ProtocolHandler [“http-nio-8081”]

Jul 29, 2015 8:32:12 AM org.apache.catalina.startup.Catalina start

INFO: Server startup in 53351 ms

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.

From: Halvdan Grelland [mailto:halvdanhg@gmail.com]
Sent: 30 July 2015 02:33 PM
To: Abyot Gizaw
Cc: Elmarie Claasen; DHIS 2 Developers list; dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-devs] [Dhis2-users] FW: Problem with Tracker program after updating to 2.20 stable

In addition; please look at the startup log of dhis2 (specifically under InitTableAlterator) and see if there’s any queries failing.

2015-07-30 12:59 GMT+02:00 Abyot Gizaw abyota@gmail.com:

On Thu, Jul 30, 2015 at 11:30 AM Elmarie Claasen elmarie@hisp.org wrote:

Hi Devs,

I have an urgent database issue which I have to resolve as this project is implementing by Monday and my database is not running on 2.20 stable which I need for the tracker capture app to load. Can someone please assist.

We have a database called ISHP which Erling has been helping us to set up the Tracker capture app for implementation.

Since the app could only connect to 2.20 we upgraded our training database some time ago to 2.20 snapshot build revision 19527 and also kept the program changes we made updated in 2.19 live version since we couldn’t risk updating a live database when we did not know what the implications would be.

We now wanting to update the 2.19 Live database to 2.20 which we did on our development instance but get the following errors which does not allow us to

  1.  access the program in the UI or via the tracker capture app (see open program error log) The problem seems to be that the programtype in our database is Integer while in other 2.20 instances it is char varying. The update script from 2.19>2.20 does not contain anything changing this so how do I deal with this please…
    

This was supposed to be handled internally in the code.

try to alter manually and see what happens

ALTER TABLE program ALTER COLUMN “type” TYPE varchar(255);

  1.  analytics is failing due to fieldname error   (see detailed analytics error log attached but here is a short version) The problem is that the temp table has a fieldname called de instead of dx – again something I don’t know how it happens or how to fix
    

Caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [update analytics_temp_2015 set “uidlevel1” = null,“uidlevel2” = null,“uidlevel3” = null,“uidlevel4” = null,“uidlevel5” = null where level > 5 and de in (‘jx6lCxe8gYy’, ‘cjA6JH0kC9B’)]; nested exception is org.postgresql.util.PSQLException: ERROR: column “de” does not exist

We checked our other 2.20 databases and the column name is dx but we don’t know how to fix this – please help!

The program we are accessing on 2.19, 2.20 stable and 2.20 snapshot Version: Build revision: 19527 Build date: 2015-07-01 08:47 is all set up exactly the same way and I don’t see why one would be able to open the program, open tracker capture in the UI and log in on tracker capture app only on the 2.20 snapshot version and not on 2.20 stable. Can you please assist us with what is wrong?

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.

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.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp


Thank you,

Abyot


Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

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.