Job is been accessed by another user

antojj · Post by **antojj** » Mon Dec 19, 2005 11:09 pm

Hi All,

I am getting the following error when trying to access a Job.

Problem Desc :
I have created a Job "Testjob" and been using since 3 days. I have been designing various transformations and able to work.

When i tried to access today, I am not able to access the Job.
Instead, I am getting the following error message :
"Job TestJob is been accessed by another user".

Can anyone suggest me what is the problem and what went wrong.
As for as my knowledge, No other user is accessing the Job.

Thanks,

kcshankar · Post by **kcshankar** » Tue Dec 20, 2005 12:40 am

Hi,
To know whats happening....
View the job status of "Testjob" in the DataStage Director.

regards
kcs

Andal · Post by **Andal** » Tue Dec 20, 2005 1:10 am

May be you could have closed the designer , when it hangs by clicking "End Now". You can relese the job by doing the "clean up resources" from the director.

loveojha2 · Post by **loveojha2** » Tue Dec 20, 2005 1:17 am

You can use DS.TOOLS from the DS Administrator for releasing the Locks.

trokosz · Post by **trokosz** » Tue Dec 20, 2005 11:29 am

The unlock suggestions are good but just to close the loop you may in addition have phantoms left out there.....even removing locks may still give you the error of exclusive so look for phatoms....

ps -ef | grep phan

kill -9 each phantom

ml · Post by ml » Tue Dec 20, 2005 11:41 am

If this is on Windows plataform,

ps -ef | grep phan
kill -9 each phantom

won't help.

Antojj, you should talk with your DS administrator and if you have admin rights you should be able to close the sesion from Director/Cleanup Resources or Admin/commands/DS.TOOLS; but you need to be carfully because you can kill some other things.

Use the forum search utility to find more detail on how to unlock a job.

good luck,

ak77 · Post by **ak77** » Tue Dec 20, 2005 12:17 pm

Hi -

I did use cleanup resources
I did use kill -9
i also tried using DS.TOOLS but dont know how far I did it right
But still some of my jobs and the table definition are locked

I didn't find any Phanton on these jobs

What else can I do?

Kishan

ArndW · Post by **ArndW** » Tue Dec 20, 2005 12:57 pm

ak77,

if you used kill -9 then you are guaranteed to leave locks on jobs and other objects open. Even experienced people have trouble locating those locks on busy systems using LIST.READU or the client cleanup tools. Your best bet for the future is to ensure that the deadlock daemon is up and running, so the longest you will have to wait is the default 15 minutes (which you can decrease). Avoid doing a kill -9 at all costs.

ak77 · Post by **ak77** » Thu Dec 22, 2005 12:43 am

Hi Arnd,

If the jobs get locked, the table definition linked with that job also gets locked??

I read before that kill -9 should be avoided but my system analyst did that when I asked her about a dead lock waiting for resource problem

I will try to avoid to this

Thanks again

Kishan

ArndW · Post by **ArndW** » Thu Dec 22, 2005 2:55 am

Jobs will get and hold certain locks; but I don't think that a metadata table definition gets locked by a job when it uses it.

A normal kill signal is an interruptable one so that allows a process that gets this notification to cleanup up after itself. A kill -9 signal say "abort right now" and does not allow time for the process to close files correctly and release locks. A kill -9 should only be used as a last resort, such as if the normal kill modes haven't worked after a couple of minutes, and even then it should be clear that some locks will remain. The easiest solution is to let the deadlock daemon take care of these.