Rangelkup failure message "Updatable lookup requires so

Nsg · Post by **Nsg** » Fri Apr 06, 2012 9:21 am

Hi all,

I have a sequence where there are 2 jobs -
1) Extract
2) Range lookup and craete output file.

The sequence when triggered, runs both the jobs successfully and creates the file.

However when the sequence is called from other sequence, the Range lookup job fails with the error message of "Updatable lookup requires sorted keys."

The job is doing range lookup on the master link.

This problem seems very strange as the parameters passed as identicle.

Please let me know if you know how to handle this situation.

Thanks,
Nsg

jwiles · Post by **jwiles** » Fri Apr 06, 2012 9:28 am

Your job parameters may be identical, but is the environment? Check the values of other environment variables, such as APT_NO_SORT_INSERTION. Maybe they are set by the master sequence.

Regards,

Nsg · Post by **Nsg** » Fri Apr 06, 2012 11:46 am

Yes, you are correct. I had APT_NO_PART_INSERTION and APT_NO_SORT_INSERTION in master sequencer and setting them to false, makes the job run just fine. Thanks for the help.

The thing I did not know was that these Env_Variables get passed to all the jobs even when not specifically passed.

Is it a good practice to have explicit sorts and partitions in jobs and have APT_NO_PART_INSERTION and APT_NO_SORT_INSERTION set to true in the sequencer.

Thanks,
nsg

chulett · Post by **chulett** » Fri Apr 06, 2012 1:33 pm

They're not 'passed' but but they are inherited because they are all running under one environment - the one established by the Sequence. And if your jobs rely on certain values being set, don't assume they are already set in the environment, explicity set them in your jobs. That way a Master Sequence can't come along and override them, all accidental like.

jwiles · Post by **jwiles** » Fri Apr 06, 2012 1:57 pm

Explicitly defining sorts and partitioning in your job provides you more control over the job's operation and performance, but can be abused if you don't have a good understanding of where and why sorting and partitioning should be done (and NOT done). I prefer it also because it provides a visual indication of where I am performing sorts and partitioning in the jobs I create.

Auto sorts and partitions generally guarantee a correctly-processing job in the great majority of cases, but do not guarantee optimal performance.

Regards,

Nsg · Post by **Nsg** » Wed Apr 11, 2012 2:34 pm

Thanks you all for the explaination and helping resolve the issue.

- nsg