[GeoNetwork-users] "statusvalues" does not exist error after updating GN 2.7 r8681

Hockaday_John · February 15, 2012, 11:33pm

Hi All,

Yesterday I upgraded GeoNetwork 2.7 to r8681 using Subversion. I then
started testing the interface and noticed that search requests returned
zero results. I have looked in the catalina.out file and noticed this
line:

<<<<<<<<<<<< catalina.out >>>>>>>>>>>>
ERROR [jeeves.service] - (C) Stack trace is :
org.postgresql.util.PSQLException: ERROR: relation "statusvalues" does
not exist
<<<<<<<<<<<< catalina.out >>>>>>>>>>>>

I have searched for "statusvalues" on the GeoNetwork developers web site
and noticed that Simon Pigot's article on "Metadata status: capturing
the lifecycle of a metadata record" mentions the "statusvalues" field.

Has anybody else had this problem?

Does this mean that I have an error in my Postgis database?

Do I need to update that database somehow?

Do I need to put in a ticket for this?

Many thanks in advance to anyone who can help me.

John Hockaday

sppigot · February 16, 2012, 3:59am

John.

I suspect you are 'upgrading' from an earlier version of GeoNetwork 2.7 with an existing database that doesn't match the latest version. There are no migration scripts for this kind of upgrade path - if you like I'll take a look at your database and see what needs to be brought in to upgrade your early 2.7 database to one that suits your current 2.7.

Cheers,
Simon
________________________________________
From: owner-anzlicmet-l@anonymised.com [owner-anzlicmet-l@anonymised.com] On Behalf Of john.hockaday [john.hockaday@anonymised.com]
Sent: Thursday, 16 February 2012 10:33 AM
To: geonetwork-users; anzlicmet-l@anonymised.com
Subject: "statusvalues" does not exist error after updating GN 2.7 r8681