Sparse lookup gives more number of records

[kennyapril]

I am using sparce lookup with oracle enterprise stage, it gives more
number of records than expected.I tried a sample job with stream 20 records
and reference 200 records and the output I get is 2000 records.
The two key columns have been selected as keys in the input of lookup.

please suggest if any changes are required.




Thanks

[akonda]

We should use where clause in sparse lookup.

ex: Time_key = ORCHESTRATE.Timekey




Thanks
arun

[kennyapril]

Thanks

Do we need to use that in the query of reference table for the key column from DB stage?

[akonda]

correct.

[kennyapril]

In the simple job which I said the stream has 100 records and the reference has 10000 records

I changed the query in the reference using where per_id=orchestrate.per_id

and when I run the job I receive an error

main_program: (aptoci.C:456). Message: ORA-00904: "ORCHESTRATE"."PER_ID": invalid identifier


please suggest

[jwiles]

The error is pretty clear: There is no column named PER_ID in your orchestrate datastream (i.e. your main input link to the lookup stage).

Regarding your original question, it sounds as if there are duplicates in your reference data.

Regards,