Help Center> Cloud Data Migration> FAQs> Troubleshooting> What Should I Do If a CDM Cluster of Version 2.8.6 Fails to Migrate Data from OBS to DLI?
Updated on 2023-06-21 GMT+08:00

What Should I Do If a CDM Cluster of Version 2.8.6 Fails to Migrate Data from OBS to DLI?

Symptom

Two CDM clusters (version 2.6.0 and 2.8.6, respectively) are used to migrate data from OBS to DLI. Configurations of the two migration jobs are the same. The CDM cluster of version 2.6.0 successfully migrates the data, but the CDM cluster of version 2.8.6 fails to migrate the data. The following figure shows log with the error message.

Possible Cause

  1. The error may occur because the field type conversion between the source and destination is abnormal.

  1. Change the field type for the destination table from biginit to string and rerun the job. The job still fails, and the same error is reported.
  2. Enable dirty data and rerun the job. The job still fails, but three pieces of data are successfully migrated to destination table.
  3. After a comparison of the data records that fail to be migrated and those that are successfully migrated, it is suspected that the error is caused by fields of the Boolean type.

Solution

Change the type of the destination fields from Boolean to string and rerun the job. The job is successful. Some Boolean fields at the source have a null value, which results in a migration failure.

In CDM 2.8.6, the cluster verification is stricter. If the data type of the destination is Boolean, the system checks the data type during data insertion. If the data type is not Boolean, an error is reported.

Troubleshooting FAQs

more