[Building Sakai] Switching from HSQLDB to MySQL

[Patrick Coleman]

Hi Robert,

Thanks for the info. I found an article like the one you sent just after I
posted and
set it to "MIXED". Everything worked fine. I'm not sure which setting to use
though,
"ROW" or "MIXED"?

I'm not using replication at the moment so I may just turn it off. But if I
decide to use
it which setting would you recommend?

Thanks.

Pat.


Robert Cohen wrote:
> 
> Hmm, you should be able to get rid of that error by changing your 
> logging options as described here.
> http://www.ispirer.com/wiki/sqlways/troubleshooting-guide/mysql/import/binlog_mode_statement
> 
> If you not using mysql replication, easiest way is to just turn logging
> off.
> All it does is chew up disk space for no gain.
> 
> But I'm surprised that the issue is arising. I would have expected some 
> of the bigger production sites to be using mysql replication and so this 
> would be a known issue.
> 
> 
> 
> On 30/04/2010 2:19 AM, Patrick Coleman wrote:
>> I'm having the same problem. I can start up the HSQLDB database but when
>> I
>> switch to
>> MySQL it doesn't work. I have the sakai.properties file Anthony Whyte
>> suggested in place but I get the following error. It repeats many times.
>>
>>
>> 2010-04-29 12:11:58,815  WARN main
>> org.sakaiproject.db.impl.BasicSqlService
>> - Sql.dbWrite(): error code: 1598 sql:  CREATE UNIQUE INDEX
>> SAKAI_LOCKS_INDEX ON SAKAI_LOCKS ( TABLE_NAME(64), RECORD_ID(128) )
>> binds:
>> java.sql.SQLException: Binary logging not possible. Message: Transaction
>> level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
>>          at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)
>>          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)
>>
>>
>> and
>>
>> 2010-04-29 12:12:05,742  WARN main
>> org.sakaiproject.springframework.orm.hibernate.AddableSessionFactoryBean
>> -
>> Unsuccessful schema statement: alter table ASN_AP_ITEM_T add index
>> FK514CEE15935EEE07 (ID), add constraint FK514CEE15935EEE07 foreign key
>> (ID)
>> references ASN_SUP_ITEM_T (ID)
>> java.sql.SQLException: Binary logging not possible. Message: Transaction
>> level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Matthew Sharrer wrote:
>>    
>>> I've built Sakai, and I can get the demo to work running off of memory
>>> with
>>> HSQLDB.
>>>
>>> This is my environment:
>>> java version "1.5.0_22"
>>> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
>>> Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode, sharing)
>>>
>>> Apache Tomcat 5.5.29
>>>
>>> Maven version: 2.0.8
>>> Java version: 1.5.0_22
>>> OS name: "linux" version: "2.6.18-164.el5" arch: "i386" Family: "unix"
>>>
>>> I've also set all the needed environment variables.
>>>
>>> The builds went alright, and like I said, I could login to Sakai when I
>>> was
>>> running off of memory.
>>>
>>> I attempted to switch to MySQL and I'm having no luck.  I'm using
>>> version
>>> 5.0.77.  I added a group and user for mysql, and set up environment
>>> variables.  I was able to start up mysql, and I created the sakai
>>> database
>>> with the default character set utf8. I then typed the following:
>>> grant all on sakai.* to sakaiuser@'localhost' identified by
>>> 'sakaipassword';
>>> grant all on sakai.* to sakaiuser@'127.0.0.1' identified by
>>> 'sakaipassword';
>>> flush privileges;
>>>
>>> I've installed the mysql JDBC driver.
>>>
>>> I created a my.cnf file in /etc:
>>> [mysqld]
>>> default-storage-engine=InnoDB
>>> Innodb_data_home_dir=/usr/local/mysql/data
>>> Innotdb_data_file_path=ibdata1:10M:autoextend
>>> Innodb_flush_log_at_trx_commit=1
>>>
>>> I edited teh sakai.properties file in $CATALINA_HOME/sakai:
>>> username at javax.sql.BaseDataSource=sakaiuser
>>> password at javax.sql.BaseDataSource=sakaipassword
>>>
>>> And I commented out the HSQLDB settings while uncommenting the mysql
>>> settings.
>>>
>>> I don't know what else to do.  I feel like I followed the configuration
>>> instructions, but perhaps I'm missing something.
>>>
>>> If anyone can provide assistance, I'd greatly appreciate it.  I can post
>>> logs, but I didn't want to post too much information at once.
>>>
>>> _______________________________________________
>>> sakai-dev mailing list
>>> sakai-dev at collab.sakaiproject.org
>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>>>
>>> TO UNSUBSCRIBE: send email to
>>> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
>>> "unsubscribe"
>>>
>>>      
>>    
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> 
> 

-- 
View this message in context: http://old.nabble.com/-Building-Sakai---Switching-from-HSQLDB-to-MySQL-tp28390631p28410691.html
Sent from the Sakai - Development mailing list archive at Nabble.com.