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
Sparse lookup gives more number of records
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 248
- Joined: Fri Jul 30, 2010 9:04 am
Sparse lookup gives more number of records
Regards,
Kenny
Kenny
Re: Sparse lookup gives more number of records
We should use where clause in sparse lookup.
ex: Time_key = ORCHESTRATE.Timekey
Thanks
arun
ex: Time_key = ORCHESTRATE.Timekey
Thanks
arun
arun
-
- Participant
- Posts: 248
- Joined: Fri Jul 30, 2010 9:04 am
-
- Participant
- Posts: 248
- Joined: Fri Jul 30, 2010 9:04 am
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
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
Regards,
Kenny
Kenny
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,
Regarding your original question, it sounds as if there are duplicates in your reference data.
Regards,
- james wiles
All generalizations are false, including this one - Mark Twain.
All generalizations are false, including this one - Mark Twain.