How to unlock datastage jobs.
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 30
- Joined: Tue Feb 19, 2008 11:02 pm
How to unlock datastage jobs.
Hi All,
I had aborted my job from command prompt which is running for quite a long time...
and when Iam trying reopen the same job....I am getting an error message...
Is there any way we can unlock the particular job either from command prompt or within datastage??
Please advise me how to comeup this issue..
Kind Regards
Srini
I had aborted my job from command prompt which is running for quite a long time...
and when Iam trying reopen the same job....I am getting an error message...
Is there any way we can unlock the particular job either from command prompt or within datastage??
Please advise me how to comeup this issue..
Kind Regards
Srini
Hi,
There are two ways to do it.
1-> Go to director ->Job->Cleanup resources-> logout with your job. This will kill the session or in other word unlock the job.
2->Log Into managers and kill the session of the user in which name the job has benn opened.
If you are using versio 8. Then you have to do it by using dsadmin by using 2nd process.
There are two ways to do it.
1-> Go to director ->Job->Cleanup resources-> logout with your job. This will kill the session or in other word unlock the job.
2->Log Into managers and kill the session of the user in which name the job has benn opened.
If you are using versio 8. Then you have to do it by using dsadmin by using 2nd process.
sanjeev kumar
-
- Premium Member
- Posts: 783
- Joined: Mon Jan 16, 2006 10:17 pm
- Location: Sydney, Australia
the job have locked . search for Unlock
viewtopic.php?t=116648
viewtopic.php?t=116648
Here are the directions we give our developers:
Note that the Administrator id can do this for any id. Useful if the locked job is locked by a developer that is on PTO.
Brad.
In Director, in the Cleanup Resources window:
1. In the Processes screen, select the 'Show All' option
2. Highlight a process with your userid
3. In the Lock screen, select the 'Show by process' option and click Release All button.
4. Click the Logout button for the Process.
Repeat steps 2-4 for each entry with your userid.
Note that the Administrator id can do this for any id. Useful if the locked job is locked by a developer that is on PTO.
Brad.
It is not that I am addicted to coffee, it's just that I need it to survive.
-
- Participant
- Posts: 123
- Joined: Wed May 18, 2005 7:41 am
- Location: USA
If you are not able to see that lock from DS Director, go to DS Administrator, select the project, click on command button, issue command LIST.READU ALL, look for the user and inode for that particular locked process, issue command UNLOCK USER <user number> ALL , or UNLOCK <inode number> ALL. But, you need DS Admin privilege to do this.
The other alternative is to kill that process from unix command line,
ps -ef | grep dscs
or
ps -ef | grep dscs | grep phantom
or
ps -ef | grep dscs | grep slave
get the process id using above command
and issue the below command
kill -9 <pid>
Please check whether you are autorized user to use "kill" command or not
The other alternative is to kill that process from unix command line,
ps -ef | grep dscs
or
ps -ef | grep dscs | grep phantom
or
ps -ef | grep dscs | grep slave
get the process id using above command
and issue the below command
kill -9 <pid>
Please check whether you are autorized user to use "kill" command or not
Regards
VS
VS
-
- Participant
- Posts: 123
- Joined: Wed May 18, 2005 7:41 am
- Location: USA
If you are not able to see that lock from DS Director, go to DS Administrator, select the project, click on command button, issue command LIST.READU ALL, look for the user and inode for that particular locked process, issue command UNLOCK USER <user number> ALL , or UNLOCK <inode number> ALL. But, you need DS Admin privilege to do this.
The other alternative is to kill that process from unix command line,
ps -ef | grep dscs
or
ps -ef | grep dscs | grep phantom
or
ps -ef | grep dscs | grep slave
get the process id using above command
and issue the below command
kill -9 <pid>
Please check whether you are autorized user to use "kill" command or not
The other alternative is to kill that process from unix command line,
ps -ef | grep dscs
or
ps -ef | grep dscs | grep phantom
or
ps -ef | grep dscs | grep slave
get the process id using above command
and issue the below command
kill -9 <pid>
Please check whether you are autorized user to use "kill" command or not
Regards
VS
VS
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Aaaaaaaaaaaaaaarrrrrrrrrrrrrrggggggggghhhhh!!!!!!!!!!!!!!!!
NEVER use kill -9 on DataStage processes.
Particularly when you have no idea that you are seeing all the processes or the parent/child relationships between them.
NEVER use kill -9 on DataStage processes.
Particularly when you have no idea that you are seeing all the processes or the parent/child relationships between them.
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.
NEVER use kill -9 unless you know what you are doing and have the ability to clean up locks and the opportunity to restart DataStagesatish_valavala wrote:...get the process id using above command
and issue the below command
kill -9 <pid>...
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>