Datastage Jobs Not Running
Moderators: chulett, rschirm, roy
Datastage Jobs Not Running
Hi,
For the last couple of days we are facing a weird situation which we never experienced before. DS jobs are scheduled using cron utility and unix scripts invoke these DS jobs to run at scheduled time.
But the unix script after processing initial stages(checking the run file etc;) and at the time of invoking the DS jobs, it is failing for no reason.
After some preliminary analysis, we thought of clearing the log information of the jobs and ran the scripts again. Doing so, we could execute the Scripts successfully.
But again today, even after clearing all the old logs of the jobs, the jobs failed for the same reason and we could finish them after re-running those scripts manually.
Do we need to restart the server after clearing the log files?
Or is there any other reason behind these script failures?
Please advise.
Thanks in advance.
Sue
For the last couple of days we are facing a weird situation which we never experienced before. DS jobs are scheduled using cron utility and unix scripts invoke these DS jobs to run at scheduled time.
But the unix script after processing initial stages(checking the run file etc;) and at the time of invoking the DS jobs, it is failing for no reason.
After some preliminary analysis, we thought of clearing the log information of the jobs and ran the scripts again. Doing so, we could execute the Scripts successfully.
But again today, even after clearing all the old logs of the jobs, the jobs failed for the same reason and we could finish them after re-running those scripts manually.
Do we need to restart the server after clearing the log files?
Or is there any other reason behind these script failures?
Please advise.
Thanks in advance.
Sue
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Re: Datastage Jobs Not Running
What was the reason?paranoid wrote:... the jobs failed for the same reason and we could finish them after re-running those scripts manually....
Are ANY events logged either in DataStage logs or in cron (or script) logs?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Re: Datastage Jobs Not Running
Ray,ray.wurlod wrote:What was the reason?paranoid wrote:... the jobs failed for the same reason and we could finish them after re-running those scripts manually....
Are ANY events logged either in DataStage logs or in cron (or script) logs?
In the DS job logs, it says that " Resetting the job". Any ideas?
Thanks for your swift response.
Thanks
Sue
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
Normally, any failure in the execution will be highlighted with a red mark in the log. Do you see any ?
Resetting is one of the feature in the job sequence to ensure correct re-run of previously failed jobs. So they must not matter.
Post any warnings or errors present in the log - especially after initiating your scripts.
Also what were your previous errors for which you cleared your log and reran the jobs successfully ?
Resetting is one of the feature in the job sequence to ensure correct re-run of previously failed jobs. So they must not matter.
Post any warnings or errors present in the log - especially after initiating your scripts.
Also what were your previous errors for which you cleared your log and reran the jobs successfully ?
0% idle can be a cause for jobs to fail due to timeouts or overloaded resources.
But all of this is pure guesswork until you have a nerror message of some type.
But all of this is pure guesswork until you have a nerror message of some type.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
i check the /tmp and it is also 3 percent filled. So i guess it is not an issue.
We are not getting any error status codes in the datastage logs. It is just getting reset by itself. I am wondering what could be the reason?
After 4 AM EST when we try to re-run the scripts manually, they are running fine.It is all happening between 2 - 4 AM EST.
But the weird thing is, the Idle time is still '0' and the jobs are running fine when we run them manaully after 4 AM EST which were failing between 2-4.
Any advise??
Thanks
Sue
We are not getting any error status codes in the datastage logs. It is just getting reset by itself. I am wondering what could be the reason?
After 4 AM EST when we try to re-run the scripts manually, they are running fine.It is all happening between 2 - 4 AM EST.
But the weird thing is, the Idle time is still '0' and the jobs are running fine when we run them manaully after 4 AM EST which were failing between 2-4.
Any advise??
Thanks
Sue
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Premium Member
- Posts: 457
- Joined: Tue Sep 25, 2007 4:05 pm
/tmp is 3% at what time? Did you check it at the peak of DataStage processing? Please rule out the possibility of /tmp getting full when you check it at its high water mark.paranoid wrote:i check the /tmp and it is also 3 percent filled. So i guess it is not an issue.
Vivek Gadwal
Experience is what you get when you didn't get what you wanted
Experience is what you get when you didn't get what you wanted
Hi,
The jobs failed today as well and finally i could find the error code when running manually on the server. It says "Status code = -14 DSJE_TIMEOUT".
When i have gone through this forums with this error message, i have found that this error occurs when the server is overloaded.
Any resolution for this?
Thanks
Sue
The jobs failed today as well and finally i could find the error code when running manually on the server. It says "Status code = -14 DSJE_TIMEOUT".
When i have gone through this forums with this error message, i have found that this error occurs when the server is overloaded.
Any resolution for this?
Thanks
Sue