Hi,
I have a simple scenario as below.
one source sequential file. (20042 rows)
one oracle table as referance. (4067814 rows)
i have used lookup stage to lookup the data.
the lookup stage property is auto partitioned.
client is complaining that the target data is not correct for few records.
what i feel is the size problem of lookup stage.
Please let me know whether the lookup can handle these many rows as referance.
Regards,
Raghu Ghantasala.
Reg: Reference data size for lookup stage.
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Number of records doesn't matter if your jobs is running without error.
lookup will partion reference link data to entire unless "inserting partitioning automatically" is disabled. If data is not correct for few records, i would first check data and try to find a link between wrong values.
Seems to me like Data/Design problem rather than limitation of Datastage / hardware.
lookup will partion reference link data to entire unless "inserting partitioning automatically" is disabled. If data is not correct for few records, i would first check data and try to find a link between wrong values.
Seems to me like Data/Design problem rather than limitation of Datastage / hardware.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
The environment variable is called APT_NO_PART_INSERTION, if its value is true then datastage won't insert any partitioning scheme automatically.
Was there any warning in the logs. are there duplicates in reference link? too many things to ask.
Saying every thing is correct except output means nothing is correct unless you identify the problem.
Was there any warning in the logs. are there duplicates in reference link? too many things to ask.
Saying every thing is correct except output means nothing is correct unless you identify the problem.
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
Hi Priyadarshan,
Please see below explanasion on two queries asked by you.
1) I have checked the job parameters in designer and Environment varibles in the Data stage Administrator, it is confirmed that the we have not used APT_NO_PART_INSERTION variable. Now the job is in production.
2) There are no duplicate records in the Referance, But there is duplication in Source itself.
Please let me know if this information is enough to analyse.
Regards,
Raghu Ghantasala.
Please see below explanasion on two queries asked by you.
1) I have checked the job parameters in designer and Environment varibles in the Data stage Administrator, it is confirmed that the we have not used APT_NO_PART_INSERTION variable. Now the job is in production.
2) There are no duplicate records in the Referance, But there is duplication in Source itself.
Please let me know if this information is enough to analyse.
Regards,
Raghu Ghantasala.
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI