Help Center/
Data Replication Service/
Troubleshooting/
Solutions to Failed Check Items/
Database Parameters
Updated on 2022-09-21 GMT+08:00
Database Parameters
- Checking Whether the Source Database Binlog Is Enabled
- Checking Whether the Source Database Binlog Is Row-Based
- Checking Whether the Binlog Retention Period Is Set on the Source Database
- 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 GTID Is Enabled
- Checking Whether the Source Database Contains Object Names with Non-ASCII Characters
- Checking Whether the Source and Destination Database TIME_ZONE Values Are Consistent
- 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_SUBSTITUTION
- 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 of the Source Database Is Correctly Configured
- 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 the Source Database Collections Contain TTL Indexes
- Checking Whether log_bin_trust_function_creators Is Set to On in Both the Source and Destination Databases
- Checking Whether GTID Is Enabled for the Source Database
- Checking Whether GTID Is Enabled for the Destination Database
- Checking Whether log_bin_trust_function_creators Is Set to On in the Destination Database
- Checking Whether the Values in the Source Oracle Database Are Out of the Ranges of the MySQL Database
- Checking Whether the max_allowed_packet Value of the Destination Database Is too Small
- Checking Whether the Source Database User Has the Permission to Parse Logs
- Checking Whether the ExpireLogsDays Value Is 0
- Checking Whether the Source Database Character Set Is Supported
- Checking Whether the Length Table and Field Names Is Not Supported
- Checking Whether the Databases and Tables Exist
- Checking Whether the Supplemental Log Level of the Source Database Meets Requirements
- Checking Whether the Length of the Source Database Object Names Exceeds the Limit
- Checking Whether session_replication_role of the Destination Database Is correctly Set
- Checking the Database Compatibility Type
- Checking Whether the Collation of the Destination Database Is Correct
- Checking Whether the Source Database Has the Permission to Parse OGG Logs
- Checking Whether the Index Name Is Supported
- Checking Whether Tables Structures Are Consistent
- Checking Whether Existing Data Meets the Constraints
- Checking the Additional Column of the Destination Database
- Checking Whether Implicit Primary Key Check Is Enabled for the Primary and Standby Databases
- Checking Whether the Source Table Replication Attribute Is Correct
- Checking Whether the Source Database Is on Standby
- Checking Whether the Specified Replication Slot Exists in the Source Database
- Checking Whether the MongoDB Instance Type Matches the Migration Mode
- Checking the Physical Standby Database
Parent topic: Solutions to Failed Check Items
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
