[MRM-1176] SQLSyntaxErrorException is thrown when browsing for artifacts after upgrading from 1.3.1 to 1.2

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2
• Fix Version/s: 1.2.1
• Component/s: Web Interface
• Environment: App Server: Sun Java System Application Server 9.1_01 (aka Glassfish v2), Database: Apache Derby 10.2.2, Java: 1.6.0_03, OS: Red Hat Enterprise Linux Server release 5.3 (i686)
• Assignee: Maria Odea B. Ching
• Reporter: Brian Schlining
• Created: 01/May/09 12:07
• Updated: 24/May/09 06:01
• Resolved: 24/May/09 06:01

Description

I upgraded from Archiva 1.3.1 to 1.2 by replacing the existing 1.3.1 war file with the new 1.2 war file. When I browse for a file, I can see the group ID's and package ID's with no problem but when I click on a version link the following error is thrown:

Exception

javax.servlet.ServletException: org.apache.maven.archiva.database.ArchivaDatabaseException: Error in JDO during get of Database object id [com.miginfocom:migcalendarbean:6.6.3] of type org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group

Root Cause

org.apache.maven.archiva.database.ArchivaDatabaseException: Error in JDO during get of Database object id [com.miginfocom:migcalendarbean:6.6.3] of type org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group

Root Cause

javax.jdo.JDODataStoreException: Error(s) were found while auto-creating/validating the datastore for classes. The errors are printed in the log, and are attached to this exception.
NestedThrowables:
java.sql.SQLSyntaxErrorException: In an ALTER TABLE statement, the column 'ARCHIVA_INDIVIDUAL_ID' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.
java.sql.SQLSyntaxErrorException: In an ALTER TABLE statement, the column 'ARCHIVA_ISSUE_MANAGEMENT_ID' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.
java.sql.SQLSyntaxErrorException: In an ALTER TABLE statement, the column 'ARCHIVA_ORGANIZATION_ID' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.
java.sql.SQLSyntaxErrorException: In an ALTER TABLE statement, the column 'ARCHIVA_CIMANAGEMENT_ID' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.
java.sql.SQLException: Constraint 'ARCHIVA_PROJTY_FK7' is invalid: there is no unique or primary key constraint on table 'APP.ARCHIVA_CIMANAGEMENT' that matches the number and types of the columns in the foreign key.
java.sql.SQLException: Constraint 'ARCHIVA_PROJTY_FK8' is invalid: there is no unique or primary key constraint on table 'APP.ARCHIVA_ORGANIZATION' that matches the number and types of the columns in the foreign key.
java.sql.SQLException: Constraint 'ARCHIVA_PROJTY_FK9' is invalid: there is no unique or primary key constraint on table 'APP.ARCHIVA_ISSUE_MANAGEMENT' that matches the number and types of the columns in the foreign key.

Root Cause

java.sql.SQLSyntaxErrorException: In an ALTER TABLE statement, the column 'ARCHIVA_INDIVIDUAL_ID' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.

Root Cause

org.apache.derby.client.am.SqlException: In an ALTER TABLE statement, the column 'ARCHIVA_INDIVIDUAL_ID' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.

Issue Links

• is related to: MRM-1157 Update from 1.1.3 to 1.2 fails with create table error