KeyLookup Failure! WHY?

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
vimalvik
Premium Member
Premium Member
Posts: 19
Joined: Tue Feb 21, 2006 5:56 am
Location: India

KeyLookup Failure! WHY?

Post by vimalvik »

hi ppl,
my lookup stage failed and as a result my job gets aborted.I then changed the failure mode to CONTINUE and made the job to run.
I wud be pleased to know why the keylookup possibly failed and wat effects will it bring if we run using CONTINUE mode.

Thanks in advance,

cheers,
R.Vimal
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The key lookup failed because the key did not exist on the reference input link. The job aborted because you had set the "lookup failed" rule to FAIL. By setting it to CONTINUE you allow the job to continue to run; any columns mapped from the reference input link will contain NULL (it becomes effectively a left outer join). If that's not what you want draw a reject link from the Lookup stage and set the lookup failed rule accordingly. The reject link can then handle any row for which the key does not exist on 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.
vmcburney
Participant
Posts: 3593
Joined: Thu Jan 23, 2003 5:25 pm
Location: Australia, Melbourne
Contact:

Post by vmcburney »

Once you have set your mode to continue (or reject) be on the lookout in testing for unexpected lookup misses such as comparing a trimmed string to an untrimmed string, or comparing char to varchar, or comparing on a duplicate key.
Post Reply