Dear list,
I want to migrate an existing 2.10 GN catalog to GN 3. Therefore I
duplicated the exisitng external geonetwork data dir and the database.
After changing the directory details and the db configuration, GN3 is
deployed but the log shows some errors, the last being a show stopper.
- one issue is an error with the db migration/update (from pg_log):
'ERROR: there is no primary key for referenced table "services" '. This is
strange as in the old db (2.10.3) the services table has this primary key,
but in the migrated one it's not present anymore, I went thru the migration
scripts, this table is added in v2100/migrate-db-postgis.sql. Then the
column (and thus the PK) is removed in v2110/2-migrate-default.sql. Why the
column is still present but no primary key anymore, I don't know.
- when trying to acces the ui, I get the following error: "Repository uses
database URL of 'jdbc:postgresql_postGIS://localhost:5432/geonetwork2103'
which does not match current database URL
'jdbc:postgresql://localhost:5432/geonetwork3x'. Modify the svn property
geonet:dburl..."
I'm not sure how to solve this... Can I really change the corresponsing
value in the metadata_subversion directory? Another option, as I found in a
discussion, was to remove the directory and have it recreatd on
startup.What are we loosing?
Thanks for your help, Michael
--
-----------------------------------------------------------
Michael Schulz
Hi,
ok, no need to proceed. The migration did not work for us. After trying
with a clean metadata_subversion directory and adding the PK manually, GN3
started and I could see most/all of the "migrated" data. After an index
rebuild basically no information was displayed anymore in the UI, the data
was still there (e.g. XML export), but since I only had a small number of
records so far in the catalog, we went for a clean, fresh install and are
importing the records.
Thanks, Michael
2015-08-17 15:34 GMT+02:00 Michael Schulz <mandschulz@anonymised.com>:
Dear list,
I want to migrate an existing 2.10 GN catalog to GN 3. Therefore I
duplicated the exisitng external geonetwork data dir and the database.
After changing the directory details and the db configuration, GN3 is
deployed but the log shows some errors, the last being a show stopper.
- one issue is an error with the db migration/update (from pg_log):
'ERROR: there is no primary key for referenced table "services" '. This is
strange as in the old db (2.10.3) the services table has this primary key,
but in the migrated one it's not present anymore, I went thru the migration
scripts, this table is added in v2100/migrate-db-postgis.sql. Then the
column (and thus the PK) is removed in v2110/2-migrate-default.sql. Why
the column is still present but no primary key anymore, I don't know.
- when trying to acces the ui, I get the following error: "Repository uses
database URL of 'jdbc:postgresql_postGIS://localhost:5432/geonetwork2103'
which does not match current database URL
'jdbc:postgresql://localhost:5432/geonetwork3x'. Modify the svn property
geonet:dburl..."
I'm not sure how to solve this... Can I really change the corresponsing
value in the metadata_subversion directory? Another option, as I found in a
discussion, was to remove the directory and have it recreatd on
startup.What are we loosing?
Thanks for your help, Michael
--
-----------------------------------------------------------
Michael Schulz
--