Update data activity fails and uploaded column order shifts in Campaign

The Update data activity in a Campaign workflow can fail when uploaded column values shift unexpectedly during bulk loading. In this case, the workflow failed because a small number of records contained a special control character in one field, which broke the CSV row structure and moved values into the wrong columns. As a result, the load_datetime timestamp value was written into the SISOA2 column and rejected as too long. Correct the affected source records and restart the workflow to restore normal processing.

Description description

Environment

Issue/Symptoms

ODB-240000 ODBC error: String ‘2022-05-31 08:45:23.000Z’ is too long and would be truncated…

WDB-200001 SQL statement ‘COPY INTO wkf…’ could not be executed.

Cause

The COPY INTO Snowflake operation failed because 2 records out of approximately 25 million in the dataset contained a special control character (STX / \x02) in the device_use_language_code field. This character conflicted with the CSV record delimiter used during bulk loading, caused the row to split incorrectly, and shifted the uploaded columns. As a result, the load_datetime timestamp value 2022-05-31 08:45:23.000Z was loaded into the SISOA2 column, which is defined as VARCHAR(2), and the load failed because the value was too long.

Resolution resolution

To resolve this issue, follow these steps:

Related reading