Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

While restoring the Mysql dump file it throws the following error.

ERROR 1665 (HY000): 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.
Query OK, 0 rows affected (0.00 sec)

The replication configuration is as below.

my.cnf

Replication Configuration:

       server-id    = 33
       max_binlog_size=40M
       log_bin=/MySql_5.5.8/log/my-bin
       log-bin-index=/MySql_5.5.8/log/log/mysql_rpllg/my-bin.index
share|improve this question

2 Answers 2

You most likely need to set it up for mixed format so the server can decide.

binlog-format=MIXED

Statement format does not always work, especially if a statement contains variable such as CURRENT_TIMESTAMP. You can read about this here: https://mariadb.com/kb/en/mariadb/mariadb-documentation/log-files/binary-log/binary-log-formats/ - Clark Vera

share|improve this answer

Try setting this in my.cnf then re-trying

binlog-format=STATEMENT
share|improve this answer
    
I think it should be ROW-based or MIXED. –  quanta Dec 12 '11 at 13:35
1  
I have solved the problem. As the mysql dump files are in the row format Row-based replication is required. To configure row-based replication explicitly, modify the binlog-format parameter in my.cnf and restart MySQL: [mysqld] binlog-format=row / mixed –  Aha Dec 12 '11 at 13:37

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.