Symptom
Replication Flow of load type: "Initial and delta" fails with error:
incompatible partfile metadata: Property replicationTaskID doesn't match existing metadata.
Requested value is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx but existing value is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Please enable the truncate option or delete the target dataset manually if this is the only replication using the target dataset
The same Replication Flow works fine when load type is changed to "Initial only".
Environment
SAP Datasphere
Cause
The cause of this issue is because of an older Replication Flow is being re-used.
Resolution
As stated in SAP Datasphere documentation Configure a Replication Flow:
"For cloud storage provider targets, Truncate must always be set. (If you still try to run a replication flow for an existing target without the Truncate option, you get an error message.) When you start the replication run, the system deletes the object completely (data and structure) and re-creates it based on the source data."
Therefore, make sure that all objects in a Replication Flow where target is a Cloud Storage provider must have Truncate option enabled.
Keywords
replication flow, incomplete partfile, delta, Amazon S3, GoogleBigQuery , KBA , DS-DI-RF , Replication Flows , Problem