Sparse Lookup - Dropping component because of prior componen

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
syedmuhammedmehdi
Participant
Posts: 43
Joined: Wed Feb 12, 2014 12:34 pm
Location: Hyderabad, India

Sparse Lookup - Dropping component because of prior componen

Post by syedmuhammedmehdi »

I'm doing a sparse lookup on oracle table on Key but when I'm running job I'm getting error as Dropping component Key because of prior component with same name Key. Actually the column for which it is saying it is dropping due to same name is lookup key only and usually we get this error for other joins when non joining columns are with same name but here for key joining column it is giving this error. Could you please advise, thanks.
SyedMuhammadMehdi
asorrell
Posts: 1707
Joined: Fri Apr 04, 2003 2:00 pm
Location: Colleyville, Texas

Post by asorrell »

Basically the problem is that the sparse lookup is returning the key to the output link, and the source link is also sending the key to the output link. So it complains about it.

Easiest solution is to use custom SQL in the sparse lookup that doesn't return the key column value. Even though it is on the list of columns (because it was sent to the sparse lookup), it doesn't have to be returned as a value.
Andy Sorrell
Certified DataStage Consultant
IBM Analytics Champion 2009 - 2020
Post Reply