← Back to team overview

dhis2-devs team mailing list archive

Re: Problems populating Orgunits directly

 

Hi Knut,
You should start with a vacuum/analyze if you are using postgresq as as start.

Can you give a dump of the DB, assuming it is not huge. Just the
orgunit tables will do. I can try and take a look at it .

Best regards,
Jason



On Sun, Sep 20, 2009 at 4:30 PM, Knut Staring <knutst@xxxxxxxxx> wrote:
> On Fri, Sep 18, 2009 at 6:31 PM, Knut Staring <knutst@xxxxxxxxx> wrote:
>>
>> Hello,
>> I am trying to populate the database directly with an enormous orgunit
>> tree of the whole world (173 000 orgunits...). I have imported data to the
>> following 3 tables:
>> source, organisationunit, and orgunithierarchystructure. Do I need to
>> populate any other tables?
>> Also, in the organisationunit table, I had to remove the uniqueness
>> constraints for both name and shortname, as there were tens of thousands of
>> duplicate names - could this be the source of the below problems? I can of
>> course try and generate unique names in some way.
>> When starting DHIS, I get these messages:
>
> The difficulty stemmed from forgetting how to start the hierarchy: With NULL
> as parentid for the top level. The only problem now is that it's a bit slow
> - perhaps we can add some indexing? Jason?
> Uniqueness is not needed, and neither is the orgunithierarchystructure table
> - what is this for?
>
> http://www.openhealthconsortium.org/wiki/doku.php?id=administrative_boundaries
>
>
> _______________________________________________
> 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
>
>



Follow ups

References