archiva-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gunther Van den Bosch (JIRA)" <>
Subject [jira] Commented: (MRM-657) 'ORA-00910: specified length too long for its datatype' Error when clicking on searched artifact.
Date Wed, 05 Mar 2008 13:04:28 GMT


Gunther Van den Bosch commented on MRM-657:

This could be solved by adapting the JDO mapping for Oracle. Oracle supports only VARCHAR
types with a maximum length of 4000. The standard implementation of archiva sometimes uses
fields which are longer.
I have attached the package-oracle.orm file which should be included in the archiva-model-1.0.1.jar
next to the package.jdo

Using the Oracle mapping can be activated by setting the mapping property in the application.xml
for the Jdofactory component

I hope this helps

> 'ORA-00910: specified length too long for its datatype' Error when clicking on searched
> -------------------------------------------------------------------------------------------------
>                 Key: MRM-657
>                 URL:
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Oracle 10g 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(
> 	at oracle.jdbc.driver.T4CTTIoer.processError(
> 	at oracle.jdbc.driver.T4CTTIoer.processError(
> 	at oracle.jdbc.driver.T4C8Oall.receive(
> 	at oracle.jdbc.driver.T4CStatement.doOall8(
> 	at oracle.jdbc.driver.T4CStatement.execute_for_rows(
> 	at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(
> 	at oracle.jdbc.driver.OracleStatement.execute(
> 	at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(
> 	at
> 	at
> 	at
> 	at
> 	at$ClassAdder.performTablesValidation(
> 	at$ClassAdder.addClassTablesAndValidate(
> 	at$
> 	at$MgmtTransaction.execute(
> 	at
> 	at
> 	at org.jpox.AbstractPersistenceManager.newObjectIdInstance(
> 	at org.apache.maven.archiva.database.jdo.JdoAccess.getObjectById(
> 	at org.apache.maven.archiva.database.jdo.JdoProjectModelDAO.getProjectModel(
> 	at org.apache.maven.archiva.database.browsing.DefaultRepositoryBrowsing.getProjectModel(
> 	at org.apache.maven.archiva.database.browsing.DefaultRepositoryBrowsing.selectVersion(
> 	at org.apache.maven.archiva.web.action.ShowArtifactAction.artifact(
> Now this does not come up like with continuum (at start up):
> 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:
For more information on JIRA, see:


View raw message