warnings in the Lookup stage

arunkumar1111 · Post by **arunkumar1111** » Wed Sep 10, 2008 1:55 am

Hi
I'm getting the wraming as mentioned below

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

How to avoid this warning

ray.wurlod · Post by **ray.wurlod** » Wed Sep 10, 2008 2:26 am

Remove duplicates from the reference input, or configure the Lookup stage to permit duplicates.

premupdate · Post by **premupdate** » Wed Sep 10, 2008 5:09 am

Ray,

Am facing the same warning in lookup stage.I dont know how to configure the lookup stage as you have mentioned to configure it.Pls help me to resolve the problem of allowing duplicates in the lookup stage
regards,
prem

ray.wurlod · Post by **ray.wurlod** » Wed Sep 10, 2008 5:54 am

On the Conditions page, where you set the rules for Conditional Lookup and Lookup Failed, there is also a dropdown list of reference input link names. You can choose to allow multiple rows to be returned from one reference input link.

If you want multiple rows to be returned from two reference input links you need two Lookup stages.

premupdate · Post by **premupdate** » Wed Sep 10, 2008 6:20 am

Thanks for the reply.

But am not a premier member.Please let me know the answer in visible format.

ray.wurlod · Post by **ray.wurlod** » Wed Sep 10, 2008 6:45 am

Please purchase premium membership, then my reply will be in "visible format" without me having to do anything at all!

Premium membership is one of the ways that the hosting and bandwidth costs incurred by DSXchange are defrayed. I do not intend to prejudice that funding by establishing a precedent of bypassing it.

OddJob · Post by **OddJob** » Wed Sep 10, 2008 7:45 am

As an alternative to paying for the membership, you could always try reading the manual

Parallel Job Developer's Guide, Look Up stage, details on Lookup Stage Conditions dialog.

chulett · Post by **chulett** » Wed Sep 10, 2008 8:10 am

Perish the thought. Besides, I'm sure that was the first prong of the attack on the problem, people only come here as a last resort when all other avenues have been exhausted... right?

OddJob · Post by **OddJob** » Wed Sep 10, 2008 9:03 am

You poor naive person!

chulett · Post by **chulett** » Wed Sep 10, 2008 9:06 am

dsdevper · Post by **dsdevper** » Wed Sep 10, 2008 9:38 am

Hi Arun....

I recommend you to take the premium membership..Its worth and you will not be dissapointed by the responses...

horserider · Post by **horserider** » Wed Sep 10, 2008 9:58 am

Lookup Source should only have 1 record per lookup key from the transformer. Ideally lookup should only match on 1 row in the lookup source and return that row only.

Fix your source and see there is only 1 row per primary key.

Note: Please get premium membership. I have been a premium member
and tell you what? You won't regret it.

ambasta · Post by **ambasta** » Sat Sep 20, 2008 4:05 am

Use a remove duplicate stage in ur reference link..I t will resolve the issue

abc123 · Post by **abc123** » Tue Sep 30, 2008 9:02 am

Ray, the Multiple Reference Link drop down allows you to set only one reference link as returning multiple rows. Can you set multiple reference links pointing to the same lookup stage to return multiple rows?

ray.wurlod · Post by **ray.wurlod** » Tue Sep 30, 2008 3:39 pm

No.

That would getting into Cartesian product territory. "They" thought that that would be a Bad Thing.

You can use more than one Lookup stage. But you still risk generating a Cartesian product.