dhis2-users team mailing list archive

[Saptarshi Purkayastha <sunbiz@xxxxxxxxx>]

Hi Hannan,

What you pasted in the email seems like a base64 string of an image. Unless
gmail screwed something from the email that you sent, I request that you
send logs or long text as attachments, instead of inline email message.

Sequences in postgreSQL are similar to auto-increment ids in MySQL. Their
values are generated during the insert statements and will depend on the
initial value of the sequence. You can manually set the sequence
value<http://www.postgresql.org/docs/9.1/static/functions-sequence.html>(i.e.
setval) before you start importing, to ensure that the values start
from 1. Either ways, the metadata xml does not have the internal Ids (i.e.
the organisationunitid and similar). Those ids are generated and if other
organisationunits exist in the system into which you are importing, then
you would not like to overwrite these internal ids.

If you are starting with a blank database, why not let DHIS2 2.11 create
the blank database schema. Then on empty tables set the sequences to 1 and
run the metadata import after that to ensure that they started from 1.

---
Regards,
Saptarshi PURKAYASTHA

My Tech Blog:  http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE


On 14 May 2013 08:15, Hannan Khan <hannank@xxxxxxxxx> wrote:

>  Dear Experts
>
> I writ you guys earlier that we are facing problem running DHIS2 version
> 2.11 with MySQL. So we are trying to migrate to PostgreSQL. With 26000
> orgunits  and 35 million data value it is really difficult for us to do
> that. When I am trying to export metadata from MySQL based dhis2 to
> PostgreSQL based dhis2 (both are version 2.11) I found the following
> problem:
>
> The orgunit table in mysql have following
>
>
> But the postgresql have the following
>
> Please see carefully the organisationunitid of 'Bangladesh' become 46
> after import metadata into postgresql  where as the original source in
> mysql was 1.
>
> Similarly in mysql dataelement table was
>
> it become following in postgres
>
> dataelement 1 become 26424. Similarly in dataelementcategory table 1
> become 13, 2 become 26387. And most dangerous is in
> dataelementcategoryoption where the values are
>
>   Also the period table is same.
>
>
> Why this is happening? Can you please explain.
>
> Regards
>
> Hannan
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>