Help Center/Data Replication Service/Troubleshooting/Troubleshooting/Failure Cases/Real-Time Migration and Synchronization from MySQL to MySQL
Updated on 2025-07-21 GMT+08:00
Real-Time Migration and Synchronization from MySQL to MySQL
- Full Phase Error: Table *** doesn't exist
- Full Phase Error: The background process is unavailable
- Full Phase Error: Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.
- Full Phase Error: Error writing file *** (errno: 28 - No space left on device)
- Full Phase Error: The MySQL server is running with the --super-read-only option so it cannot execute this statement
- Full Phase Error: The table *** is full
- Full Phase Error: Unknown column *** in 'field list'
- Full Phase Error: Lock wait timeout exceeded; try restarting transaction
- Full Phase Error: Java heap space
- Full Phase Error: Table *** already exists
- Full Phase Error: temp table: *** not exist
- Full Phase Error: failed to create new session
- Full Phase Error: load table: *** failed
- Full Phase Error: extract table structure failed!
- Full Phase Error: read table=*** failed
- Full Phase Error: CANNOT UPDATE USER WITH NULL PASSWORD
- Full Phase Error: Access denied for user *** to database ***
- Full Phase Error: The MySQL server is running with the --super-read-only option so it cannot execute this statement
- Full Phase Error: Temporary file write failure.
- Full Phase Error: Incorrect prefix key; the used key part isn't a string, the used length is longer than the key part, or the storage engine doesn't support unique prefix keys
- Full Phase Error: Unknown database ***
- Full Phase Error: Access denied; you need (at least one of) the SUPER privilege(s) for this operation
- Full Phase Error: retry structures failed events and Table *** doesn't exist
- Full Phase Error: shard table=*** failed
- Full Phase Error: error when split table shard occur!
- Full Phase Error: Column name 'AUTO_PK_ROW_ID' is reserved.
- Full Phase Error: transfer account failed, can not find password from src DB
- Full Phase Error: Failed to add the foreign key constraint '***' to system tables
- Full Phase Error: Too many keys specified; max 64 keys allowed
- Full Phase Error: Unknown collation: 'utf8mb4_0900_ai_ci'
- Full Phase Error: exist some xa transactions for long times, may lack some data for this Job!.
- Full Phase Error: Invalid GIS data provided to function st_geometryfromtext'
- Full or Incremental Phase Error: Access denied for user ***
- Full or Incremental Phase Error: binlog is not existed
- Full or Incremental Phase Error: database log download failed
- Full or Incremental Phase Error: Can not read response from server
- Full or Incremental Phase Error: Communications link failure
- Full or Incremental Phase Error: EOF Packet received, master disconnected
- Full or Incremental Phase Error: Extract db create sql failed
- Full or Incremental Phase Error: load database structure failed in source database
- Full or Incremental Phase Error: load table: *** failed
- Full or Incremental Phase Error: Reached end of input stream
- Full or Incremental Phase Error: Read timed out
- Full or Incremental Phase Error: The background process is unavailable
- Full or Incremental Phase Error: Duplicate entry *** for key 'PRIMARY'
- Full or Incremental Phase Error: cause by: Index: ***, Size: ***
- Full or Incremental Phase Error: The offset and file name between src and parser is inconsistency
- Full or Incremental Phase Error: core process is not healthy or crashed
- Full or Incremental Phase Error: table info of table `***` from metadata miss
- Full or Incremental Phase Error: binlog parse fail, data dictionary may be not complete!
- Full or Incremental Phase Error: table *** record field size for insert/delete dml
- 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
- Full or Incremental Phase Error: Received error packet: errno - 1047, solstate - HY000 errmsg =Unknown command
- Incremental Phase Error: not equals to target db column count
- Incremental Phase Error: The MySQL server is running with the --super-read-only option
- Incremental Phase Error: you need (at least one of) the SUPER privilege(s) for this operation
- Incremental Phase Error: Can't DROP ***; check that column/key exists
- Incremental Phase Error: Can't find file: *** (errno: 2 - No such file or directory)
- Incremental Phase Error: Data truncation: Data too long for column
- Incremental Phase Error: Failed to read file header from
- Incremental Phase Error: Lock wait timeout exceeded
- Incremental Phase Error: Must seek before attempting to read next event
- Incremental Phase Error: Table *** already exists
- Incremental Phase Error: Table *** doesn't exist
- Incremental Phase Error: Table *** not found in database
- Incremental Phase Error: source has more columns than target
- Incremental Phase Error: Unknown storage engine
- Incremental Phase Error: Unknown table
- Incremental Phase Error: You have an error in your SQL syntax
- Incremental Phase Error: not illegal for mariaDb gtid position
- Incremental Phase Error: without PK execute failed
- Incremental Phase Error: Deadlock found when trying to get lock
- Incremental Phase Error: current serverUUID not equals to this session
- Incremental Phase Error: Slave has more GTIDs than the master has, using the master's SERVER_UUID.
- Incremental Phase Error: Operation not allowed when innodb_force_recovery > 0
- Incremental Phase Error: filter data in config condition filter error
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.
The system is busy. Please try again later.
