- Troubleshooting
- Solutions to Failed Check Items
- Database Parameters
- Checking Whether the Source Database Binlog Is Enabled
- Checking Whether the Source Database Binlog Is Row-Based
- Checking Whether the expire_logs_days Value in the Source Database Is Correct
- Checking Whether the Source and Destination Database Character Sets Are Consistent
- Checking Whether the Source Database server_id Meets the Incremental Migration Requirements
- Checking Whether the Source and Destination Database Table Names Are Consistent in Case Sensitivity
- Checking Whether the Source Database Contains Object Names with Non-ASCII Characters
- Checking Whether the time_zone Values of the Source and Destination Databases Are the Same
- Checking Whether the collation_server Values of the Source and Destination Databases Are the Same
- Checking Whether the SERVER_UUID Values of the Source and Destination Databases Are the Same
- Checking Whether the SERVER_ID Values of the Source and Destination Databases Are Different
- Checking Whether the Source Database Contains Invalid sql_mode Values
- Checking Whether the sql_mode Values of the Source and Destination Databases Are the Same
- Checking Whether the sql_mode Value in the Destination Database Is Not no_engine
- Checking Whether the innodb_strict_mode Values of the Source and Destination Databases Are the Same
- Checking Whether the max_wal_senders Value of the Source Database Is Correctly Configured
- Checking Whether the WAL_LEVEL Value in the Source Database Is Correct
- Checking Whether the MAX_REPLICATION_SLOTS Value in the Source Database Is Correct
- Checking Whether the Source Database Is on Standby
- Checking Whether the log_slave_updates Value in the Source Database Is Correct
- Checking Whether the BLOCK_SIZE Value of the Source Database Is the Same as That of the Destination Database
- Checking Whether the binlog_row_image Value is FULL
- Checking Whether the Transaction Isolation Levels are Consistent
- Checking Whether the lc_monetary Values of the Source and Destination Databases Are the Same
- Checking Whether the Source Database Contains Trigger Names with Non-ASCII Characters
- Checking Whether the Source Database Collections Contain More Than 10 Indexes
- Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Databases
- Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database
- Checking Whether the max_allowed_packet Value of the Destination Database Is too Small
- Checking Whether the Source Database Character Set Is Supported
- Checking Whether the Databases and Tables Exist
- Checking Whether session_replication_role of the Destination Database Is correctly Set
- Checking Whether the MongoDB Instance Type Matches the Migration Mode
- Checking the Physical Standby Database
- Checking the Synchronization Objects
- Checking Whether the Values of group_concat_max_len Are Consistent
- Checking Whether the Character Sets Are Compatible
- Checking Replication Attribute of Primary Key Columns
- Checking Whether the Source and Destination Database Character Sets Are Consistent
- Oracle Account Check in the Source Database
- Whether the Selected Objects Exist in the Destination Database
- Whether the Selected Table Contains Delay Constraints
- Whether the Source Database Tables Contain Primary Keys
- Whether There Are Composite Hash Indexes in the Source Collection
- Whether There Are Composite Hash Shard Keys in the Source Collection
- Whether the Source Table Structure Contains Newline Characters
- Whether There Are Tables Containing Fields of the bytea or text Type in the Synchronization Object
- Whether the max_allowed_packet Value of the Source Database Is Too Small
- block_encryption_mode Consistency Check
- Character Type and Sorting Rule Check in the Destination Database
- Source Encrypted Table Check
- Change History
Checking Whether the Transaction Isolation Levels are Consistent
During MySQL migration, the transaction isolation levels of the source and destination databases must be the same.
Failure Cause
The transaction isolation levels of the source and destination databases are inconsistent.
Handling Suggestion
Change the value of the database isolation level parameter (tx_isolation or transaction_isolation) to ensure that the transaction isolation levels of the source and destination databases are the same.
- MySQL 5.7 and 5.6: tx_isolation
- MySQL 8.0: transaction_isolation
Parent topic: Database Parameters
- Failure Cause
- Handling Suggestion