Checking Whether the Source Database Binlog Is Row-Based

Updated on 2022-09-21 GMT+08:00

View PDF

MySQL Migration

**Table 1** Checking whether the source database binlog is row-based
Check Item	Whether the source database binlog is row-based
Description	Check whether the source database binlog is row-based.
Failure Cause and Handling Suggestion	Failure cause: This item cannot be checked because the source database fails to be connected. Handling suggestion: Check whether the source database is connected.
	Failure cause: Insufficient user permissions Handling suggestion: Check whether the database user permissions meet the migration requirements.
	Failure cause: The source database binlog is not row-based. Handling suggestion: If the source database is an on-premises database, perform the following operations to change the binlog format of the source database: Method 1: You can modify the my.cnf or my.ini configuration file and restart the database. binlog_format=row Method 2: Stop all service connections. set global binlog_format='ROW' Modify the my.cnf or my.ini configuration file. binlog_format=row In the ROW format, the log growth rate increases, which may occupy more disk space. NOTE: The MySQL Global binlog_format parameter does not take effect for connected sessions. For details, see How Do I Set Global binlog_format=ROW to Take Effect Immediately? If the source database is an RDS DB instance on the cloud, change the binlog_format value of the source database to ROW. After the change, restart the database for the change to take effect. NOTE: The MySQL Global binlog_format parameter does not take effect for connected sessions. For details, see How Do I Set Global binlog_format=ROW to Take Effect Immediately?
	Failure cause: An internal error occurs. Handling suggestion: Contact Huawei technical support.