Warning on Datastage parallel job on duplicate entry

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
mayura
Participant
Posts: 40
Joined: Fri Aug 01, 2008 5:58 am
Location: Mumbai

Warning on Datastage parallel job on duplicate entry

Post by mayura »

Recieved warning on ignoring duplicate entry at table ...no further warnings will be issued for this table.

Solution:
Made the one of the referance link in lookup stage for selecting multiple rows from link and warning has gone.

Query: Is there any impact of data flowed from link after selecting multiple rows from link or it is just removed warning and no impact on data which has been loaded from the link to target. :roll:
Mayura
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Yes, you'll get one row on the output for every row returned from the reference input.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mayura
Participant
Posts: 40
Joined: Fri Aug 01, 2008 5:58 am
Location: Mumbai

Post by mayura »

So did this change is good sign to be implement or there is any other way to remove above warning.

As I dont want to return multiple rows for single line. or suggest
Mayura
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

If you want one row being turned into multiple rows after the lookup, then the setting you used allows that to happen. If you do not want that, then either craft your lookup so it only returns a single row so no warning is thrown, or live with the warning as it throws away all of the 'extra' rows from the lookup.
-craig

"You can never have too many knives" -- Logan Nine Fingers
mukejee
Participant
Posts: 37
Joined: Thu Dec 11, 2008 5:38 am
Location: India,Bangalore

Post by mukejee »

go to look up stage > stage prperties > Input >giv partition and then click on uniq. Then u will not get the warning...
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Remove Duplicates on the reference input link.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mayura
Participant
Posts: 40
Joined: Fri Aug 01, 2008 5:58 am
Location: Mumbai

Post by mayura »

I did checked table data there were no duplicates hence using remove duplicate stage warning remains the same.

Any other resolultiion please...
Mayura
jerome_rajan
Premium Member
Premium Member
Posts: 376
Joined: Sat Jan 07, 2012 12:25 pm
Location: Piscataway

Post by jerome_rajan »

On what basis did you check if there are duplicates? Is it not possible that there are multiple records for the same value of your lookup keys?
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn

Life is really simple, but we insist on making it complicated.
mayura
Participant
Posts: 40
Joined: Fri Aug 01, 2008 5:58 am
Location: Mumbai

Post by mayura »

I did used remove duplicate stage for the records on which warning coming out.

I used the same key column based on what data has been extracted or lookedup in lookup stage.

Is there any possiblity of line break or any junk character into file.

May be i will check data set data one more time..
But please suggestion is open.
Mayura
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Shouldn't be all that hard to confirm. As noted, the error tells you that based on your lookup key that it found more than one match in the lookup data. So please, check your 'data set' again.
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply