What Should I Do If an Error Is Reported When the Destination Contains Date Fields During Data Migration to DWS and the Error Message Contains "Text 'xxx' could not be parsed, unparsed text found at index 10"?

Symptom

An exception occurs during incremental synchronization of a DWS table. The error log of jobmanager or taskmanager contains message "Text'xxx'couldnotbeparsed,unparsedtextfoundatindex10".

Figure 1 Error message

Possible Causes

In MySQL-compatible mode, DWS does not automatically convert fields of the date type to fields of the timestamp(0) type. The date and time format "yyyy-MM-dd HH:mm:ss" cannot be inserted at the source.

Solution

• Manually change the date type for the DWS destination table to timestamp.
• Use a DWS database compatible mode that can automatically convert fields of the date type to fields of the timestamp type. For example, you can use the default ORA mode.

  DWS does not allow you to modify the compatibility mode of an existing database. You can only specify the compatibility mode when creating a database.