dhis2-devs team mailing list archive

[Rishi <rsukul@xxxxxxxxxxxxxxxxx>]

Hi Morton,

Hereby the error log. I did it this time with versión 2.20, problem
seems to manifest itself the same in the User Interface.  I include the
stdout log file this contains in the end some ERRORS and Warnings
related to the import.

Some background (ignore when short of time) "Why import into a empty database?"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When testing import metadata into 2.19 i wanted to know if all kind of metadata can be imported, so stopped tomcat, dropped the database , created an new empty one, started tomcat and imported our metadata. (Did also tried it with an metadata export from the  sierra leone demo server).  This went fine with 2.18 but not with 2.19 and 2.20. (all as admin). 


** Attachment added: "STDout  2.20"
   https://bugs.launchpad.net/dhis2/+bug/1474419/+attachment/4433489/+files/tomcat7-stderr.2015-07-24.log

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1474419

Title:
  metadata import into empty db in 2.19 dhis2 fails

Status in DHIS:
  New

Bug description:
  Dhis2 version: 2.19
  tested: local and with the demo Sierra Leone server.
  OS: Local Windows 7, tomcat(-7.0.62) , postgres 9.4
  browser: Firefox and Chrome.

  Problem statement
  Dhis2 version 2.19 fails  to imports metadate into empty database. Goes fine with 2.18 version.

  How tested
   Test 1. Do a default meta data export in msf dhis2 data on dhis2 version 2.19. 
  Stop tomcat, drop database , create a new empty database.
  1.	Start tomcat, start metadata import as admin user.
  2.	Check import summary, see Detailed error description below.

  Detailed error description
  Import never finishes it gets ‘stuck’  during importing  of Data sets. 
   
  In tomcat cat log the following is found.
  SEVERE: Servlet.service() for servlet [webapi] in context with path [/dhis] threw exception
  org.springframework.dao.DataIntegrityViolationException: could not execute statement; SQL [n/a]; constraint [null]; nested exception is org.hibernate.exception.ConstraintViolationException: could not execute statement
  	at … (a lot of java class exceptions calls that are not helpful)
  	
  Test 2, same but then with an meta data export into  the Sierra Leone demo server. With same result ( as described in the detailed err description).
  Test 3. Same but then with 2.18 version of dhis2 installed local and with a dhis2 import with Sierra leone demo data and our data,  both goes fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1474419/+subscriptions