[Deploying Sakai] starting lessonbuilder 1.4.x

[Charles Hedrick]

I suggest that you look at the file components/sakai-lessonbuildertool-components/WEB-INF/classes/mysql/simplepage.sql

Unfortunately hibernate will not create indices for mysql. Thus we put all indexing into a file, which gets taken every time the system starts.

It uses a generic Sakai facility that reads an SQL file at startup. If the first line produces an error, the rest of the file is ignored. Otherwise it takes the whole file, and there's a problem if any lines don't work. The problem is that we don't in general know what state your system is in, so you may get an unexpected error here. My suggestion is to do the lines by hand. As long as all the indices have been created you should be fine. Once everything is there, the file will abort at the first line, and there will be no problem, because that's expected.


On Jan 5, 2012, at 3:16 AM, Anders Nordkvist wrote:

> Hi,
>  
> I’ve just upgraded Lessonbuilder from tag 1.2.2 to 1.4.x. We use Sakai 2.7.x here in Skövde, Sweden.
> It works fine to build and deploy Sakai but when I start it up and watch the tomcat log I get the following two database warnings:
>  
> 2012-01-05 08:37:23,486  WARN main org.sakaiproject.db.impl.BasicSqlService - Sql.dbWrite(): error code: 1061 sql:  create index lesson_builder_log_index on lesson_builder_log(userId,itemId, studentPageId) binds:
> com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Duplicate key name 'lesson_builder_log_index'
>         at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936)
>         at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
>         at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
>         at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
>         at com.mysql.jdbc.Connection.execSQL(Connection.java:3256)
>  
> 2012-01-05 08:37:23,488  WARN main org.sakaiproject.lessonbuildertool.service.SimplePageToolService - Unable to DDL Lesson Builder
> java.lang.RuntimeException: SqlService.dbWrite failure
>         at org.sakaiproject.db.impl.BasicSqlService.dbWrite(BasicSqlService.java:1282)
>         at org.sakaiproject.db.impl.BasicSqlService.dbWrite(BasicSqlService.java:1095)
>         at org.sakaiproject.db.impl.BasicSqlService.ddl(BasicSqlService.java:2075)
>         at org.sakaiproject.lessonbuildertool.service.SimplePageToolService.init(SimplePageToolService.java:89)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> I think its nothing to worry about beacause it’s a complain that he cant create some kind of log table that already exists!
> What do you think? Is it safe to run in a production environment?
>  
> My second question is: will everything in old pages created in 1.2.2 still work after upgrade?
>  
>  
> Regards
> Anders Nordkvist
> System administrator
> University Of Skövde
> Sweden
>  
>  
>  
> _______________________________________________
> production mailing list
> production at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/production
> 
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20120118/967c7c44/attachment.html