DSXchange

Check which job is 287?
Go to the director of the job and clear the job log, check whether it allows you to clear it or not, if yes, then re run the job.

Love,
This repeats every week. Done with the clearing and compilation of the job , which was recommended , and the frst step that I do when this error pops up. But it does not seem to be a perm solution. So need to find a reason for it so that can be fixed for good.
Thanks

Deepak,

Why cant you import the job again, so that it will clear all the old entries and create new entries.

I did this last week. Deleted the Job and Reimported it in the project , but this error came up again this week. DO I have to do it again??

Find out who's deleting them. Castigate them.

Well , yes I will for sure. But not sure how to find that out. No one is running anything at that time on the server as well. Grrrrr.... ..

Hi Deepak,

I was facing a similar problem but jus found the reason and solution to it..

The reason is that your datastage application directory has reached 100% of its allotted space..
The solution is you need to first enable "auto purge" feature in Ds administartor for your project.
Second, you need to manually set the option of Auto purge in the jobs that you have created uptil this point sice the auto purge feature will now work ONLy in the new jobs that you create.. And dont forget to clear the logs of all your jobs which have run with warnings and increased the size of log files theru the "immediate purge" option in director.

If DS is completely hung up and is not responding then first ask ur SA to assign half a GB space to the application directory so that DS has the space to execute processes.

Hope this helps...

Thank you..Can be the reason as the Job log is huge. Will Auto purge the log for the particular Job and check out if it works..

In the meantime, a manual purge (up to the last run) would help you to get up and running again.

Yes it did. Thanks.