continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Lustig ...@marclustig.com>
Subject Re: Continuum 1.3 not working with Oracle 9g
Date Tue, 22 Sep 2009 07:32:37 GMT

Hello Brett, you were guessing right. "size" is a keyword in Oracle. So my
original guess was right that it's not a JPOX, but an application
(Continuum) issue.

I will see if I can fix that today.


PS: For some strange reason, nabble affirms that my posting was not accepted
by the mailing list and hence it rejects to display any replies :-( 
So I have to copy the reply from my inbox to the nabble UI.
Btw, I am definately subscribed with the same Email-address. Weired...

-----Urspr√ľngliche Nachricht-----
Von: Brett Porter [mailto:brett@porterclan.net] Im Auftrag von Brett Porter
Gesendet: Dienstag, 22. September 2009 03:50
An: users@continuum.apache.org
Betreff: Re: Continuum 1.3 not working with Oracle 9g



On 22/09/2009, at 6:07 AM, Marc Lustig wrote:

>
> I started Continuum 1.3.4 with an empty database, and the same JPOX  
> error
> appeared.
>
> How can I verify that JPOX automatically detected the database and  
> set the
> dialect accordingly?
>

You need to edit WEB-INF/classes/log4j.xml and change the JPOX.RDBMS  
log to "debug", then search for "DatabaseAdapter" in the logs on  
startup.

I'm going to guess it is correctly identifying Oracle but that we need  
to figure out what is wrong with that statement. If you can confirm by  
running the SELECT statement - if you change "AS size" to "AS foo"  
will it work? We may need to change the column name under Oracle.

- Brett




Marc Lustig wrote:
> 
> This is the exception you get:
> 
>  javax.jdo.JDODataStoreException: Error executing JDOQL query "SELECT
> THIS.PROJECT_GROUP_ID_OID AS projectGroupId,THIS.PROJECTSTATE AS
> projectState,COUNT(THIS.PROJECTSTATE) AS size FROM PROJECT THIS GROUP BY
> THIS.PROJECT_GROUP_ID_OID,THIS.PROJECTSTATE" : ORA-00923: FROM keyword not
> found where expected
> .
> 	at
> org.jpox.store.rdbms.query.JDOQLQuery.performExecute(JDOQLQuery.java:636)
> 	at org.jpox.store.query.Query.executeWithMap(Query.java:959)
> 	at org.jpox.store.query.Query.executeWithArray(Query.java:932)
> 	at org.jpox.store.query.Query.execute(Query.java:855)
> 	at
> org.apache.continuum.dao.ProjectDaoImpl.getProjectsSummary(ProjectDaoImpl.java:332)
> 	at
> org.apache.maven.continuum.DefaultContinuum.getProjectsSummaryByGroups(DefaultContinuum.java:746)
> 	at
> org.apache.maven.continuum.web.action.GroupSummaryAction.execute(GroupSummaryAction.java:56)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:597)
> 	at
> com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:404)
> 	at
> com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:267)
> 	at
> com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:229)
> 	at
> org.apache.struts2.interceptor.MessageStoreInterceptor.intercept(MessageStoreInterceptor.java:195)
> 
> ...
> estedThrowablesStackTrace:
> java.sql.SQLSyntaxErrorException: ORA-00923: FROM keyword not found where
> expected
> 
> 	at
> oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:91)
> 	at
> oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
> 	at
> oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
> 	at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
> 	at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
> 	at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
> 	at
> oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
> 	at
> oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:791)
> 	at
> oracle.jdbc.driver.T4CPreparedStatement.executeMaybeDescribe(T4CPreparedStatement.java:866)
> 	at
> oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1186)
> 	at
> oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
> 	at
> oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3431)
> 	at
> oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1491)
> 	at
> org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:93)
> 	at
> org.jpox.store.rdbms.RDBMSManager.executeStatementQuery(RDBMSManager.java:643)
> 	at
> org.jpox.store.rdbms.query.JDOQLQuery.performExecute(JDOQLQuery.java:594)
> 	at org.jpox.store.query.Query.executeWithMap(Query.java:959)
> 	at org.jpox.store.query.Query.executeWithArray(Query.java:932)
> 	at org.jpox.store.query.Query.execute(Query.java:855)
> 	at
> org.apache.continuum.dao.ProjectDaoImpl.getProjectsSummary(ProjectDaoImpl.java:332)
> 	at
> org.apache.maven.continuum.DefaultContinuum.getProjectsSummaryByGroups(DefaultContinuum.java:746)
> 	at
> org.apache.maven.continuum.web.action.GroupSummaryAction.execute(GroupSummaryAction.java:56)
> ...
> 

-- 
View this message in context: http://www.nabble.com/Continuum-1.3-not-working-with-Oracle-9g-tp25530339p25530606.html
Sent from the Continuum - Users mailing list archive at Nabble.com.


Mime
View raw message