Why do I get 'Binary logging not possible.' on my MySQL server?

mysql linux virtualbox toad

11,908

According to ERROR 1598 (HY000): Binary Logging not Possible. Message: Transaction Level READ-COMMITTED in InnoDB is not Safe for Binlog Mode STATEMENT:

There are several solutions for the issue:
You need to change the binlog mode to either ROW or MIXED in order to run the load of the data into the database
mysql> SET GLOBAL binlog_format = 'ROW';
If you are not planning to use your MySQL server for the replication consider turning the binary logging off by removing the option --log-bin from the command options for the mysqld utility starting the MySQL server.

11,908

Author by

Steven

I'm an interaction designer with focus on usability and front-end design. 10+ years of PHP programming and 6+ years of WordPress experience. "Hardcore" programming is not my strong side as I tend to focus on usability, design and consultancy.

Updated on June 09, 2022

Comments

Steven almost 2 years

When I started up my MySQL server today and try to do some changes using Toad for Mysql, I get this message:

MySQL Database Error

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

I have no idea what this means. I'm running Mysql on VirtualBox with Ubuntu 11.x.

Has anyone run into this problem before?
Steven about 12 years

I did that last bit. I had turned it ON because I was trying to debug some issues.
Seaux about 11 years

setting the binlog_format did not resolve my problem. any other advice as to what it could be?
Seaux about 11 years

actually, the SET GLOBAL just didn't work. i had to set 'binlog_format' in /etc/my.cnf and restart mysql.