Job Corruption problem
Posted: Wed Jan 11, 2006 10:19 am
We have a problem in production..
All of a sudden one of the DS jobs is not running properly.
It has a oracle -> Hash file stage, followed by lookups and the sequential file and finally update/inser on oracle stage. Its a fairly big job.
The job was hanging initially while creating the hash file. We then cleared
existsing hash file on Unix, rename the hash file in the job and finally now hash gets created but the job is not progressing further. Its just stand still for 12 hrs, normally it finished in 3-4 hrs.
Director shows o rows, designer shows blue and no oracle sessions at all.
We tried all the following
1. Recompiled the job
2. Renamed the job
3. Saved a copy, renamed and compiled.
4.Deleted the job from the server and imported again
5. Imported on a different name
Nothing worked!!
When we loginto the project thru director , we frequently get these error message
Cannot open executable job file RT_CONFIG1219
We cleared the jobs logs, status file and resources through unix and director. Also imported the job in a different name, again the new job hangs.
Rest other jobs are running fine.
Totally clueless...
Anyidea??
All of a sudden one of the DS jobs is not running properly.
It has a oracle -> Hash file stage, followed by lookups and the sequential file and finally update/inser on oracle stage. Its a fairly big job.
The job was hanging initially while creating the hash file. We then cleared
existsing hash file on Unix, rename the hash file in the job and finally now hash gets created but the job is not progressing further. Its just stand still for 12 hrs, normally it finished in 3-4 hrs.
Director shows o rows, designer shows blue and no oracle sessions at all.
We tried all the following
1. Recompiled the job
2. Renamed the job
3. Saved a copy, renamed and compiled.
4.Deleted the job from the server and imported again
5. Imported on a different name
Nothing worked!!
When we loginto the project thru director , we frequently get these error message
Cannot open executable job file RT_CONFIG1219
We cleared the jobs logs, status file and resources through unix and director. Also imported the job in a different name, again the new job hangs.
Rest other jobs are running fine.
Totally clueless...
Anyidea??