Updated on 2025-02-17 GMT+08:00

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

  1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
  2. On the Abnormal Records tab, filter abnormal data, including statements and description, by time range.