Samigo is broken for students in oracle
Activity
Matthew Jones April 19, 2016 at 5:38 PMEdited
This issue was introduced by SAM-1200. Since https://sakaiproject.atlassian.net/browse/SAM-1200#icft=SAM-1200 is now merged to 11, this will also need to go into 11. I don't think https://sakaiproject.atlassian.net/browse/SAM-2472#icft=SAM-2472 is relevant.
Neal Caidin April 19, 2016 at 5:08 PM
I removed the 11 status flag for merging, if this only affects Sakai 12. If that changes and the decision is to merge https://sakaiproject.atlassian.net/browse/SAM-1200#icft=SAM-1200 and https://sakaiproject.atlassian.net/browse/SAM-2472#icft=SAM-2472 , please feel free to set the status flag and we will qa test.
Matthew Jones March 16, 2016 at 10:30 AMEdited
@Laura Gekeler Yeah, this only affects 12, the Marist server is running Sakai 11.It's related to the recent fix on https://sakaiproject.atlassian.net/browse/SAM-1200#icft=SAM-1200 to increase some column lengths (like description and feedback) and the bug is also Oracle only
Laura Gekeler March 16, 2016 at 10:27 AM
we are testing on http://qa01-sakai.marist.edu:8080/portal/ today and find samigo accessible to students.
Details
Details
Priority
Blocker
Click the Samigo tool link as student. Samigo fails. Stacktrace:
Stacktrace: at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:476) caused by: org.springframework.dao.InvalidDataAccessResourceUsageException: could not execute query; SQL [select distinct assessment0_.ASSESSMENTGRADINGID as col_0_0_, publisheda1_.ID as col_1_0_, publisheda1_.TITLE as col_2_0_, assessment0_.AGENTID as col_3_0_, assessment0_.SUBMITTEDDATE as col_4_0_, assessment0_.ISLATE as col_5_0_, assessment0_.FORGRADE as col_6_0_, assessment0_.TOTALAUTOSCORE as col_7_0_, assessment0_.TOTALOVERRIDESCORE as col_8_0_, assessment0_.FINALSCORE as col_9_0_, assessment0_.COMMENTS as col_10_0_, assessment0_.STATUS as col_11_0_, assessment0_.GRADEDBY as col_12_0_, assessment0_.GRADEDDATE as col_13_0_, assessment0_.ATTEMPTDATE as col_14_0_, assessment0_.TIMEELAPSED as col_15_0_ from SAM_ASSESSMENTGRADING_T assessment0_, SAM_PUBLISHEDASSESSMENT_T publisheda1_, SAM_AUTHZDATA_T authorizat2_ where assessment0_.PUBLISHEDASSESSMENTID=publisheda1_.ID and assessment0_.FORGRADE=? and assessment0_.AGENTID=? and (authorizat2_.AGENTID=? or authorizat2_.AGENTID in (? , ?)) and authorizat2_.FUNCTIONID=? and authorizat2_.QUALIFIERID=publisheda1_.ID and (publisheda1_.STATUS=? or publisheda1_.STATUS=?) order by publisheda1_.ID DESC, assessment0_.SUBMITTEDDATE DESC]; nested exception is org.hibernate.exception.SQLGrammarException: could not execute query at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:414) caused by: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) caused by: java.sql.SQLSyntaxErrorException: ORA-00932: inconsistent datatypes: expected - got CLOB at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1017)