Hi,
We have a simple job
Row Generator ===> XFM with two output links ===> Difference Stage====>Peek Stage
We gete the follwing two warnings:
diff: When checking operator: Dropping component "diff_key" because of a prior component with the same name.
diff: When checking operator: Dropping component "diff_val" because of a prior component with the same name.
I checked the developer's job and the values of both links going into the Difference Stage from the XFM stage are hard coded:
Link2:
diff_key 1
diff_val "Link 2"
lnk2_ind "2"
Link3:
diff_key 1
diff_val "Link 3"
lnk3_ind "3"
They are using the diff_key as the Difference Keys and for Difference Values:
All non-Key Columns are Valiues = False
Value=diff_val
Thanks - - John
Dropping Component warning on the Difference Stage
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
-
- Premium Member
- Posts: 306
- Joined: Wed Jun 21, 2006 11:41 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
DataStage is telling you that it can't transfer two identically named columns to the output of the stage. You could rename - or make copies of - the columns on one of the input links if you need both in the output.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
In such a case, I think the best you can do to remove the warning is to introduce a new column (eg: diff_val_new) in the before link that has the same data as diff_val and pass it to the output. The same resolution will hold true for any other column on which the warning is seen.
The problem with the above approach is that there will be an overhead of including new columns on which the warnings are seen, something which is not a best practice![Smile :)](./images/smilies/icon_smile.gif)
The problem with the above approach is that there will be an overhead of including new columns on which the warnings are seen, something which is not a best practice
![Smile :)](./images/smilies/icon_smile.gif)