Page 1 of 1

How to unlock datastage jobs.

Posted: Tue Jul 29, 2008 3:45 am
by srinivas143
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

Posted: Tue Jul 29, 2008 4:19 am
by sanjumsm
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.

Posted: Tue Jul 29, 2008 5:53 am
by rajngt
How the job was killed using command prompt? Using unix Kill command?

Posted: Tue Jul 29, 2008 5:58 am
by keshav0307
the job have locked . search for Unlock
viewtopic.php?t=116648

Posted: Tue Jul 29, 2008 9:42 pm
by bcarlson
Here are the directions we give our developers:
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. :wink:

Brad.

Posted: Tue Jul 29, 2008 10:07 pm
by satish_valavala
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

Posted: Tue Jul 29, 2008 10:08 pm
by satish_valavala
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

Posted: Tue Jul 29, 2008 11:32 pm
by ray.wurlod
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.

Posted: Wed Jul 30, 2008 2:22 am
by ArndW
satish_valavala wrote:...get the process id using above command
and issue the below command
kill -9 <pid>...
NEVER use kill -9 unless you know what you are doing and have the ability to clean up locks and the opportunity to restart DataStage