[GeoNetwork-devel] [upgrade database from 1 month-old trunk to current trunk]

Craig_Jones1 · April 3, 2012, 1:32am

Hi All,

I've been using an open source tool called liquibase
(http://www.liquibase.org/) to put together migration scripts from our
BlueNetMEST instance to the latest GeoNetwork snapshot.

Thought I'd mention it because it resolves problems like the one Jean is
having at the moment. Required database changes and update steps are
automatically applied as required when liquibase is run (we run it every
time the web app starts up).

Something to look at in future perhaps.

Regards,
--
Craig Jones
eMII Infrastructure Programmer
IMOS e-Marine Information Infrastructure Facility (eMII)
Ph: +61 3 6226 8567

-------- Forwarded Message --------
From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] upgrade database from 1 month-old trunk to
current trunk
Date: Mon, 02 Apr 2012 19:31:22 +0200

Hi,

I've got a running geonetwork from the trunk code, 1 month ago. Since
then, there have been quite a few changes, some in the database.
I understand we've got the migrate sql codes, that would allow, I
believe, to upgrade a database from gn 2.6.4 to trunk (2.7.0)
But trying to apply it on my postgresql database, I get many errors,
since most of the structure and data is yet here, but not all...
Do you know an "easy" way to do such an upgrade ?

Note : the DB is yet configured, with many metadatas inside, so I would
prefer not the make it from scratch and reimport the data. If possible..

Thanks,

Jean
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

ticheler · April 3, 2012, 7:53am

Hi Craig,
It sounds like a great tool that could improve the software. Do you have suggestions on how to integrate it? Or is it something you have more or less ready to go in to the latest trunk? Should we add it to older versions also (or better: how much work is it to start using this)?
Thanks,
Jeroen

On 3 apr. 2012, at 03:32, Craig Jones wrote:

Hi All,

I've been using an open source tool called liquibase
(http://www.liquibase.org/) to put together migration scripts from our
BlueNetMEST instance to the latest GeoNetwork snapshot.

Thought I'd mention it because it resolves problems like the one Jean is
having at the moment. Required database changes and update steps are
automatically applied as required when liquibase is run (we run it every
time the web app starts up).

Something to look at in future perhaps.

Regards,
--
Craig Jones
eMII Infrastructure Programmer
IMOS e-Marine Information Infrastructure Facility (eMII)
Ph: +61 3 6226 8567

-------- Forwarded Message --------
From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] upgrade database from 1 month-old trunk to
current trunk
Date: Mon, 02 Apr 2012 19:31:22 +0200

Hi,

I've got a running geonetwork from the trunk code, 1 month ago. Since
then, there have been quite a few changes, some in the database.
I understand we've got the migrate sql codes, that would allow, I
believe, to upgrade a database from gn 2.6.4 to trunk (2.7.0)
But trying to apply it on my postgresql database, I get many errors,
since most of the structure and data is yet here, but not all...
Do you know an "easy" way to do such an upgrade ?

Note : the DB is yet configured, with many metadatas inside, so I would
prefer not the make it from scratch and reimport the data. If possible..

Thanks,

Jean
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Jean_Pommier · April 3, 2012, 2:06pm

Hi !
Yes indeed, it would be great !

And right now, any idea how I could do it ?
Thanks

Jean

2012/4/3 Jeroen Ticheler <jeroen.ticheler@anonymised.com>

Hi Craig,
It sounds like a great tool that could improve the software. Do you have suggestions on how to integrate it? Or is it something you have more or less ready to go in to the latest trunk? Should we add it to older versions also (or better: how much work is it to start using this)?
Thanks,
Jeroen

On 3 apr. 2012, at 03:32, Craig Jones wrote:

Hi All,

I’ve been using an open source tool called liquibase
(http://www.liquibase.org/) to put together migration scripts from our
BlueNetMEST instance to the latest GeoNetwork snapshot.

Thought I’d mention it because it resolves problems like the one Jean is
having at the moment. Required database changes and update steps are
automatically applied as required when liquibase is run (we run it every
time the web app starts up).

Something to look at in future perhaps.

Regards,

Craig Jones
eMII Infrastructure Programmer
IMOS e-Marine Information Infrastructure Facility (eMII)
Ph: +61 3 6226 8567

-------- Forwarded Message --------
From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] upgrade database from 1 month-old trunk to
current trunk
Date: Mon, 02 Apr 2012 19:31:22 +0200

Hi,

I’ve got a running geonetwork from the trunk code, 1 month ago. Since
then, there have been quite a few changes, some in the database.
I understand we’ve got the migrate sql codes, that would allow, I
believe, to upgrade a database from gn 2.6.4 to trunk (2.7.0)
But trying to apply it on my postgresql database, I get many errors,
since most of the structure and data is yet here, but not all…
Do you know an “easy” way to do such an upgrade ?

Note : the DB is yet configured, with many metadatas inside, so I would
prefer not the make it from scratch and reimport the data. If possible…

Thanks,

Jean

This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Craig_Jones1 · April 4, 2012, 12:37am

Hi Jeroen,

I'll get back to you re what's involved and how much work it would be to
include it for future changes - making it work for previous versions of
the software would involve writing liquibase changesets for database
changes made in the previous versions and working out how to identify
whether it should be applied (e.g. by testing the current state of the
database). The scope of work increases the further you try to go back.
Future changes would be controlled by the liquibase changelog,

Jean, I have changesets based on changes made to the migration scripts
in revisions made since December last year - e.g. language code changes,
but they are probably postgres specific at the moment (table changes can
be database dependent). I'm currently testing this update including the
changesets. I guess another approach is just to piece together the
required sql updates using the migration script changes since you last
updated. I also had problems with 'sp' and had to adjust my changesets
to get this to work.

Regards,
CraigJ

On Tue, 2012-04-03 at 09:53 +0200, Jeroen Ticheler wrote:

Hi Craig,
It sounds like a great tool that could improve the software. Do you have suggestions on how to integrate it? Or is it something you have more or less ready to go in to the latest trunk? Should we add it to older versions also (or better: how much work is it to start using this)?
Thanks,
Jeroen

On 3 apr. 2012, at 03:32, Craig Jones wrote:

> Hi All,
>
> I've been using an open source tool called liquibase
> (http://www.liquibase.org/) to put together migration scripts from our
> BlueNetMEST instance to the latest GeoNetwork snapshot.
>
> Thought I'd mention it because it resolves problems like the one Jean is
> having at the moment. Required database changes and update steps are
> automatically applied as required when liquibase is run (we run it every
> time the web app starts up).
>
> Something to look at in future perhaps.
>
>
> Regards,
> --
> Craig Jones
> eMII Infrastructure Programmer
> IMOS e-Marine Information Infrastructure Facility (eMII)
> Ph: +61 3 6226 8567
>
>
>
>
> -------- Forwarded Message --------
> From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
> To: geonetwork-devel@lists.sourceforge.net
> Subject: [GeoNetwork-devel] upgrade database from 1 month-old trunk to
> current trunk
> Date: Mon, 02 Apr 2012 19:31:22 +0200
>
> Hi,
>
> I've got a running geonetwork from the trunk code, 1 month ago. Since
> then, there have been quite a few changes, some in the database.
> I understand we've got the migrate sql codes, that would allow, I
> believe, to upgrade a database from gn 2.6.4 to trunk (2.7.0)
> But trying to apply it on my postgresql database, I get many errors,
> since most of the structure and data is yet here, but not all...
> Do you know an "easy" way to do such an upgrade ?
>
> Note : the DB is yet configured, with many metadatas inside, so I would
> prefer not the make it from scratch and reimport the data. If possible..
>
> Thanks,
>
> Jean
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork
>
>
>
>
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> GeoNetwork-devel mailing list
> GeoNetwork-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
> GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Craig_Jones1 · April 4, 2012, 1:20am

Hi Jean,

Further to my last email, another option is to use liquibase to generate
the required changesets for you.

You could use the diff option of liquibase to create changesets to go
from the previous version you installed to the current version. I'd do
this on blank installs of the two versions.so you only pick up actual
changes between the two versions not data changes.

I'd check the changesets generated to make sure they make sense -
particularly for the settings table as new settings can conflict with
the 'assigned place' for settings in later migration script changes.

Regards,
CraigJ.

On Tue, 2012-04-03 at 16:06 +0200, Jean Pommier (IGE) wrote:

Hi !
Yes indeed, it would be great !

And right now, any idea how I could do it ?
Thanks

Jean

2012/4/3 Jeroen Ticheler <jeroen.ticheler@anonymised.com>
        Hi Craig,
        It sounds like a great tool that could improve the software.
        Do you have suggestions on how to integrate it? Or is it
        something you have more or less ready to go in to the latest
        trunk? Should we add it to older versions also (or better: how
        much work is it to start using this)?
        Thanks,
        Jeroen

        On 3 apr. 2012, at 03:32, Craig Jones wrote:

        > Hi All,
        >
        > I've been using an open source tool called liquibase
        > (http://www.liquibase.org/) to put together migration
        scripts from our
        > BlueNetMEST instance to the latest GeoNetwork snapshot.
        >
        > Thought I'd mention it because it resolves problems like the
        one Jean is
        > having at the moment. Required database changes and update
        steps are
        > automatically applied as required when liquibase is run (we
        run it every
        > time the web app starts up).
        >
        > Something to look at in future perhaps.
        >
        >
        > Regards,
        > --
        > Craig Jones
        > eMII Infrastructure Programmer
        > IMOS e-Marine Information Infrastructure Facility (eMII)
        > Ph: +61 3 6226 8567
        >
        >
        >
        >
        > -------- Forwarded Message --------
        > From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
        > To: geonetwork-devel@lists.sourceforge.net
        > Subject: [GeoNetwork-devel] upgrade database from 1
        month-old trunk to
        > current trunk
        > Date: Mon, 02 Apr 2012 19:31:22 +0200
        >
        > Hi,
        >
        > I've got a running geonetwork from the trunk code, 1 month
        ago. Since
        > then, there have been quite a few changes, some in the
        database.
        > I understand we've got the migrate sql codes, that would
        allow, I
        > believe, to upgrade a database from gn 2.6.4 to trunk
        (2.7.0)
        > But trying to apply it on my postgresql database, I get many
        errors,
        > since most of the structure and data is yet here, but not
        all...
        > Do you know an "easy" way to do such an upgrade ?
        >
        > Note : the DB is yet configured, with many metadatas inside,
        so I would
        > prefer not the make it from scratch and reimport the data.
        If possible..
        >
        > Thanks,
        >
        > Jean
        >
        ------------------------------------------------------------------------------
        > This SF email is sponsosred by:
        > Try Windows Azure free for 90 days Click Here
        > http://p.sf.net/sfu/sfd2d-msazure
        > _______________________________________________
        GeoNetwork-devel mailing list
        GeoNetwork-devel@lists.sourceforge.net
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        GeoNetwork OpenSource is maintained at
        http://sourceforge.net/projects/geonetwork
        >
        >
        >
        >
        >
        ------------------------------------------------------------------------------
        > Better than sec? Nothing is better than sec when it comes to
        > monitoring Big Data applications. Try Boundary one-second
        > resolution app monitoring today. Free.
        > http://p.sf.net/sfu/Boundary-dev2dev
        > _______________________________________________
        > GeoNetwork-devel mailing list
        > GeoNetwork-devel@lists.sourceforge.net
        >
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        > GeoNetwork OpenSource is maintained at
        http://sourceforge.net/projects/geonetwork

        ------------------------------------------------------------------------------
        Better than sec? Nothing is better than sec when it comes to
        monitoring Big Data applications. Try Boundary one-second
        resolution app monitoring today. Free.
        http://p.sf.net/sfu/Boundary-dev2dev
        _______________________________________________
        GeoNetwork-devel mailing list
        GeoNetwork-devel@lists.sourceforge.net
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        GeoNetwork OpenSource is maintained at
        http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Jean_Pommier · April 4, 2012, 8:30am

Hi Craig,

OK, thanks for the advice. I’ll give it a try.
Is Liquibase easy to learn ?
Thanks,

Jean

2012/4/4 Craig Jones <jonescc@anonymised.com>

Hi Jean,

Further to my last email, another option is to use liquibase to generate
the required changesets for you.

You could use the diff option of liquibase to create changesets to go
from the previous version you installed to the current version. I’d do
this on blank installs of the two versions.so you only pick up actual
changes between the two versions not data changes.

I’d check the changesets generated to make sure they make sense -
particularly for the settings table as new settings can conflict with
the ‘assigned place’ for settings in later migration script changes.

Regards,
CraigJ.

On Tue, 2012-04-03 at 16:06 +0200, Jean Pommier (IGE) wrote:

Hi !
Yes indeed, it would be great !

And right now, any idea how I could do it ?
Thanks

Jean

2012/4/3 Jeroen Ticheler <jeroen.ticheler@anonymised.com>
Hi Craig,
It sounds like a great tool that could improve the software.
Do you have suggestions on how to integrate it? Or is it
something you have more or less ready to go in to the latest
trunk? Should we add it to older versions also (or better: how
much work is it to start using this)?
Thanks,
Jeroen

On 3 apr. 2012, at 03:32, Craig Jones wrote:

Hi All,

I’ve been using an open source tool called liquibase
(http://www.liquibase.org/) to put together migration
scripts from our
BlueNetMEST instance to the latest GeoNetwork snapshot.

Thought I’d mention it because it resolves problems like the
one Jean is
having at the moment. Required database changes and update
steps are
automatically applied as required when liquibase is run (we
run it every
time the web app starts up).

Something to look at in future perhaps.

Regards,

Craig Jones
eMII Infrastructure Programmer
IMOS e-Marine Information Infrastructure Facility (eMII)
Ph: +61 3 6226 8567

-------- Forwarded Message --------
From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] upgrade database from 1
month-old trunk to
current trunk
Date: Mon, 02 Apr 2012 19:31:22 +0200

Hi,

I’ve got a running geonetwork from the trunk code, 1 month
ago. Since
then, there have been quite a few changes, some in the
database.
I understand we’ve got the migrate sql codes, that would
allow, I
believe, to upgrade a database from gn 2.6.4 to trunk
(2.7.0)
But trying to apply it on my postgresql database, I get many
errors,
since most of the structure and data is yet here, but not
all…
Do you know an “easy” way to do such an upgrade ?

Note : the DB is yet configured, with many metadatas inside,
so I would
prefer not the make it from scratch and reimport the data.
If possible…

Thanks,

Jean

This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geonetwork-devel

GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Craig_Jones1 · April 4, 2012, 11:59pm

Hi Jean,

Yes, I found liquibase really easy to learn.

Do you know what revision you last updated from?

I probably have the required changesets already and, thinking about it
further, the changesets generated by the diff may not cope with the
recent language code changes.

I've tested my postgres changesets now (my update went smoothly) and I'd
be interested to look at the what modifications would be required for
non-postgres databases.

If I give you the changesets (xml file(s) containing each database
change/migration step that may need to be performed) you'd just need to
download the liquibase jar and run it with the appropriate jdbc
parameters and class path.

This would then provide an example changeset for illustration.

Thanks,
CraigJ

On Wed, 2012-04-04 at 10:30 +0200, Jean Pommier (IGE) wrote:

Hi Craig,

OK, thanks for the advice. I'll give it a try.
Is Liquibase easy to learn ?
Thanks,

Jean

2012/4/4 Craig Jones <jonescc@anonymised.com>
        Hi Jean,

        Further to my last email, another option is to use liquibase
        to generate
        the required changesets for you.

        You could use the diff option of liquibase to create
        changesets to go
        from the previous version you installed to the current
        version. I'd do
        this on blank installs of the two versions.so you only pick up
        actual
        changes between the two versions not data changes.

        I'd check the changesets generated to make sure they make
        sense -
        particularly for the settings table as new settings can
        conflict with
        the 'assigned place' for settings in later migration script
        changes.

        Regards,
        CraigJ.

        On Tue, 2012-04-03 at 16:06 +0200, Jean Pommier (IGE) wrote:
        > Hi !
        > Yes indeed, it would be great !
        >
        > And right now, any idea how I could do it ?
        > Thanks
        >
        > Jean
        >
        > 2012/4/3 Jeroen Ticheler <jeroen.ticheler@anonymised.com>
        > Hi Craig,
        > It sounds like a great tool that could improve the
        software.
        > Do you have suggestions on how to integrate it? Or
        is it
        > something you have more or less ready to go in to
        the latest
        > trunk? Should we add it to older versions also (or
        better: how
        > much work is it to start using this)?
        > Thanks,
        > Jeroen
        >
        > On 3 apr. 2012, at 03:32, Craig Jones wrote:
        >
        > > Hi All,
        > >
        > > I've been using an open source tool called
        liquibase
        > > (http://www.liquibase.org/) to put together
        migration
        > scripts from our
        > > BlueNetMEST instance to the latest GeoNetwork
        snapshot.
        > >
        > > Thought I'd mention it because it resolves
        problems like the
        > one Jean is
        > > having at the moment. Required database changes
        and update
        > steps are
        > > automatically applied as required when liquibase
        is run (we
        > run it every
        > > time the web app starts up).
        > >
        > > Something to look at in future perhaps.
        > >
        > >
        > > Regards,
        > > --
        > > Craig Jones
        > > eMII Infrastructure Programmer
        > > IMOS e-Marine Information Infrastructure Facility
        (eMII)
        > > Ph: +61 3 6226 8567
        > >
        > >
        > >
        > >
        > > -------- Forwarded Message --------
        > > From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
        > > To: geonetwork-devel@lists.sourceforge.net
        > > Subject: [GeoNetwork-devel] upgrade database from
        1
        > month-old trunk to
        > > current trunk
        > > Date: Mon, 02 Apr 2012 19:31:22 +0200
        > >
        > > Hi,
        > >
        > > I've got a running geonetwork from the trunk code,
        1 month
        > ago. Since
        > > then, there have been quite a few changes, some in
        the
        > database.
        > > I understand we've got the migrate sql codes, that
        would
        > allow, I
        > > believe, to upgrade a database from gn 2.6.4 to
        trunk
        > (2.7.0)
        > > But trying to apply it on my postgresql database,
        I get many
        > errors,
        > > since most of the structure and data is yet here,
        but not
        > all...
        > > Do you know an "easy" way to do such an upgrade ?
        > >
        > > Note : the DB is yet configured, with many
        metadatas inside,
        > so I would
        > > prefer not the make it from scratch and reimport
        the data.
        > If possible..
        > >
        > > Thanks,
        > >
        > > Jean
        > >
        >
        ------------------------------------------------------------------------------
        > > This SF email is sponsosred by:
        > > Try Windows Azure free for 90 days Click Here
        > > http://p.sf.net/sfu/sfd2d-msazure
        > > _______________________________________________
        > GeoNetwork-devel mailing list
        > GeoNetwork-devel@lists.sourceforge.net
        >
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        > GeoNetwork OpenSource is maintained at
        > http://sourceforge.net/projects/geonetwork
        > >
        > >
        > >
        > >
        > >
        >
        ------------------------------------------------------------------------------
        > > Better than sec? Nothing is better than sec when
        it comes to
        > > monitoring Big Data applications. Try Boundary
        one-second
        > > resolution app monitoring today. Free.
        > > http://p.sf.net/sfu/Boundary-dev2dev
        > > _______________________________________________
        > > GeoNetwork-devel mailing list
        > > GeoNetwork-devel@lists.sourceforge.net
        > >
        >
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        > > GeoNetwork OpenSource is maintained at
        > http://sourceforge.net/projects/geonetwork
        >
        >
        >
        ------------------------------------------------------------------------------
        > Better than sec? Nothing is better than sec when it
        comes to
        > monitoring Big Data applications. Try Boundary
        one-second
        > resolution app monitoring today. Free.
        > http://p.sf.net/sfu/Boundary-dev2dev
        > _______________________________________________
        > GeoNetwork-devel mailing list
        > GeoNetwork-devel@lists.sourceforge.net
        >
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        > GeoNetwork OpenSource is maintained at
        > http://sourceforge.net/projects/geonetwork
        >
        >
        >
        ------------------------------------------------------------------------------
        > Better than sec? Nothing is better than sec when it comes to
        > monitoring Big Data applications. Try Boundary one-second
        > resolution app monitoring today. Free.
        > http://p.sf.net/sfu/Boundary-dev2dev
        > _______________________________________________
        GeoNetwork-devel mailing list
        GeoNetwork-devel@lists.sourceforge.net
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        GeoNetwork OpenSource is maintained at
        http://sourceforge.net/projects/geonetwork

        ------------------------------------------------------------------------------
        Better than sec? Nothing is better than sec when it comes to
        monitoring Big Data applications. Try Boundary one-second
        resolution app monitoring today. Free.
        http://p.sf.net/sfu/Boundary-dev2dev
        _______________________________________________
        GeoNetwork-devel mailing list
        GeoNetwork-devel@lists.sourceforge.net
        https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
        GeoNetwork OpenSource is maintained at
        http://sourceforge.net/projects/geonetwork

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Jean_Pommier · April 5, 2012, 7:32am

Hi Craig,

You’re very kind, but in fact, I tried updating my geonetwork instance yesterday with latest trunk, and didn’t manage to make it work (even with a plain new DB). Lost 1 day work, and I have a deadline arriving faast. So I’ll have to postpone all this. I’ll keep with my older revision until the deadline is past (april, 15), and we’ll see then.

By the way, I had some kind of mixing up my databases : I was not trying to upgrade a database from trunk, but from GN 2.6.4 (it did not work). Using the correct DB (trunk, 1 month old, rev 8973) it worked almost smoothly. I just had to change some mismatch in the language codes.
But thanks again for your help, and I hope past april, 15, I’ll have time to look at this. It seems pretty useful for the future…
Cheers,

Jean

2012/4/5 Craig Jones <jonescc@anonymised.com>

Hi Jean,

Yes, I found liquibase really easy to learn.

Do you know what revision you last updated from?

I probably have the required changesets already and, thinking about it
further, the changesets generated by the diff may not cope with the
recent language code changes.

I’ve tested my postgres changesets now (my update went smoothly) and I’d
be interested to look at the what modifications would be required for
non-postgres databases.

If I give you the changesets (xml file(s) containing each database
change/migration step that may need to be performed) you’d just need to
download the liquibase jar and run it with the appropriate jdbc
parameters and class path.

This would then provide an example changeset for illustration.

Thanks,
CraigJ

On Wed, 2012-04-04 at 10:30 +0200, Jean Pommier (IGE) wrote:

Hi Craig,

OK, thanks for the advice. I’ll give it a try.
Is Liquibase easy to learn ?
Thanks,

Jean

2012/4/4 Craig Jones <jonescc@…158…>
Hi Jean,

Further to my last email, another option is to use liquibase
to generate
the required changesets for you.

You could use the diff option of liquibase to create
changesets to go
from the previous version you installed to the current
version. I’d do
this on blank installs of the two versions.so you only pick up
actual
changes between the two versions not data changes.

I’d check the changesets generated to make sure they make
sense -
particularly for the settings table as new settings can
conflict with
the ‘assigned place’ for settings in later migration script
changes.

Regards,
CraigJ.

On Tue, 2012-04-03 at 16:06 +0200, Jean Pommier (IGE) wrote:

Hi !
Yes indeed, it would be great !

And right now, any idea how I could do it ?
Thanks

Jean

2012/4/3 Jeroen Ticheler <jeroen.ticheler@anonymised.com>
Hi Craig,
It sounds like a great tool that could improve the
software.
Do you have suggestions on how to integrate it? Or
is it
something you have more or less ready to go in to
the latest
trunk? Should we add it to older versions also (or
better: how
much work is it to start using this)?
Thanks,
Jeroen

On 3 apr. 2012, at 03:32, Craig Jones wrote:

Hi All,

I’ve been using an open source tool called
liquibase
(http://www.liquibase.org/) to put together
migration
scripts from our
BlueNetMEST instance to the latest GeoNetwork
snapshot.

Thought I’d mention it because it resolves
problems like the
one Jean is
having at the moment. Required database changes
and update
steps are
automatically applied as required when liquibase
is run (we
run it every
time the web app starts up).

Something to look at in future perhaps.

Regards,

Craig Jones
eMII Infrastructure Programmer
IMOS e-Marine Information Infrastructure Facility
(eMII)
Ph: +61 3 6226 8567

-------- Forwarded Message --------
From: Jean Pommier (IGE) <jean.pommier@anonymised.com>
To: geonetwork-devel@lists.sourceforge.net
Subject: [GeoNetwork-devel] upgrade database from
1
month-old trunk to
current trunk
Date: Mon, 02 Apr 2012 19:31:22 +0200

Hi,

I’ve got a running geonetwork from the trunk code,
1 month
ago. Since
then, there have been quite a few changes, some in
the
database.
I understand we’ve got the migrate sql codes, that
would
allow, I
believe, to upgrade a database from gn 2.6.4 to
trunk
(2.7.0)
But trying to apply it on my postgresql database,
I get many
errors,
since most of the structure and data is yet here,
but not
all…
Do you know an “easy” way to do such an upgrade ?

Note : the DB is yet configured, with many
metadatas inside,
so I would
prefer not the make it from scratch and reimport
the data.
If possible…

Thanks,

Jean

This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure

GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.comourceforge.net

https://lists.sourceforge.net/lists/listinfo/geonetwork-devel

GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when
it comes to
monitoring Big Data applications. Try Boundary
one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.coms.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geonetwork-devel

GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it
comes to
monitoring Big Data applications. Try Boundary
one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@anonymised.comourceforge.net

https://lists.sourceforge.net/lists/listinfo/geonetwork-devel

GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at
http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________ GeoNetwork-devel mailing list GeoNetwork-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geonetwork-devel GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork

Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev

GeoNetwork-devel mailing list
GeoNetwork-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-devel
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork