"Migration" mis-detecting db version?

[osjonathan]

I'm not sure how major this bug is, so I'll leave it as default.

My database is an Oracle one that was created with GeoNetwork 2.6.0 RC0 (you may recall there was a bug in that one where the Oracle DB creator didn't work - Jose Garcia fixed it and over the users-mailing list sent me a link to the working file). As such I'm 99% certain my DB was created with a 2.6.0 build.

But looking in my geonetwork.log file I see it saying that it's 2.5.0 and there are migration issues:

---

2010-09-20 14:43:21,590 INFO [jeeves.apphand] - - Migration ... 2010-09-20 14:43:21,590 DEBUG [jeeves.apphand] - Webapp version:2.6.0 subversion:RC2 2010-09-20 14:43:21,590 DEBUG [jeeves.apphand] - Database version:2.5.0 subversion:0 2010-09-20 14:43:21,590 INFO [jeeves.apphand] - Migrating from 2.5.0 to 2.6.0 (dbtype:mckoi)... 2010-09-20 14:43:21,590 INFO [jeeves.apphand] - No migration task found between webapp and database version.

The system may be unstable or may failed to start if you try to run the current GeoNetwork 2.6.0 with an older database (ie. 2.5.0 ). Try to run the migration task manually on the current database before starting the application or start with a new empty database. Sample SQL scripts for migration could be found in WEB-INF/sql/migrate folder.

---

I've never downloaded or run a 2.5.0 build, so have no idea where it's getting that from.

[Fxp]

DB Version was wrong in 2.6.0RC sql scripts. That's why you get that warning. You should update your node version in Settings table. Migration task is not really used yet.

[osjonathan]

Updated the "version" setting in the DB to "2.6.0", and it's no-longer complaining. It's implied by your reply that this issue (the creating-SQL) is resolved for 2.6.0 proper.

[ticheler]

Version numbers should be updated by the release team to ensure this works as designed. Thanks for the warning.