Lookup error

smitageorge · Post by **smitageorge** » Thu Mar 30, 2006 5:18 pm

Hi all,

I am having this error message

lkp_group,0: Ignoring duplicate entry at table record 3; no further warnings will be issued for this table

I know that i am getting this error message due to the duplicate entry,but i just want to know is there anyway i can overcome this.

Thanks
smita

vmcburney · Post by **vmcburney** » Thu Mar 30, 2006 5:46 pm

You need to either deduplicate your lookup stream by providing a better SQL select or pushing it through a remove duplicates stage or improve the lookup key fields to add an extra mapping field that will gaurantee your lookup is unique or review the lookup data to see if the source table has duplicates it is not supposed to have.

vsurap · Post by **vsurap** » Thu Mar 30, 2006 6:36 pm

If you are trying to get a Cartesian product then use a Join Stage.
or
You can use the message handler to suppress the warning from the logs, but in my opinion it is not a best practice
or
As vmcburney said, remove duplicates from your Lookup stream

smitageorge · Post by **smitageorge** » Thu Mar 30, 2006 6:53 pm

vsurap wrote:If you are trying to get a Cartesian product then use a Join Stage.
or
You can use the message handler to suppress the warning from the logs, but in my opinion it is not a best practice
or
As vmcburney said, remove duplicates from your Lookup stream

I dont have any duplicates in the lookup stream,but there are duplicates in the source.

Thanks
smita

us1aslam1us · Post by **us1aslam1us** » Thu Mar 30, 2006 6:57 pm

Hi smita i am also having the same problem.

Thanks
sam

kumar_s · Post by **kumar_s** » Thu Mar 30, 2006 10:27 pm

Try to select your link as 'Multiple rows returend from the link' from Lookup stage condtition tab.

ray.wurlod · Post by **ray.wurlod** » Fri Mar 31, 2006 1:00 am

smitageorge wrote:I dont have any duplicates in the lookup stream,but there are duplicates in the source.

Oh, yes you do! Further, it's on the first processing node (number 0) in your configuration file. Otherwise DataStage would not have reported "lkp_group,0: Ignoring duplicate entry at table record 3"

kool78 · Post by **kool78** » Mon Apr 03, 2006 2:58 pm

i had the same problem:

Try to select your link as 'Multiple rows returned from the link' for the reference link in Lookup stage condtition tab which returns multiple rows with same values.

It would solve your problem.

wittyme · Post by **wittyme** » Mon Mar 29, 2010 9:48 am

I have many lookup links... How can I know which link to select.... It is not in log ....

wittyme · Post by **wittyme** » Mon Mar 29, 2010 9:50 am

I have many lookup links... How can I know which link to select.... It is not in log .... And I am getting Ignoring duplicate warning for 5 times..

JSWARBRI · Post by **JSWARBRI** » Mon Mar 29, 2010 10:23 am

wittyme wrote:I have many lookup links... How can I know which link to select.... It is not in log .... And I am getting Ignoring duplicate warning for 5 times..

You can only select one link when choosing the option "Multiple rows returned from link".

If more than one link is producing this warning, you either have to de-duplicate on the problematic links or use one lookup stage per lookup file and select the Multiple Rows option for each.

If only one link is producing this warning, then to identify which link is causing the warning, you can just select this option for the first link in the drop down list and test it. If this doesn't work, move onto the next link and test..... so on and so forth. Long winded I know, but I can't think of another way to identify the specific link.

Hope this helps.
John