Help Center>
Data Replication Service>
FAQs>
Real-Time Synchronization>
Garbled Characters or Synchronization Failure Due to Incompatible Character Sets
Updated on 2023-04-03 GMT+08:00
Garbled Characters or Synchronization Failure Due to Incompatible Character Sets
If the character set of the source database is incompatible with that of the destination database, some data may include garbled characters, data synchronization may be inconsistent, or data may fail to be written into the destination database. In this case, change the character set of the destination database before synchronization.
Parent topic: Real-Time Synchronization
Real-Time Synchronization FAQs
- Can DRS Sync Tables of Different Schemas to the Same Schema?
- Can Online DDL Tools Be Used for Real-time Synchronization?
- Does DRS Support Bidirectional Real-time Synchronization?
- Why Do I Use the SCAN IP Address to Connect to an Oracle RAC Cluster?
- How Do I Check Supplemental Logging of the Source Oracle Database?
- Which Specifications Should I Select for My DRS Task to Synchronize Data to GaussDB(DWS)?
- Suggestions on Synchronizing Data to GaussDB(DWS)
- Character Set Compatibility Between Oracle and GaussDB
- Garbled Characters or Synchronization Failure Due to Incompatible Character Sets
- How Do I Specify the Start Point for DRS Incremental Synchronization?
- What Are Syntax Differences Between MySQL or MariaDB Versions?
- Configuring Remote Connection to a GaussDB Database
- Connection and Port Description for Incremental Synchronization from GaussDB
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.
Chatbotmore
