Upgrade 2.20 to 2.21 issue encountered

Hi,

I have a VM running Ubuntu 15.10, Java OpenJDK (Latest version), Tomcat 8, PostgreSQL 9.4.

The DHIS instance is running version 2.20.

Via PGAdmin the number of Views on the db is confirmed to be 0.

When upgrading to version 2.21 (by replacing the 2.20 WAR file with the 2.21 version), I experienced the following:

I replaced the WAR file and started Tomcat - and a blank screen instead of the login screen resulted.

I then also restarted the VM with the same end-result. (If I revert back to the 2.20 WAR file, everything works fine).

I then created a blank test-db and started the tomcat instance - the standard login screen is displayed as per normal, indicating to me that the challenge lies with the actual db upgrade process.

Comparing the Catalina log file from the problematic process to the test-db log, the following point of failure was picked up:

TEST db catalina.out shows the adding of a default category:

  • INFO 2015-11-06 11:36:59,993 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

* INFO 2015-11-06 11:37:01,406 Added default category (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-11-06 11:37:01,505 Executing startup routine [4 of 13, runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

The actual db catalina.out shows the following:

  • INFO 2015-11-06 12:10:07,281 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

  • ERROR 2015-11-06 12:10:08,106 java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum class [org.hisp.dhis.common.ValueType]

at org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)

at

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/dhis2-1] startup failed due to previous errors

It thus seems that the "Added default category (DataElementDefaultDimensionPopulator.java" step is failing when upgrading this specific 2.20 database .

Any proposals/advise on how to solve this matter?

Much appreciated!

Kind regards

image

···

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

Hi Ferdie,

I guess the problem is that you have some SQL views which refer to the dataelement table. We are changing the length of the dataelement.valuetype column in 2.21. For that to work you need to drop all SQL views prior to the first time you start on 2.21. This information can be found in the upgrade notes:

https://www.dhis2.org/221-upgrade

Lars

Notes

- If you have SQL views associated with the “dataelement” and “trackedentityattribute” tables, it is recommended to remove those views before starting 2.21 for the first time. This to allow the upgrade routines to change column types. You can drop all SQL views from data administration > maintenance > Drop SQL views. You can later recreate with Create SQL views.

image

···

On Fri, Nov 6, 2015 at 11:22 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi,

I have a VM running Ubuntu 15.10, Java OpenJDK (Latest version), Tomcat 8, PostgreSQL 9.4.

The DHIS instance is running version 2.20.

Via PGAdmin the number of Views on the db is confirmed to be 0.

When upgrading to version 2.21 (by replacing the 2.20 WAR file with the 2.21 version), I experienced the following:

I replaced the WAR file and started Tomcat - and a blank screen instead of the login screen resulted.

I then also restarted the VM with the same end-result. (If I revert back to the 2.20 WAR file, everything works fine).

I then created a blank test-db and started the tomcat instance - the standard login screen is displayed as per normal, indicating to me that the challenge lies with the actual db upgrade process.

Comparing the Catalina log file from the problematic process to the test-db log, the following point of failure was picked up:

TEST db catalina.out shows the adding of a default category:

  • INFO 2015-11-06 11:36:59,993 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

* INFO 2015-11-06 11:37:01,406 Added default category (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-11-06 11:37:01,505 Executing startup routine [4 of 13, runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

The actual db catalina.out shows the following:

  • INFO 2015-11-06 12:10:07,281 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • ERROR 2015-11-06 12:10:08,106 java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum class [org.hisp.dhis.common.ValueType]

at org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)

at

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/dhis2-1] startup failed due to previous errors

It thus seems that the "Added default category (DataElementDefaultDimensionPopulator.java" step is failing when upgrading this specific 2.20 database .

Any proposals/advise on how to solve this matter?

Much appreciated!

Kind regards


Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Hi Lars, all views were dropped prior to the upgrade using the maintenance functionality. PgAdmin also indicated “Views (0)” in the database.
Should I delete the SQL views altogether instead of just “Drop SQL views” from the Maintenance User-Screen?

Any other potential reasons I can investigate?

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.

image

···

On Fri, Nov 6, 2015 at 1:30 PM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Ferdie,

I guess the problem is that you have some SQL views which refer to the dataelement table. We are changing the length of the dataelement.valuetype column in 2.21. For that to work you need to drop all SQL views prior to the first time you start on 2.21. This information can be found in the upgrade notes:

https://www.dhis2.org/221-upgrade

Lars

Notes

- If you have SQL views associated with the “dataelement” and “trackedentityattribute” tables, it is recommended to remove those views before starting 2.21 for the first time. This to allow the upgrade routines to change column types. You can drop all SQL views from data administration > maintenance > Drop SQL views. You can later recreate with Create SQL views.

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

On Fri, Nov 6, 2015 at 11:22 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi,

I have a VM running Ubuntu 15.10, Java OpenJDK (Latest version), Tomcat 8, PostgreSQL 9.4.

The DHIS instance is running version 2.20.

Via PGAdmin the number of Views on the db is confirmed to be 0.

When upgrading to version 2.21 (by replacing the 2.20 WAR file with the 2.21 version), I experienced the following:

I replaced the WAR file and started Tomcat - and a blank screen instead of the login screen resulted.

I then also restarted the VM with the same end-result. (If I revert back to the 2.20 WAR file, everything works fine).

I then created a blank test-db and started the tomcat instance - the standard login screen is displayed as per normal, indicating to me that the challenge lies with the actual db upgrade process.

Comparing the Catalina log file from the problematic process to the test-db log, the following point of failure was picked up:

TEST db catalina.out shows the adding of a default category:

  • INFO 2015-11-06 11:36:59,993 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

* INFO 2015-11-06 11:37:01,406 Added default category (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-11-06 11:37:01,505 Executing startup routine [4 of 13, runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

The actual db catalina.out shows the following:

  • INFO 2015-11-06 12:10:07,281 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • ERROR 2015-11-06 12:10:08,106 java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum class [org.hisp.dhis.common.ValueType]

at org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)

at

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/dhis2-1] startup failed due to previous errors

It thus seems that the "Added default category (DataElementDefaultDimensionPopulator.java" step is failing when upgrading this specific 2.20 database .

Any proposals/advise on how to solve this matter?

Much appreciated!

Kind regards


Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Hi Ferdie,

okay. Are you getting the same error this time or another one? Do you think you could post the output to the Tomcat log from when you started last time?

Lars

image

···

On Fri, Nov 13, 2015 at 9:25 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi Lars, all views were dropped prior to the upgrade using the maintenance functionality. PgAdmin also indicated “Views (0)” in the database.
Should I delete the SQL views altogether instead of just “Drop SQL views” from the Maintenance User-Screen?

Any other potential reasons I can investigate?

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.

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

On Fri, Nov 6, 2015 at 1:30 PM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Ferdie,

I guess the problem is that you have some SQL views which refer to the dataelement table. We are changing the length of the dataelement.valuetype column in 2.21. For that to work you need to drop all SQL views prior to the first time you start on 2.21. This information can be found in the upgrade notes:

https://www.dhis2.org/221-upgrade

Lars

Notes

- If you have SQL views associated with the “dataelement” and “trackedentityattribute” tables, it is recommended to remove those views before starting 2.21 for the first time. This to allow the upgrade routines to change column types. You can drop all SQL views from data administration > maintenance > Drop SQL views. You can later recreate with Create SQL views.

On Fri, Nov 6, 2015 at 11:22 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi,

I have a VM running Ubuntu 15.10, Java OpenJDK (Latest version), Tomcat 8, PostgreSQL 9.4.

The DHIS instance is running version 2.20.

Via PGAdmin the number of Views on the db is confirmed to be 0.

When upgrading to version 2.21 (by replacing the 2.20 WAR file with the 2.21 version), I experienced the following:

I replaced the WAR file and started Tomcat - and a blank screen instead of the login screen resulted.

I then also restarted the VM with the same end-result. (If I revert back to the 2.20 WAR file, everything works fine).

I then created a blank test-db and started the tomcat instance - the standard login screen is displayed as per normal, indicating to me that the challenge lies with the actual db upgrade process.

Comparing the Catalina log file from the problematic process to the test-db log, the following point of failure was picked up:

TEST db catalina.out shows the adding of a default category:

  • INFO 2015-11-06 11:36:59,993 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

* INFO 2015-11-06 11:37:01,406 Added default category (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-11-06 11:37:01,505 Executing startup routine [4 of 13, runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

The actual db catalina.out shows the following:

  • INFO 2015-11-06 12:10:07,281 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • ERROR 2015-11-06 12:10:08,106 java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum class [org.hisp.dhis.common.ValueType]

at org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)

at

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/dhis2-1] startup failed due to previous errors

It thus seems that the "Added default category (DataElementDefaultDimensionPopulator.java" step is failing when upgrading this specific 2.20 database .

Any proposals/advise on how to solve this matter?

Much appreciated!

Kind regards


Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Attached the catalina log.

Till now - I have a 2.20 db running perfectly.

  • I then used the Data Administration/Maintenance option and selected “Drop SQL Views”.

  • After the maintenance was performed, I verified in PgAdmin that no views exist in the db.

  • I now replaced the 2.20 WAR with a 2.21 WAR

  • I started Tomcat using the startup.sh script.

Attached is the catalina.out log file created by the process (I deleted the log before I started the 2.21 process).

(Note - 2.21 using a blank db works fine…)

Please advise.

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.

catalina.out.221-err (15.7 KB)

···

On Fri, Nov 13, 2015 at 11:55 AM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Ferdie,

okay. Are you getting the same error this time or another one? Do you think you could post the output to the Tomcat log from when you started last time?

Lars

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

On Fri, Nov 13, 2015 at 9:25 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi Lars, all views were dropped prior to the upgrade using the maintenance functionality. PgAdmin also indicated “Views (0)” in the database.
Should I delete the SQL views altogether instead of just “Drop SQL views” from the Maintenance User-Screen?

Any other potential reasons I can investigate?

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.


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

On Fri, Nov 6, 2015 at 1:30 PM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Ferdie,

I guess the problem is that you have some SQL views which refer to the dataelement table. We are changing the length of the dataelement.valuetype column in 2.21. For that to work you need to drop all SQL views prior to the first time you start on 2.21. This information can be found in the upgrade notes:

https://www.dhis2.org/221-upgrade

Lars

Notes

- If you have SQL views associated with the “dataelement” and “trackedentityattribute” tables, it is recommended to remove those views before starting 2.21 for the first time. This to allow the upgrade routines to change column types. You can drop all SQL views from data administration > maintenance > Drop SQL views. You can later recreate with Create SQL views.

On Fri, Nov 6, 2015 at 11:22 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi,

I have a VM running Ubuntu 15.10, Java OpenJDK (Latest version), Tomcat 8, PostgreSQL 9.4.

The DHIS instance is running version 2.20.

Via PGAdmin the number of Views on the db is confirmed to be 0.

When upgrading to version 2.21 (by replacing the 2.20 WAR file with the 2.21 version), I experienced the following:

I replaced the WAR file and started Tomcat - and a blank screen instead of the login screen resulted.

I then also restarted the VM with the same end-result. (If I revert back to the 2.20 WAR file, everything works fine).

I then created a blank test-db and started the tomcat instance - the standard login screen is displayed as per normal, indicating to me that the challenge lies with the actual db upgrade process.

Comparing the Catalina log file from the problematic process to the test-db log, the following point of failure was picked up:

TEST db catalina.out shows the adding of a default category:

  • INFO 2015-11-06 11:36:59,993 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

* INFO 2015-11-06 11:37:01,406 Added default category (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-11-06 11:37:01,505 Executing startup routine [4 of 13, runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

The actual db catalina.out shows the following:

  • INFO 2015-11-06 12:10:07,281 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • ERROR 2015-11-06 12:10:08,106 java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum class [org.hisp.dhis.common.ValueType]

at org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)

at

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/dhis2-1] startup failed due to previous errors

It thus seems that the "Added default category (DataElementDefaultDimensionPopulator.java" step is failing when upgrading this specific 2.20 database .

Any proposals/advise on how to solve this matter?

Much appreciated!

Kind regards


Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Okay thanks Ferdie. I suspect the problem a missing value in the valuetype column.

Try running this SQL and see what effect it has:

update dataelement set valuetype=‘UNIT_INTERVAL’ where numbertype=‘unitInterval’;

I will change the upgrade statements inside dhis accordingly if this has any effect.

regards,

Lars

image

···

On Mon, Nov 16, 2015 at 9:48 AM, Ferdie Botha ferdie@hisp.org wrote:

Attached the catalina log.

Till now - I have a 2.20 db running perfectly.

  • I then used the Data Administration/Maintenance option and selected “Drop SQL Views”.
  • After the maintenance was performed, I verified in PgAdmin that no views exist in the db.
  • I now replaced the 2.20 WAR with a 2.21 WAR
  • I started Tomcat using the startup.sh script.

Attached is the catalina.out log file created by the process (I deleted the log before I started the 2.21 process).

(Note - 2.21 using a blank db works fine…)

Please advise.

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.

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

On Fri, Nov 13, 2015 at 11:55 AM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Ferdie,

okay. Are you getting the same error this time or another one? Do you think you could post the output to the Tomcat log from when you started last time?

Lars

On Fri, Nov 13, 2015 at 9:25 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi Lars, all views were dropped prior to the upgrade using the maintenance functionality. PgAdmin also indicated “Views (0)” in the database.
Should I delete the SQL views altogether instead of just “Drop SQL views” from the Maintenance User-Screen?

Any other potential reasons I can investigate?

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.


Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

On Fri, Nov 6, 2015 at 1:30 PM, Lars Helge Øverland larshelge@gmail.com wrote:

Hi Ferdie,

I guess the problem is that you have some SQL views which refer to the dataelement table. We are changing the length of the dataelement.valuetype column in 2.21. For that to work you need to drop all SQL views prior to the first time you start on 2.21. This information can be found in the upgrade notes:

https://www.dhis2.org/221-upgrade

Lars

Notes

- If you have SQL views associated with the “dataelement” and “trackedentityattribute” tables, it is recommended to remove those views before starting 2.21 for the first time. This to allow the upgrade routines to change column types. You can drop all SQL views from data administration > maintenance > Drop SQL views. You can later recreate with Create SQL views.

On Fri, Nov 6, 2015 at 11:22 AM, Ferdie Botha ferdie@hisp.org wrote:

Hi,

I have a VM running Ubuntu 15.10, Java OpenJDK (Latest version), Tomcat 8, PostgreSQL 9.4.

The DHIS instance is running version 2.20.

Via PGAdmin the number of Views on the db is confirmed to be 0.

When upgrading to version 2.21 (by replacing the 2.20 WAR file with the 2.21 version), I experienced the following:

I replaced the WAR file and started Tomcat - and a blank screen instead of the login screen resulted.

I then also restarted the VM with the same end-result. (If I revert back to the 2.20 WAR file, everything works fine).

I then created a blank test-db and started the tomcat instance - the standard login screen is displayed as per normal, indicating to me that the challenge lies with the actual db upgrade process.

Comparing the Catalina log file from the problematic process to the test-db log, the following point of failure was picked up:

TEST db catalina.out shows the adding of a default category:

  • INFO 2015-11-06 11:36:59,993 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

* INFO 2015-11-06 11:37:01,406 Added default category (DataElementDefaultDimensionPopulator.java [localhost-startStop-1])

  • INFO 2015-11-06 11:37:01,505 Executing startup routine [4 of 13, runlevel 4]: ReportingIdentityPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])

The actual db catalina.out shows the following:

  • INFO 2015-11-06 12:10:07,281 Executing startup routine [3 of 13, runlevel 3]: DataElementDefaultDimensionPopulator (DefaultStartupRoutineExecutor.java [localhost-startStop-1])
  • ERROR 2015-11-06 12:10:08,106 java.lang.IllegalArgumentException: Unknown name value [unitInterval] for enum class [org.hisp.dhis.common.ValueType]

at org.hibernate.type.EnumType$NamedEnumValueMapper.fromName(EnumType.java:467)

at

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file

Nov 06, 2015 12:10:08 PM org.apache.catalina.core.StandardContext startInternal

SEVERE: Context [/dhis2-1] startup failed due to previous errors

It thus seems that the "Added default category (DataElementDefaultDimensionPopulator.java" step is failing when upgrading this specific 2.20 database .

Any proposals/advise on how to solve this matter?

Much appreciated!

Kind regards


Ferdie Botha

Health Information Systems Program


**e-mail: **ferdie@hisp.org
**Mobile: **082 453 5744

Skype: ferdie.botha.skype

**Web: ** http://www.hisp.org

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

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org

Lars Helge Øverland

Lead developer, DHIS 2

University of Oslo

Skype: larshelgeoverland

http://www.dhis2.org