You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Gunther Van den Bosch (JIRA)" <ji...@codehaus.org> on 2008/03/05 14:04:28 UTC
[jira] Updated: (MRM-657) 'ORA-00910: specified length too long for
its datatype' Error when clicking on searched artifact.
[ http://jira.codehaus.org/browse/MRM-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gunther Van den Bosch updated MRM-657:
--------------------------------------
Attachment: package-oracle.orm
> 'ORA-00910: specified length too long for its datatype' Error when clicking on searched artifact.
> -------------------------------------------------------------------------------------------------
>
> Key: MRM-657
> URL: http://jira.codehaus.org/browse/MRM-657
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Oracle 10g 10.2.0.3.0 on Sun Solaris Sparc 64
> Reporter: Mick Knutson
> Fix For: 1.1
>
> Attachments: package-oracle.orm
>
>
> When I do a search for an artifact, then I get the results, I then get this error:
> javax.jdo.JDODataStoreException: An exception was thrown while adding/validating class(es) : ORA-00910: specified length too long for its datatype
> java.sql.SQLException: ORA-00910: specified length too long for its datatype
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:158)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
> at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:113)
> at oracle.jdbc.driver.T4CStatement.execute_for_rows(T4CStatement.java:703)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1196)
> at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1804)
> at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264)
> at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:614)
> at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:570)
> at org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:297)
> at org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:341)
> at org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDBMSManager.java:3052)
> at org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3313)
> at org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2554)
> at org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2406)
> at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:821)
> at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:835)
> at org.jpox.AbstractPersistenceManager.newObjectIdInstance(AbstractPersistenceManager.java:2377)
> at org.apache.maven.archiva.database.jdo.JdoAccess.getObjectById(JdoAccess.java:429)
> at org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.getProjectModel(JdoProjectModelDAO.java:74)
> at org.apache.maven.archiva.database.browsing.DefaultRepositoryBrowsing.getProjectModel(DefaultRepositoryBrowsing.java:281)
> at org.apache.maven.archiva.database.browsing.DefaultRepositoryBrowsing.selectVersion(DefaultRepositoryBrowsing.java:127)
> at org.apache.maven.archiva.web.action.ShowArtifactAction.artifact(ShowArtifactAction.java:105)
> Now this does not come up like with continuum (at start up):
> http://jira.codehaus.org/browse/CONTINUUM-1622
> So Archiva runs, but not when I try to search.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira