rows getting dropped from look up stage

[Hope]

my source is teradata table. my target is also a teradata table. I have to do lookup get the related records where there is key match. My source has 3 rows.and my look up table has 3 rows.
source data
State sourcename Records
MI xxx 100
WI yyy 200
CA zzz 555

LookupData
State sourcename Loaddate
WI xxx 2007-06-07
MI yyy 2005-09-06
CA zzz 2007-06-07

I am joining these two tables using a lookup stage using 2 key columns(State and sourcename).The job gets aborted with an error "Failed a key lookup for record".When there is a key match my job gets aborted. The same logic worked for a different job.This jobs gets aborted.am I missing anything?

[Yuan_Edward]

Did you notice that the first two records of the source don't match the lookup? You can change the action for the Lookup Failure condition if you want the job to contine.

my source is teradata table. my target is also a teradata table. I have to do lookup get the related records where there is key match. My source has 3 rows.and my look up table has 3 rows.
source data
State sourcename Records
MI xxx 100
WI yyy 200
CA zzz 555

LookupData
State sourcename Loaddate
WI xxx 2007-06-07
MI yyy 2005-09-06
CA zzz 2007-06-07

I am joining these two tables using a lookup stage using 2 key columns(State and sourcename).The job gets aborted with an error "Failed a key lookup for record".When there is a key match my job gets aborted. The same logic worked for a different job.This jobs gets aborted.am I missing anything?

[Zhang Bo]

that's because you set constraints in lookup stage if lookup fail,then fail,that's the default option,you can choose others,

[Hope]

I am sorry This is how my data is.
sourcename state load_dt
xxxx MI 2007-06-07
xxxx WI 2007-06-08
xxxx CA 2007-09-07


sourcename state Recordscount
xxxx CA 100
xxxx MI 200
xxxx WI 200

sourcename and state are keys.
does records in the State column need to match order?.

[prashkvrk]

again the look up wont happen because data is not matching for the key "state". However if u remove the constraint look up failure the job wont abort !

[Hope]

If I take the constraint out the job gives me the warning "Field Recordscount from input dataset '0' is NULL. Record dropped." I thought the lookup stage will check for the key match from the source xxxx MI 2007-06-07
and from the reference xxxx MI 200 and
gives me output xxxx MI 2007-06-07 200.