Hi Andrew,
We have been following a similar upgrade path and now using
Bluenet v1.4.2. So far we have managed upgrades without having to re-build
the database and have not used export/import of MEF files.
The advantage of this over the MEF method is that you
get to preserve all the groups, users and records permission information,
which for us would have been very tedious to rebuild.
The db changes from 1.2 to 1.4.2 (Simon Pigot will correct me if I am wrong on this)
were:
1) a change on the uniqueness constraints in the 'Metadata' table
In oracle sql script for v1.2 got 'unique(uuid,source,harvestUuid)' but
in v1.4.2 its 'unique(uuid)'. See file /gast/setup/sql/create-db-oracle.sql
in the 2 versions.
2) Several additional entries on the 'settings' table.
The first change above can be handled by altering the uniqueness constraints
with an SQL tool.
The change to the settings table is much more tricky as it is not an
easy table to follow. We tried at first hand editing
the table but this failed and our entry got all mixed up. We then decided
to re-build a test version of the settings table by:
- installing a test instance of v1.4.2,
- building the Oracle db tables with gast and the create-db-oracle.sql script
- login as admin and go to system configuration page and enter all
the settings as you would have in your production instance.
- the settings table also holds information on harvest nodes. So if you
had any harvests running go to admin->harvest configuration and re-build these.
Following the above you now have a working settings table in the test instance.
Further steps in our upgrade procedure were:
- Back up the old prod. settings table and do a text dump of it
- drop or truncate the settings table
- import with SQL the new settings table from the test instance to the prod. db.
- Go to the settings table with an SQL editor and set the 'siteId'
to the existing value on the production instance.
- Install v.1.4.2 on prod. with no sample metadata. The Geonetwork 'data'
directory should be clean as you will copy contents from the old version
to here.
- With gast point the new version at the existing database.
- Copy all the material in the Geonetwork 'data' directory from the old version
to the new. This includes all the thumbnails and data files
for download. On Unix/Linux this would be
from /oldversionpath/web/geonetwork/WEB-INF/data
cp -rp * /newversionpath/web/geonetwork/WEB-INF/data
- Copy the existing site logo to the new version from
web/geonetwork/images/logos e.g
cp -p * /newversionpath/web/geonetwork/images/logos
The above procedure should restore all your content to the new version.
Hope this helps, let us know how you decide to do your upgrade.
Andrew
----- Original Message ----- From: "Andrew Watkins" <a.watkins@anonymised.com>
To: "geonetwork-users Users" <geonetwork-users@lists.sourceforge.net>
Sent: Tuesday, April 12, 2011 1:03 PM
Subject: [GeoNetwork-users] upgrading advice
I'm moving from BlueNetMEST 1.2 to 1.4.2 There are some changes to the database schema that mean that I can't just continue with the original db.
What is the 'official' method of bringing existing data forwards?
Is it to
a) export and re-import .mef files
b) to harvest from the older system into the new one.
What are the things to watch out for in each case?
Thanks Andrew
Please consider the environment before printing this email.
NIWA is the trading name of the National Institute of Water & Atmospheric Research Ltd.
------------------------------------------------------------------------------
Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now! http://p.sf.net/sfu/ibm-webcastpromo
_______________________________________________
GeoNetwork-users mailing list
GeoNetwork-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geonetwork-users
GeoNetwork OpenSource is maintained at http://sourceforge.net/projects/geonetwork