1) That's such an odd message. It doesn't say columnS, yet provides a whole list of columns. One wonders whether this is a single column name or multiple.
Was there perhaps an existing 'attrep_apply_exceptions' on the target db/schema? Can you delete or rename that and try again? Can you try without having 'attrep_apply_exceptions' activated?
To help you it would be best to share (critical parts) of the exported task json. (feel free to generously trim table lists and transformations).
Anyway, I suspect the warning is just that, a warning which you evaluate once and then ignore going forward as this is not business data as such, just error handling background information.
2) Why do you need 'decimal' data?
According to Microsoft "Decimal and numeric are synonyms and can be used interchangeably." msSQL decimal-and-numeric . For other SQL's there may be a difference in precision handling according to other decimal vs numeric . The Replicate Userguide shows decimal(p,s) source columns to be mapped on numeric(p,s) on target and why not?!
If need be, can you try pre-creating the target table with decimal(p,s) column(s) and use 'truncate' or 'do nothing' in the full-load settings? Does that work for you?
hope this helps,
Hein
