Database errors when upgrading to OCS 2.3.5

Are you responsible for making OCS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, michael, John

Forum rules
The Public Knowledge Project Support Forum is moving to

This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.
Posts: 16
Joined: Wed Oct 10, 2007 12:45 am
Location: University of British Columbia

Database errors when upgrading to OCS 2.3.5

Postby derekp » Mon Jul 16, 2012 4:13 pm

I encountered two errors when upgrading OCS 2.1.2 to 2.3.5. The database is PostgreSQL 9.0.

The first error was a violation of the NOT NULL constraint on the assoc_type column of the announcement_types table. My workaround for that was to comment out the <NOTNULL/> for the assoc_type field in lib/pkp/xml/schema/announcements.xml, then manually execute

Code: Select all

ALTER TABLE announcement_types ALTER COLUMN assoc_type SET NOT NULL

The second error came when trying to execute dbscripts/xml/upgrade/2.3.4_update.xml. The SQL statements are in <query driver="postgres"> elements; they should be <query driver="postgres7"> instead. As a result, Installer::executeAction() finds no SQL statements in 2.3.4_update.xml to execute and aborts with an error message installer.installParseDBFileError (lib/pkp/classes/install/ line 393).

Return to “OCS Technical Support”

Who is online

Users browsing this forum: Baidu [Spider] and 2 guests