On Fri, Jun 11, 2010 at 02:49:07PM -0500, Harish Maringanti wrote: > I'm trying to upgrade our test dspace instance from 1.5.2 to 1.6 & am having > some issues. Wanted to check if these had anything to do with the versions > we are using - postgresql 7.4.6 & tomcat 5.0.28.
Those are both very old releases. Tomcat 5.0 is no longer supported
by the Tomcat maintainers, and the current release is 6.0.26 (which
runs DSpace very well). I'm not sure whether PostgreSQL 7.x is
supported by its maintainers or not, but 8.4 is current (and serves
DSpace well) and 9.0 is in beta. May I suggest at least Tomcat 5.5
and PostgreSQL 8.1.
> When I ran the database schema script I got these errors:
> ---------------------------------------
> psql: database_schema_15-16.sql:56: ERROR: adding columns with defaults is
> not implemented
> HINT: Add the column, then use ALTER TABLE SET DEFAULT
> ----------------------------------------------------
It looks as though 7.x did not completely execute the schema update.
This will cause problems later...
> I proceeded with the upgrade anyway (test) and encountered the following
> error in the tomcat logs:
> --------------------------------------------------------
> StandardWrapperValve[handle]: Servlet.service() for servlet handle threw
> exception
> java.lang.IllegalArgumentException: No such column confidence
> at org.dspace.storage.rdbms.TableRow.getIntColumn(TableRow.java:157)
> at org.dspace.content.Item.<init>(Item.java:179)
> at org.dspace.content.Item.find(Item.java:248)
> ----------------------------------------------------------------------------------
...as you can see.
> Looks like the 2nd error is related to the database error reported
> above..did the db schema upgrade script throw an error because of the
> postgresql version ? Any advise is much appreciated.
I believe you are correct.
I hope you have a backup of your database. Simplest would be to
upgrade PostgreSQL to 8.x, restore the backup, dump a separate new
backup using 8.x (in case anything else goes wrong), and try the
schema upgrade again. (If you're able to install 8.x alongside 7.x,
you can use 8.x tools to dump from the 7.x server, and I believe this
is recommended for Pg upgrades. But first you need to recover the
un-upgraded database.)
As an UNTESTED workaround, you might instead try restoring your backup
and then splitting line 56 of database_schema_15-16.sql:
ALTER TABLE MetadataValue ADD confidence INTEGER DEFAULT -1;
to:
ALTER TABLE MetadataValue ADD confidence INTEGER;
ALTER TABLE MetadataValue ALTER COLUMN confidence SET DEFAULT -1;
and rerunning the schema upgrade. There may be other usages in the
script which don't work in 7.x. I don't have a 7.x to test with. If
you can upgrade PostgreSQL, I would do that instead.
The 1.6.1 documentation does still treat Pg 7.3 and 7.4. It looks as
though we need to either note that 7.x is no longer usable and remove
the 7.x instructions, or rework the schema upgrade script. The 7.4
documentation says both that ALTER TABLE ADD COLUMN uses the same
syntax as CREATE TABLE (which supports DEFAULT) and, much later, that
DEFAULT is not supported. It appears that the latter is correct.
Considering the age of 7.x I would suggest leaving it behind at the
next opportunity, whatever might be done with the schema upgrade
script in the meantime.
--
Mark H. Wood, Lead System Programmer mw...@iupui.edu
Balance your desire for bells and whistles with the reality that only a
little more than 2 percent of world population has broadband.
-- Ledford and Tyler, _Google Analytics 2.0_
pgp4AAofZWES8.pgp
Description: PGP signature
------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
