Page 1 of 1

DS Compile Error

Posted: Mon Nov 24, 2008 11:49 am
by abhishekachrekar
Hi,

These days we are facing space issues on our development server.
Our parallel jobs are frequently aborting with the following message.

Join.Right_ecdi_account_Sort,3: Failure during execution of operator logic.
Join.Left_aibm17_Sort,1: Fatal Error: mmap failed: Not enough space

When we try to compile the job (after it aborts) we get the following compilation error.

Cannot get exclusive access to executable file for job b_jb_NBR_CreateECDIExtract_AIBM01

We are able to open the job, make a copy of the job but we cannot compile it, delete it or rename it.

After few days we are able to delete the job. But till then we keep creating duplicate jobs.

Can any one help in solving this issue? i.e. how to compile/delete such jobs?

Thanks and Regards,
Abhishek

Re: DS Compile Error

Posted: Mon Nov 24, 2008 2:02 pm
by jseclen
Hi abhishekachrekar

PLease check this link

viewtopic.php?t=121475&highlight=mmap

in this post appear a similar case, but using sort stage, i think that the solution will work in your case.

Posted: Tue Nov 25, 2008 7:26 am
by abhishekachrekar
Thanks jseclen,

I thought it was due to space issue on scratch disk.

In one of the job I have used a sort stage with no limit on memory usage (i.e. I havent set "Restrict Memory Usage" property).
But this job has also aborted before.

These job aborts randomly. It will abort now but on the second attempt it completes successfully.

Sometimes after the abort if we try to compile the job it throws the error given in my earlier post.
The job is not locked. I cannot see it in the "cleanup resources"
I can open the job in designer but cannot rename/delete/compile it.

Is there any method to release this kind of job?

Posted: Tue Nov 25, 2008 10:00 am
by jseclen
Hi abhishekachrekar,

PLease search in the forum about DS.TOOLS, the job maybe need to unlock by command, once have that problem.

I hope this help.

Posted: Tue Nov 25, 2008 1:57 pm
by ray.wurlod
Not setting the Restrict Memory Usage property does not give unlimited memory; it gives 20MB per node (unless this has been overridden by setting a different value in the environment variable APT_TSORT_STRESS_BLOCKSIZE.