ERROR 1598 (HY000): Binary Logging not Possible. Message: Transaction Level READ-COMMITTED in InnoDB
2014-11-03 20:19
1436 查看
Symptoms
On the import of objects to the MySQL database the following message may arise: “ERROR 1598 (HY000) at line 25: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'”.
Cause
The error arises when you try to load the data to the MySQL database. The error arises only if the binary logging option, which is required for the replication, is turned on for the MySQL server.
Solutions
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
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 mysqldutility starting the MySQL server.
原文链接:http://wiki.ispirer.com/sqlways/troubleshooting-guide/mysql/import/binlog_mode_statement
On the import of objects to the MySQL database the following message may arise: “ERROR 1598 (HY000) at line 25: Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'”.
Cause
The error arises when you try to load the data to the MySQL database. The error arises only if the binary logging option, which is required for the replication, is turned on for the MySQL server.
Solutions
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';
mysql> COMMIT;
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 mysqldutility starting the MySQL server.
原文链接:http://wiki.ispirer.com/sqlways/troubleshooting-guide/mysql/import/binlog_mode_statement
相关文章推荐
- Binary Logging not Possible. Message: Transaction Level READ-COMMITTED in InnoDB
- MySql之错误异常--Binary logging not possible. Message: Transaction level 'READ-COMMITTED' in InnoDB is no
- MYSQL:Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'
- Jira的 Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'错误的解决
- MySQL报错【innoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED】
- InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMIT
- Jira的 Transaction level 'READ-COMMITTED' in InnoDB is not safe for binlog mode 'STATEMENT'错误的解决 原创 2
- InnoDB is limited to row-logging when transaction isolation level is READ COMMIT
- not an error (code 0): Could not open the database in read/write mode.的解决办法
- You receive a "Setup Library wbemupgd.dll could not be loaded" error message when you use Add or Remove Programs in Windows Server 2003
- BizTalk - Most possible reason for “is Delimiters are not unique” in EDI transaction
- SQLiteException: not an error (code 0): Could not open the database in read/write mode
- Compiler Error Message: CS0234: The type or namespace name 'BorderDetails' does not exist in the class or namespace 'Infragistics.WebUI.Shared' (are you missing an assembly reference?)
- ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 77, even
- gdb的一个bug Internal error: 【pc 0xxxxxxx】 in read in psymtab, but not in symtab
- mydqldump 备份数单库 然后还原数据的时候报:ERROR 1881 (HY000) at line 52: Operation not allowed when innodb_forced_recovery > 0.
- ERROR 1201 (HY000): Could not initialize master in
- Getting this error message: dbModel read resource does not implement Zend_Db_Adapter_Abstract
- [BTS] Error in Check Transaction: 没有注册类 (异常来自 HRESULT:0x80040154 (REGDB_E_CLASSNOTREG))
- Error message when you try to save a table in SQL Server 2008: "Saving changes is not permitted"