Differences
This shows you the differences between two versions of the page.
|
knowledge-base:database-migration:setup-and-troubleshooting:mysql:error-1598 [2009/10/07 10:20] |
knowledge-base:database-migration:setup-and-troubleshooting:mysql:error-1598 [2023/10/26 14:12] (current) uliana.philippova created |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | \\ | ||
| + | [[https://www.ispirer.com|Ispirer Website]] | ||
| + | [[https://www.ispirer.com/products/mysql-migration|Ispirer Capabilities: MySQL Migration]] | ||
| + | [[https://www.ispirer.com/download/download-demo|Free Trial]] | ||
| + | ====== ERROR 1598 (HY000): Binary Logging Not Possible. Message: Transaction Level READ-COMMITTED in InnoDB is Not Safe for Binlog Mode STATEMENT ====== | ||
| + | **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 | ||
| + | |||
| + | 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 <html><i>--log-bin</i></html> from the command options for the //mysqld// utility starting the MySQL server. | ||