Viewing Abnormal Data
During the synchronization, data may become abnormal due to conflicts, data processing, heterogeneous conversion, and object missing. You can view abnormal data on the Abnormal Records tab to locate the fault.
The following exception data types are supported when the destination database is GaussDB, PostgreSQL, or Oracle:
- Non-null constraint violation
- Abnormal data
- The right part of data truncated
- Unique key conflicts
The following exception data types are supported when the destination database is MySQL:
- Non-null constraint violation
- Overlong data
- Unique key conflicts
- Columns with the same name
- The column already exists.
- Unknown columns
Supported data flow types:
- DDM->Oracle
- MySQL -> GaussDB Distributed
- MySQL -> GaussDB Centralized
- Oracle->TaurusDB
- Oracle->MySQL
- Oracle->GaussDB(DWS)
- Oracle->PostgreSQL
- Oracle -> GaussDB Distributed
- Oracle -> GaussDB Centralized
- GaussDB Centralized - > Oracle
- GaussDB Distributed -> Oracle
- GaussDB Centralized - > MySQL
- GaussDB Distributed -> MySQL
- GaussDB Centralized
- GaussDB Centralized -> GaussDB Distributed
- GaussDB Distributed
- GaussDB Distributed -> GaussDB Centralized
Procedure
- On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
- On the Abnormal Records tab, filter abnormal data, including statements and description, by time range.
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.
For any further questions, feel free to contact us through the chatbot.
Chatbot