dhis2-devs team mailing list archive

[Calle Hedberg <calle.hedberg@xxxxxxxxx>]

Hi

The way to do this is NOT to export meta-data from one version and import
it into another version - as a general rule that is not supported. It works
in the majority of cases where there's been no changes to the api or the
data model, but it will not work for cases where there's been significant
changes. (off hand, I seem to recall the upgrade from 2.22 to 2.23 was
significant...)

The "safe" way is to
- create a new (local) database instance and copy your 2.22 source database
into that.
- run the upgrade script to 2.23 on the new 2.22 copy, and follow any other
instructions.
- start up the newly upgraded instance, check for integrity violations etc
and make sure everything is running as expected.
- export from the new upgraded instance to your destination 2.23 instance.

Regards
calle


On 29 June 2018 at 15:00, Nuria Masclans <necessitouncompte@xxxxxxxxx>
wrote:

> Good morning,
>
> I have been trying to import dhis 2.22 metadada from one server to another
> server that uses dhis 2.23  using import/export app. By selecting
> individually the different metadata types, some of them are imported to
> 2.23 just fine, while some others are imported or upgrades giving conflicts.
>
> Why does these conflicts appear and what do they mean? How can we solve
> them?
>
> Thank you in advance,
> Núria M.
>
> _______________________________________________
> 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
>
>


-- 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA

Tel/fax (home): +27-21-685-6472

Cell: +27-82-853-5352

Iridium SatPhone: +8816-315-19119

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************