Open Space stops or won't start at all

Document ID : KB000029187
Last Modified Date : 14/02/2018
Show Technical Document Details

DESCRIPTION:

When trying to start Open Space it stops few minutes after starting or won't start at all. In the Open Space logs(liferay.xxx-xx-xx.log), the following error will show:

16:04:03,960 ERROR [JDBCExceptionReporter:75] Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.
16:04:03,976 ERROR [MainServlet:198] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.exception.SystemException: com.liferay.portal.kernel.dao.orm.ORMException: org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.exception.SystemException: com.liferay.portal.kernel.dao.orm.ORMException: org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
 at com.liferay.portal.events.StartupAction.run(StartupAction.java:58)

 This is the same error that is shown for another Open Space issue as per TEC617809. However, you can get the same error if the default userid that is used for Open Space connection doesn't have sufficient rights in the database.  You can confirm this by running simple SQL queries with the default userid to get the following error: "Error Code 122  Access denied; you need at least one of the RELOAD privileges for this operation"

 

SOLUTION:

Make sure that the default database userid for Open Space has the following database roles associated in MySQL. (MySQL Studio can be used to check this):   UserAdmin, SecurityAdmin, Dbmanager, DBDesigner, BackupAdmin and Custom.

After ensuring, restart Open Space again. 

Below screen print also shows the same needed roles highlighted.

open_space_roles1.JPG