Release Notes
Announcements
row_format in the source database table cannot be FIXED.lower_case_table_names variable in both the source and target databases must be the same.max_allowed_packet parameter of the target database must be set to 1 GB or above.connect_timeout variable of the source database must be above 10.row_format parameter in the source databaserow_format in a database table is FIXED, an error will be reported when the storage length of each row of the table exceeds the limit. Therefore, you need to change the value of row_format to DYNAMIC so that the storage length of each row varies by the content length.row_format to DYNAMIC.alter table table_name row_format = DYNAMIC;
show table status like 'table_name'\\G;
mysql> show table status like 'table_name'\\G;*************************** 1. row ***************************Name: table_nameEngine: InnoDBVersion: 10Row_format: DynamicRows: 5......1 row in set (0.00 sec)
lower_case_table_names have the same value in source and target databaseslower_case_table_names sets the letter case sensitivity in MySQL. It has the following valid values:
Windows and macOS environments are case-insensitive, but Linux environments are case-sensitive. To ensure the compatibility between different operating systems, you need to use the same letter case sensitivity rule.0: The name of a stored table is in the specified letter case and is case-sensitive during comparison.1: The name of a stored table is in lowercase on the disk and is case-insensitive during comparison.2: The name of a stored table is in the specified letter case and is in lowercase during comparison.lower_case_table_names in the source and target databases.show variables like '%lower_case_table_names%';
my.cnf configuration file of the source database as follows:my.cnf configuration file is /etc/my.cnf, subject to the actual conditions.lower_case_table_names = 1
[$Mysql_Dir]/bin/mysqladmin -u root -p shutdown[$Mysql_Dir]/bin/safe_mysqld &
show variables like '%lower_case_table_names%';
mysql> show variables like '%lower_case_table_names%';+------------------------+-------+| Variable_name | Value |+------------------------+-------+| lower_case_table_names | 1 |+------------------------+-------+1 row in set (0.00 sec)
max_allowed_packet parameter in the target databasemax_allowed_packet is the maximum size of a packet that can be transferred. If its value is too large, more memory will be used, causing packet losses and the inability to capture the SQL statements of large exception event packets. If its value is too small, program errors may occur, causing backup failures and frequent sending/receiving of network packets, which compromises the system performance.max_allowed_packet parameter.set global max_allowed_packet = 4*1024*1024;
show global variables like '%max_allowed_packet%';
mysql> show global variables like '%max_allowed_packet%';+------------------------+---------+| Variable_name | Value |+------------------------+---------+| max_allowed_packet | 4194304 |+------------------------+---------+1 row in set (0.00 sec)
connect_timeout variable in the source databaseconnect_timeout is the database connection timeout, and a connection request will be denied if the connection duration is greater than the value of connect_timeout. If the value of connect_timeout is too small, the database will be frequently disconnected, which will impact the database processing efficiency. Therefore, we recommend that you set a value greater than 10 for this parameter.connect_timeout parameter.set global connect_timeout = 10;
show global variables like '%connect_timeout%';
mysql> show global variables like '%connect_timeout%';+------------------------+---------+| Variable_name | Value |+------------------------+---------+| connect_timeout | 10 |+------------------------+---------+1 row in set (0.00 sec)
フィードバック