Please I need help ASAP. I cannot stop a server job that is running. I have had the DBA kill the oracle session, and I have submitted a stop from the DataStage Director, but nothing is stopping it. Our server administrator even re-booted our DataStage server, and it's still running. How do you stop something like this?????
thanks in advance
Mona
Help needed to kill a "rogue" server job
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 26
- Joined: Fri Feb 27, 2004 7:23 am
- Location: WI, USA
There's a big difference between a job that says it is running versus one that actually is. If you've rebooted the DataStage server than your job, she ain't running. It is just a flag and it says it is 'Running' because it never heard back that the job ended.
Use the 'Clear Status File' command from Director to clear this condition.
Use the 'Clear Status File' command from Director to clear this condition.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 26
- Joined: Fri Feb 27, 2004 7:23 am
- Location: WI, USA
Try recompiling the job, if you rebooted there can't be any runaway threads. You have a "software" lock, basically just a status in a table is invalid. Recompile and that should fix it.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
-
- Participant
- Posts: 26
- Joined: Fri Feb 27, 2004 7:23 am
- Location: WI, USA
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What you see in the Director is not the actual status of the job. Rather, it's the most recent entry that the job has been able to write to its status file, which is what Director reads.
If the job has aborted suddenly (or been killed), then it never gets the opportunity to update its status records, so the Director appears to show it as still running.
This is why re-compiling, or clearing the status file, has the apparent effect of "stopping" the job. It's not really stopping it; rather it's updating the record that indicates that the job is running.
If the job has aborted suddenly (or been killed), then it never gets the opportunity to update its status records, so the Director appears to show it as still running.
This is why re-compiling, or clearing the status file, has the apparent effect of "stopping" the job. It's not really stopping it; rather it's updating the record that indicates that the job is running.
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.