Error in Lookup stage with too many number of references

[vcsasikala]

I'm having a job as below

Reference Datasets (16 numbers)
|
|
Dataset ---> Lookup -----> Transformer--->dataset

I'm getting follwoing error...


692 INFO Tue Feb 16 06:31:14 2010
main_program: APT configuration file: /dsadm/Ascential/DataStage/Configurations/default.apt (...)
693 FATAL Tue Feb 16 06:31:51 2010
ValidValue_Lkup,1: The runLocally() of the operator failed.
694 INFO Tue Feb 16 06:31:51 2010
ValidValue_Lkup,1: Input 0 consumed 4 records.
Input 1 consumed 16 records.
Input 2 consumed 0 records.
Input 3 consumed 0 records.
Input 4 consumed 0 records.

695 FATAL Tue Feb 16 06:31:51 2010
ValidValue_Lkup,0: The runLocally() of the operator failed.
696 INFO Tue Feb 16 06:31:51 2010
ValidValue_Lkup,0: Input 0 consumed 5 records.
Input 1 consumed 16 records.
Input 2 consumed 0 records.
Input 3 consumed 0 records.
Input 4 consumed 0 records.
Input 5 consumed 0 records.
Input 6 consumed 0 records.
Input 7 consumed 0 records.
Input 8 consumed 0 records.
Input 9 consumed 0 records.
Input 10 consumed 0 records.
Input 11 consumed 0 records.
Input 12 consumed 0 records.
Input 13 consumed 0 records.
Input 14 consumed 0 records.
Input 15 consumed 0 records.
Input 16 consumed 0 records.
Input 17 consumed 0 records.

697 INFO Tue Feb 16 06:31:51 2010
ValidValue_Lkup,0: Output 0 produced 4 records.
698 FATAL Tue Feb 16 06:31:51 2010
ValidValue_Lkup,0: Operator terminated abnormally: runLocally did not return APT_StatusOk
699 INFO Tue Feb 16 06:31:51 2010
ValidValue_Lkup,1: Input 5 consumed 0 records.
Input 6 consumed 0 records.
Input 7 consumed 0 records.
Input 8 consumed 0 records.
Input 9 consumed 0 records.
Input 10 consumed 0 records.
Input 11 consumed 0 records.
Input 12 consumed 0 records.
Input 13 consumed 0 records.
Input 14 consumed 0 records.
Input 15 consumed 0 records.
Input 16 consumed 0 records.
Input 17 consumed 0 records.

700 INFO Tue Feb 16 06:31:51 2010
ValidValue_Lkup,1: Output 0 produced 3 records.
701 FATAL Tue Feb 16 06:32:01 2010
ValidValue_Lkup,1: Operator terminated abnormally: runLocally did not return APT_StatusOk
702 FATAL Tue Feb 16 06:32:01 2010
main_program: Step execution finished with status = FAILED.


Please tell me solution

[rohithmuthyala]

Hi,

In the lookup stage, if you select constraints then you can find an option for Lookup failure if that is selected as "FAIL" then if there is no match then the job will fail change it to drop or continue or reject depending on ur need.

[ray.wurlod]

Not "ur". The correct spelling is "your". Ur was a city in ancient Babylon or thereabouts.