Help Center/
Data Replication Service/
Troubleshooting/
Solutions to Failed Check Items/
Database Parameters
Updated on 2024-11-30 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 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 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 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 Specified Replication Slot Exists in the Source Database
- Checking Whether the MongoDB Instance Type Matches the Migration Mode
- Checking the Physical Standby Database
- Checking Whether the Case Sensitivity of the Destination Database Is Configured
- Checking Whether CDC is Enabled for Tables in the Source Database
- Checking Whether the CDC Retention Period in the Source Database Is Long Enough
- Checking Whether the Source and Destination Databases Have Different Computer Names
- Checking Whether the Length of the Source Database Name Exceeds 64
- Synchronization Object Name Check
- Checking Whether the Source Database Contains Disabled Clustered Indexes
- Checking Whether the Source Database Is Empty
- Checking Whether the Source Database Uses the Full Recovery Model
- Checking the Synchronization Objects
- Checking Whether the Source Database Tables Contain Data Types Not Supported for Migration
- Checking Whether the SQL Server Agent of the Source Database Is Enabled
- Checking Whether the Values of group_concat_max_len Are Consistent
- Checking Whether the Table Structures of the Source Database Are Consistent
- Checking Whether the Character Sets Are Compatible
- Whether There Are XA Transactions That Have Not Been Submitted for a Long Time in the Source Database
- Whether the Selected Objects Exist in the Destination Database
- Destination Database Same Name Check
- Whether the Destination Database User (Schema) and Table Exist
- Whether the Maximum Number of Indexed Columns Has Been Reached
- Checking the Length of the Index Column in the Source Database
- Whether the Table Structures (Including Primary Key Indexes and the Number of Columns) of the Source Oracle Database and Destination Database Middleware Are Aligned
- Whether Synchronization Objects Exist in the Destination Database
- Whether the Source Database Contains Encrypted Objects
- Checking Whether the Source Database Contains Unsupported Table Field Types
- Checking Replication Attribute of Primary Key Columns
- Whether There Are Tables Containing Fields of the longtext or longblob Type in the Synchronization Object
- Checking Database Mapping Objects
- Whether the Source Database Is the Standby Database of a GaussDB(for MySQL) Instance
- Checking Whether Type Names Mapped to the Destination Database Are Valid
- Checking Whether the Source and Destination Database Character Sets Are Consistent
- Checking Whether Data Replication Is Enabled for the Source Database
- Checking Whether the Maximum Sequence Number of the Source Database is Less Than That of the Destination Database
- Checking Whether Interval Partitioned Tables Are Included in the Source Database
- Oracle Account Check in the Source Database
- Checking the Number of DNs in the Source Database
- Whether the Selected Objects Exist in the Destination Database
- Whether There Are Foreign Keys Containing Unsupported Reference Operations in the Source Database
- Whether the Selected Table Contains Delay Constraints
- Whether the Source Database Tables Contain Primary Keys
- Whether Foreign Keys Are Disabled or Tables to Be Synchronized Have Foreign Keys in the Destination Database
- 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
- Checking Whether the Source Table Structure Contains Virtual Columns
- Whether the max_allowed_packet Value of the Source Database Is Too Small
- Whether the Supplemental Log Level in the Source Database Is Correct
- Whether Kafka Topics Have Been Created
- Whether the Source Database Kernel Encoding Supports Data Replication
- block_encryption_mode Consistency Check
- Character Type and Sorting Rule Check in the Destination Database
- Column Name Check in the Source Database
- Whether the Destination Schemas and Table Objects Are Consistent
- Source Encrypted Table Check
- Checking Whether the Source Table Replication Attribute Is Correct
- Partition Table Check on the Source Database
- Checking Whether the Source Database Contains Unsupported Generated Columns
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.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
