Scneario of read and write hashed file concurrently
Posted: Wed Jun 01, 2011 4:44 pm
hello,
We are revisiting the usage of hashed files in our jobs. Some of the jobs use hashed files for lookup and these hashed files are created using a job which runs at a scheduled time every day. We have observed that few of the jobs are not using hashed files and instead use direct table lookups.
We don't plan to get these 3-4 new hashed files (each hashed file may have up to 300,000 records) created in the existing hashed file creation job as that job takes 25 minutes to create 5 files. In this case, we are planning to let the new hashed files be created just before the lookup job runs and use them. We have multiple instance jobs which run at different times of the day and could possibly refer the same hashed file.
In this case. will there be any job error / issue if one job got kicked off and starts reading the hashed file (previously created) while another job is overwrittng the hashed file?
Your inputs are appreciated.
We are revisiting the usage of hashed files in our jobs. Some of the jobs use hashed files for lookup and these hashed files are created using a job which runs at a scheduled time every day. We have observed that few of the jobs are not using hashed files and instead use direct table lookups.
We don't plan to get these 3-4 new hashed files (each hashed file may have up to 300,000 records) created in the existing hashed file creation job as that job takes 25 minutes to create 5 files. In this case, we are planning to let the new hashed files be created just before the lookup job runs and use them. We have multiple instance jobs which run at different times of the day and could possibly refer the same hashed file.
In this case. will there be any job error / issue if one job got kicked off and starts reading the hashed file (previously created) while another job is overwrittng the hashed file?
Your inputs are appreciated.