If the bin-log (binary logging) is enabled in the MySQL server, then the schema export utility fails to create EMS specific schemas in database, while altering tables.

If the bin-log (binary logging) is enabled in the MySQL server, then the schema export utility fails to create EMS specific schemas in database, while altering tables.

book

Article ID: KB0086144

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
Description:

The following error happens in the schema export utility during altering tables, when the MySQL server is started from the console as “”mysqld –console –log-bin=c:\mysql.log”, i.e. bin-logging is enabled:

SEVERE: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'

When the EMS server is started after this, the EMS server reports the following error and fails to start:

2009-11-23 14:50:39.127 ERROR: Failed to lock store '$sys.failsafe' [ERRSTR = org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update ]
2009-11-23 14:50:39.127 FATAL: Exception in startup, exiting.

Environment:

All H/W and OS.
TIBCO Enterprise Message Service 5.x
MySQL server database

Symptoms:

The schema export utility fails and the EMS server fails to start.

Cause:

bin-logging is not supported in MySQL server when it is used with EMS 5.x for database based stores.

Resolution:

Disable bin-logging in the MySQL server.

Issue/Introduction

If the bin-log (binary logging) is enabled in the MySQL server, then the schema export utility fails to create EMS specific schemas in database, while altering tables.