You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Marc Lustig <ml...@marclustig.com> on 2009/05/19 11:13:53 UTC
Migration 1.1.3 => 1.2 - JDO issues !
We have been running Archiva 1.x for about 13 months now serving now about 20
teams/120 developers. In order to get rid of the tedious error messages
"unable to find project model" in the browse view and to benefit from the
new features and the new layout we tried upgrading to Archiva 1.2 by
following the instructions located here
http://archiva.apache.org/docs/1.2/adminguide/webapp.html and here
http://archiva.apache.org/docs/1.2/adminguide/standalone.html
We are running Archiva in Tomcat6 on jdk1.6.0_07 with Oracle RAC database.
After deploying the webapp it is impossible to browse the repositories
anymore, as we get various errors by JDO-implementation, such as
Error in JDO during get of Database object id
[xxx:automotive-benutzerverwaltung-actions:1.13-20081121.175349-3] of type
org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-group
...
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: ORA-01758: table must be empty to add
mandatory (NOT NULL) column
java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to add
mandatory (NOT NULL) column
java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to add
mandatory (NOT NULL) column
java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to add
mandatory (NOT NULL) column
java.sql.SQLSyntaxErrorException: ORA-00904: "ARCHIVA_ORGANIZATION_ID":
invalid identifier
java.sql.SQLSyntaxErrorException: ORA-00904: "ARCHIVA_ISSUE_MANAGEMENT_ID":
invalid identifier
java.sql.SQLSyntaxErrorException: ORA-00904: "ARCHIVA_CIMANAGEMENT_ID":
invalid identifier
=> It seems that the webapp tries to generate a fresh schema.
=> Anybody know what exactly is going on and how to work around?
Marc
--
View this message in context: http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23612501.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Migration 1.1.3 => 1.2 - JDO issues !
Posted by Marc Lustig <ml...@marclustig.com>.
Ok sorry, of course I mean archiva, i. e. the datasource jdbc/archiva.
The question is if I can savely empty all the tables of that database and
let it recreate from scratch by pressing the button "Update database now".
brettporter wrote:
>
> jdbc/archiva, since that's what you are asking about.
> If you delete Continuum's database, Continuum will lose all it's data, but
> that's a different list to ask on :)
>
> 2009/5/20 Marc Lustig <ml...@marclustig.com>
>
>>
>> Thanks Brett for the hints.
>>
>> You are speaking about the RDBMS-database configured as datasource
>> "jdbc/continuum", right?
>>
>> Do I understand you correct, you can empty all tables of that database,
>> press the "Update database now" button, and the database will be filled
>> from
>> scratch to work properly again ?
>>
>>
>>
>>
>> brettporter wrote:
>> >
>> > You are best to delete the archiva database and rescan to regenerate
>> > it after an upgrade at this point.
>> >
>> > Please be aware that there are a few issues with indexing in the 1.2
>> > release that will be resolved in the near future with a 1.2.1 release.
>> >
>> > - Brett
>> >
>> > On 19/05/2009, at 7:13 PM, Marc Lustig wrote:
>> >
>> >>
>> >> We have been running Archiva 1.x for about 13 months now serving now
>> >> about 20
>> >> teams/120 developers. In order to get rid of the tedious error
>> >> messages
>> >> "unable to find project model" in the browse view and to benefit
>> >> from the
>> >> new features and the new layout we tried upgrading to Archiva 1.2 by
>> >> following the instructions located here
>> >> http://archiva.apache.org/docs/1.2/adminguide/webapp.html and here
>> >> http://archiva.apache.org/docs/1.2/adminguide/standalone.html
>> >>
>> >> We are running Archiva in Tomcat6 on jdk1.6.0_07 with Oracle RAC
>> >> database.
>> >>
>> >> After deploying the webapp it is impossible to browse the repositories
>> >> anymore, as we get various errors by JDO-implementation, such as
>> >>
>> >> Error in JDO during get of Database object id
>> >> [xxx:automotive-benutzerverwaltung-actions:1.13-20081121.175349-3]
>> >> of type
>> >> org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-
>> >> group
>> >> ...
>> >> 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: ORA-01758: table must be empty to
>> >> add
>> >> mandatory (NOT NULL) column
>> >>
>> >> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
>> >> add
>> >> mandatory (NOT NULL) column
>> >>
>> >> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
>> >> add
>> >> mandatory (NOT NULL) column
>> >>
>> >> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
>> >> add
>> >> mandatory (NOT NULL) column
>> >>
>> >> java.sql.SQLSyntaxErrorException: ORA-00904:
>> >> "ARCHIVA_ORGANIZATION_ID":
>> >> invalid identifier
>> >>
>> >> java.sql.SQLSyntaxErrorException: ORA-00904:
>> >> "ARCHIVA_ISSUE_MANAGEMENT_ID":
>> >> invalid identifier
>> >>
>> >> java.sql.SQLSyntaxErrorException: ORA-00904:
>> >> "ARCHIVA_CIMANAGEMENT_ID":
>> >> invalid identifier
>> >>
>> >>
>> >>
>> >> => It seems that the webapp tries to generate a fresh schema.
>> >>
>> >> => Anybody know what exactly is going on and how to work around?
>> >>
>> >> Marc
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23612501.html
>> >> Sent from the archiva-users mailing list archive at Nabble.com.
>> >>
>> >
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23619456.html
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Brett Porter
> http://blogs.exist.com/bporter/
>
>
--
View this message in context: http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23630402.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Migration 1.1.3 => 1.2 - JDO issues !
Posted by Brett Porter <br...@apache.org>.
jdbc/archiva, since that's what you are asking about.
If you delete Continuum's database, Continuum will lose all it's data, but
that's a different list to ask on :)
2009/5/20 Marc Lustig <ml...@marclustig.com>
>
> Thanks Brett for the hints.
>
> You are speaking about the RDBMS-database configured as datasource
> "jdbc/continuum", right?
>
> Do I understand you correct, you can empty all tables of that database,
> press the "Update database now" button, and the database will be filled
> from
> scratch to work properly again ?
>
>
>
>
> brettporter wrote:
> >
> > You are best to delete the archiva database and rescan to regenerate
> > it after an upgrade at this point.
> >
> > Please be aware that there are a few issues with indexing in the 1.2
> > release that will be resolved in the near future with a 1.2.1 release.
> >
> > - Brett
> >
> > On 19/05/2009, at 7:13 PM, Marc Lustig wrote:
> >
> >>
> >> We have been running Archiva 1.x for about 13 months now serving now
> >> about 20
> >> teams/120 developers. In order to get rid of the tedious error
> >> messages
> >> "unable to find project model" in the browse view and to benefit
> >> from the
> >> new features and the new layout we tried upgrading to Archiva 1.2 by
> >> following the instructions located here
> >> http://archiva.apache.org/docs/1.2/adminguide/webapp.html and here
> >> http://archiva.apache.org/docs/1.2/adminguide/standalone.html
> >>
> >> We are running Archiva in Tomcat6 on jdk1.6.0_07 with Oracle RAC
> >> database.
> >>
> >> After deploying the webapp it is impossible to browse the repositories
> >> anymore, as we get various errors by JDO-implementation, such as
> >>
> >> Error in JDO during get of Database object id
> >> [xxx:automotive-benutzerverwaltung-actions:1.13-20081121.175349-3]
> >> of type
> >> org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-
> >> group
> >> ...
> >> 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: ORA-01758: table must be empty to
> >> add
> >> mandatory (NOT NULL) column
> >>
> >> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
> >> add
> >> mandatory (NOT NULL) column
> >>
> >> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
> >> add
> >> mandatory (NOT NULL) column
> >>
> >> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
> >> add
> >> mandatory (NOT NULL) column
> >>
> >> java.sql.SQLSyntaxErrorException: ORA-00904:
> >> "ARCHIVA_ORGANIZATION_ID":
> >> invalid identifier
> >>
> >> java.sql.SQLSyntaxErrorException: ORA-00904:
> >> "ARCHIVA_ISSUE_MANAGEMENT_ID":
> >> invalid identifier
> >>
> >> java.sql.SQLSyntaxErrorException: ORA-00904:
> >> "ARCHIVA_CIMANAGEMENT_ID":
> >> invalid identifier
> >>
> >>
> >>
> >> => It seems that the webapp tries to generate a fresh schema.
> >>
> >> => Anybody know what exactly is going on and how to work around?
> >>
> >> Marc
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23612501.html
> >> Sent from the archiva-users mailing list archive at Nabble.com.
> >>
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23619456.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>
--
Brett Porter
http://blogs.exist.com/bporter/
Re: Migration 1.1.3 => 1.2 - JDO issues !
Posted by Marc Lustig <ml...@marclustig.com>.
Thanks Brett for the hints.
You are speaking about the RDBMS-database configured as datasource
"jdbc/continuum", right?
Do I understand you correct, you can empty all tables of that database,
press the "Update database now" button, and the database will be filled from
scratch to work properly again ?
brettporter wrote:
>
> You are best to delete the archiva database and rescan to regenerate
> it after an upgrade at this point.
>
> Please be aware that there are a few issues with indexing in the 1.2
> release that will be resolved in the near future with a 1.2.1 release.
>
> - Brett
>
> On 19/05/2009, at 7:13 PM, Marc Lustig wrote:
>
>>
>> We have been running Archiva 1.x for about 13 months now serving now
>> about 20
>> teams/120 developers. In order to get rid of the tedious error
>> messages
>> "unable to find project model" in the browse view and to benefit
>> from the
>> new features and the new layout we tried upgrading to Archiva 1.2 by
>> following the instructions located here
>> http://archiva.apache.org/docs/1.2/adminguide/webapp.html and here
>> http://archiva.apache.org/docs/1.2/adminguide/standalone.html
>>
>> We are running Archiva in Tomcat6 on jdk1.6.0_07 with Oracle RAC
>> database.
>>
>> After deploying the webapp it is impossible to browse the repositories
>> anymore, as we get various errors by JDO-implementation, such as
>>
>> Error in JDO during get of Database object id
>> [xxx:automotive-benutzerverwaltung-actions:1.13-20081121.175349-3]
>> of type
>> org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-
>> group
>> ...
>> 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: ORA-01758: table must be empty to
>> add
>> mandatory (NOT NULL) column
>>
>> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
>> add
>> mandatory (NOT NULL) column
>>
>> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
>> add
>> mandatory (NOT NULL) column
>>
>> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
>> add
>> mandatory (NOT NULL) column
>>
>> java.sql.SQLSyntaxErrorException: ORA-00904:
>> "ARCHIVA_ORGANIZATION_ID":
>> invalid identifier
>>
>> java.sql.SQLSyntaxErrorException: ORA-00904:
>> "ARCHIVA_ISSUE_MANAGEMENT_ID":
>> invalid identifier
>>
>> java.sql.SQLSyntaxErrorException: ORA-00904:
>> "ARCHIVA_CIMANAGEMENT_ID":
>> invalid identifier
>>
>>
>>
>> => It seems that the webapp tries to generate a fresh schema.
>>
>> => Anybody know what exactly is going on and how to work around?
>>
>> Marc
>> --
>> View this message in context:
>> http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23612501.html
>> Sent from the archiva-users mailing list archive at Nabble.com.
>>
>
>
>
--
View this message in context: http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23619456.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: Migration 1.1.3 => 1.2 - JDO issues !
Posted by Brett Porter <br...@apache.org>.
You are best to delete the archiva database and rescan to regenerate
it after an upgrade at this point.
Please be aware that there are a few issues with indexing in the 1.2
release that will be resolved in the near future with a 1.2.1 release.
- Brett
On 19/05/2009, at 7:13 PM, Marc Lustig wrote:
>
> We have been running Archiva 1.x for about 13 months now serving now
> about 20
> teams/120 developers. In order to get rid of the tedious error
> messages
> "unable to find project model" in the browse view and to benefit
> from the
> new features and the new layout we tried upgrading to Archiva 1.2 by
> following the instructions located here
> http://archiva.apache.org/docs/1.2/adminguide/webapp.html and here
> http://archiva.apache.org/docs/1.2/adminguide/standalone.html
>
> We are running Archiva in Tomcat6 on jdk1.6.0_07 with Oracle RAC
> database.
>
> After deploying the webapp it is impossible to browse the repositories
> anymore, as we get various errors by JDO-implementation, such as
>
> Error in JDO during get of Database object id
> [xxx:automotive-benutzerverwaltung-actions:1.13-20081121.175349-3]
> of type
> org.apache.maven.archiva.model.ArchivaProjectModel using no fetch-
> group
> ...
> 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: ORA-01758: table must be empty to
> add
> mandatory (NOT NULL) column
>
> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
> add
> mandatory (NOT NULL) column
>
> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
> add
> mandatory (NOT NULL) column
>
> java.sql.SQLSyntaxErrorException: ORA-01758: table must be empty to
> add
> mandatory (NOT NULL) column
>
> java.sql.SQLSyntaxErrorException: ORA-00904:
> "ARCHIVA_ORGANIZATION_ID":
> invalid identifier
>
> java.sql.SQLSyntaxErrorException: ORA-00904:
> "ARCHIVA_ISSUE_MANAGEMENT_ID":
> invalid identifier
>
> java.sql.SQLSyntaxErrorException: ORA-00904:
> "ARCHIVA_CIMANAGEMENT_ID":
> invalid identifier
>
>
>
> => It seems that the webapp tries to generate a fresh schema.
>
> => Anybody know what exactly is going on and how to work around?
>
> Marc
> --
> View this message in context: http://www.nabble.com/Migration-1.1.3-%3D%3E-1.2---JDO-issues-%21-tp23612501p23612501.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>