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
By the way, it looks like there are some errors in the migration sql script : turkish (tur) language is missing, and the new ones seem not to be inserted in the tables (vie, nor, fin)
2012/4/2 Jean Pommier (IGE) <jean.pommier@anonymised.com>
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
OK, I’ve tried, changing a little bit the migration script’s code in order to get it working smoothly.
But even then, when I launch geonetwork against this “up to date” database, I get errors for each of my metadatas :
ERROR [geonetwork.datamanager] - The metadata document index with id=134 is corrupt/invalid - ignoring it. Error: ERROR: current transaction is aborted, commands ignored until end of transaction block
org.postgresql.util.PSQLException: ERROR: current transaction is aborted, commands ignored until end of transaction block
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2062)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1795)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:479)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:367)
at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:271)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at jeeves.resources.dbms.Dbms.selectFull(Dbms.java:210)
at jeeves.resources.dbms.Dbms.select(Dbms.java:181)
at org.fao.geonet.kernel.XmlSerializer.internalSelect(XmlSerializer.java:92)
at org.fao.geonet.kernel.XmlSerializerSvn.internalSelect(XmlSerializerSvn.java:72)
at org.fao.geonet.kernel.XmlSerializerSvn.selectNoXLinkResolver(XmlSerializerSvn.java:107)
at org.fao.geonet.kernel.DataManager.indexMetadata(DataManager.java:436)
at org.fao.geonet.kernel.DataManager.indexMetadataGroup(DataManager.java:419)
at org.fao.geonet.kernel.DataManager$IndexMetadataTask.run(DataManager.java:367)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
and the result is almost nothing works (no metadata loaded, not possible to login)
Checking with an old gn 2.6.4 database, I can confirm there seem to be errors in the 2 char lang codes (‘es’ in place of ‘sp’, ‘pt’ in place of ‘po’, turkish absent, etc) in the migration script.
I’m definitely going to fill a ticket.
2012/4/2 Jean Pommier (IGE) <jean.pommier@anonymised.com>
By the way, it looks like there are some errors in the migration sql script : turkish (tur) language is missing, and the new ones seem not to be inserted in the tables (vie, nor, fin)
2012/4/2 Jean Pommier (IGE) <jean.pommier@anonymised.com>
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