Help Center>
Data Replication Service>
Troubleshooting>
Failure Cases>
Real-Time Synchronization from MySQL to GaussDB(DWS)
Updated on 2023-06-28 GMT+08:00
Real-Time Synchronization from MySQL to GaussDB(DWS)
- Full Synchronization Error: Table *** not found in database
- Full Synchronization Error: column 'database_table' of relation *** does not exist
- Full Synchronization Error: value too long for type character varying
- Full Synchronization Error: int1 has not implemented
- Full Synchronization Error: column name 'tid' conflicts with a system column name
- Full Synchronization Error: date/time field value out of range
- Full or Incremental Synchronization Error: service LOGMANAGER failed
- Full or Incremental Synchronization Error: service CAPTURER failed
- Full or Incremental Synchronization Error: ERROR: pooler
- Full or Incremental Phase Error: service *** failed, cause by: Unable to connect to DBMS: ***
- Full or Incremental Phase Error: The binlog fetch connection may be interrupted
- Incremental Synchronization Error: dn_***: column *** contains null values
- Incremental Synchronization Error: source has more columns than target
- Incremental Synchronization Errors: Connection to *.*.*.98:8000 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections
- Incremental Synchronization Error: Table *** not found in target database
- Incremental Synchronization Error: in a read-only transaction
- Incremental Synchronization Error: relation *** does not exist
- Incremental Synchronization Error: *** doesn't in the target table
- Incremental Synchronization Error: syntax error at or near
- Incremental Synchronization Error: schema *** does not exist
- Incremental Synchronization Error: Check whether dws supports the DDL
- Incremental Synchronization Error: PL/pgSQL function *** line *** at SQL statement
Parent topic: Failure Cases
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
