DSXchange

Posted: **Tue Sep 27, 2011 4:50 am**

samyamkrishna wrote:
ray.wurlod wrote:And the error message ID ? ...
There is no error message id in the warning.

or where will i find it?

Thanks,
Samyam

Double click to view the Detail of the log event.

Posted: **Tue Sep 27, 2011 8:32 am**

patelamit009 wrote:Hi All,

I was also facing the similar kind of error message in one of my job development in transformer stage as below.

Transformer_113: When checking operator: On output data set 0: Dropping component "keyChange" because of a prior component with the same name.

I tried all options that were suggested in the thread and i wasnt successful. Finaly, i realised the problem was due to RCP enabled in the job level. After unchecking it, i get rid of the error.

But, any one could help me out to understand how RCP related to this error ?

Thanks in advance.

RCP will propagate all columns present in any of the input links downstream - may they be explicitly displayed in the job design or not. This is helpful for jobs where You are working with dynamic input, but as You just discovered, it is very confusing if You are not. Your column is present in more than one of your inputs even though You can't see it in the transformer.

Posted: **Tue Nov 24, 2015 5:41 pm**

I unchecked the RCP at transformation level. The problem is resolved. But I do not understand the relation between the problem and solution.

DSXchange

When checking operator: Dropping component

I also faced the same issue.