← Back to team overview

dhis2-devs team mailing list archive

Re: Meta Data Import Problem When upgrading from Version 2.13 to 2.20

 

Hi there.

This does not seem to be related to the issue which you reported above.  Is
the startup hanging at a certain stage now?

This can be notoriously difficult to diagnose. Can you turn on the
postgresql logs and see at which stage the startup fails by looking for
database errors in the logs when the system is starting up?

Also, if you are moving from 2.13, did you execute the upgrade script?

https://github.com/dhis2/dhis2-utils/blob/master/resources/sql/convert-fixed-attributes-to-dynamic-postgres.sql

Regards,
Jason





On Fri, Aug 21, 2015 at 9:14 AM, Mihayo Mathayo <princehayo@xxxxxxxxx>
wrote:

> logs attached
>
> On Fri, Aug 21, 2015 at 9:36 AM, Mihayo Mathayo <princehayo@xxxxxxxxx>
> wrote:
>
>> Yes, am importing with the default admin/district account and i presume
>> it has all privileges.Visited the database i cant see the org units in the
>> tables but the interface shows all org units have been imported.
>>
>> On Fri, Aug 21, 2015 at 9:12 AM, Jason Pickering <
>> jason.p.pickering@xxxxxxxxx> wrote:
>>
>>> Hi there.
>>>
>>> It looks like you user may be restricted. Are you importing this with a
>>> superuser account?
>>>
>>> Can you check the database (in the organisationunit table) and see if
>>> any of the imported data is there?
>>>
>>>
>>> Regards,
>>> Jason
>>>
>>>
>>> On Fri, Aug 21, 2015 at 7:25 AM, Mihayo Mathayo <princehayo@xxxxxxxxx>
>>> wrote:
>>>
>>>> Hello Jason,
>>>> I have done as you said,the org units were all imported but users'
>>>> permission is denied and i can  not see the imported org units on the
>>>> organisation unit link menu even after running analytics.
>>>> See the attached screenshots.
>>>>
>>>> Regards
>>>>
>>>> On Fri, Aug 21, 2015 at 7:17 AM, Jason Pickering <
>>>> jason.p.pickering@xxxxxxxxx> wrote:
>>>>
>>>>> Hi there.
>>>>>
>>>>> Have you tried to upgrade the 2.13 instance database first to
>>>>> 2.20,following all of the necessary documented upgrade steps, and then
>>>>> perform the export?
>>>>>
>>>>> There have been numerous model changes since then which will likely
>>>>> affect the import.
>>>>> Regards,
>>>>> Jason
>>>>>
>>>>>
>>>>> On Fri, Aug 21, 2015, 05:58 Mihayo Mathayo <princehayo@xxxxxxxxx>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>> I checked the xml file every org unit has opening date ..but to my
>>>>> surprise during importation they are ignored. Am thinking of trying other
>>>>> versions like 2.18 or 2.15 but I cant find the download links..
>>>>>
>>>>> On Aug 21, 2015 1:23 AM, "Juan Manuel Alcantara Acosta" <
>>>>> jmalcantara1@xxxxxxxxx> wrote:
>>>>>
>>>>> Hi Mihayo
>>>>>
>>>>> A copy of the log would be useful to help you but based on the list of
>>>>> conflicts shown in the image you included, the ignored org units are
>>>>> missing the opening date, check your XML and add a valid date where it's
>>>>> missing, here's an example:
>>>>>
>>>>> <organisationUnit xmlns="http://dhis2.org/schema/dxf/2.0
>>>>> " code="OU_222702" uuid="b1c9eff6-92e0-465b-8e33-71012171eeb2" lastUpdated="2014-11-25T08:37:53.469+0000"href="
>>>>> https://apps.dhis2.org/dev/api/organisationUnits/ueuQlqb8ccl"; id="ueuQlqb8ccl" level="4" created="2012-02-17T14:54:39.987+0000" name=" Panderu
>>>>> MCHP" shortName=" Panderu MCHP">
>>>>>
>>>>> <displayName>Panderu MCHP</displayName>
>>>>>
>>>>> <displayShortName>Panderu MCHP</displayShortName>
>>>>>
>>>>> <externalAccess>false</externalAccess>
>>>>>
>>>>> <path>/ImspTQPwCqd/kJq2mPyFEHo/KIUCimTXf8Q/ueuQlqb8ccl</path>
>>>>>
>>>>> *<openingDate>1993-12-31T23:00:00.000+0000</openingDate>*
>>>>>
>>>>>
>>>>> <parent id="KIUCimTXf8Q" name="Nongowa" code="OU_222690" created="2012-02-17T14:54:39.987+0000" lastUpdated="2014-11-25T08:37:53.296+0000"href="
>>>>> https://apps.dhis2.org/dev/api/organisationUnits/KIUCimTXf8Q"/>
>>>>>
>>>>> </organisationUnit>
>>>>>
>>>>>
>>>>> JM
>>>>>
>>>>> El 20/08/2015, a las 16:23, Mihayo Mathayo <princehayo@xxxxxxxxx>
>>>>> escribió:
>>>>>
>>>>> Hello Team,
>>>>>
>>>>>  Am having a problem with upgrade of dhis2 instance from version 2.13
>>>>> to 2.20.The issue am facing is on importing meta data where top level,level
>>>>> two and level three  OrganizationUnits are ignored but the lowest level
>>>>> organizations units are imported into version 2.20.
>>>>>
>>>>> Attached screenshots gives a summary of the problem.
>>>>>
>>>>> Any help will be highly appreciated.
>>>>>
>>>>> Best Regards.
>>>>>
>>>>>
>>>>> <DHIS_import.PNG><DHIS2_Conflict.PNG>_______________________________________________
>>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list: https://launchpad.net/~dhis2-devs
>>>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Jason P. Pickering
>>> email: jason.p.pickering@xxxxxxxxx
>>> tel:+46764147049
>>>
>>
>>
>


-- 
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+46764147049

References