Cannot get exlusive access to ex..job may be being monitored

Alethesnake · Post by **Alethesnake** » Thu Feb 12, 2009 2:41 am

Hi all,
I've a problem with a sequence.
Yesterday I runned a sequence that remained running for almost 1 hour by doing nothing (it seems a dead-lock), it simply keept still before the attaching of a job.
I tried to stop it from the director several times without success, so I decided to kill its respective pid (I get it from the unix shell with ps -emo THREAD and I killed it with kill -9 <pid>).
The job finally stopped, but now I'm not able to recompile it. I can reset it, I can run it (successfully) but everytime I try to compile it I get the message:

Cannot get exclusive access to executable file for job XXX job may be being monitored.

Is there a way to "unlock" this job?

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Thu Feb 12, 2009 4:02 am

look for locks from iis administration

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Thu Feb 12, 2009 4:02 am

look for locks from iis administration

richdhan · Post by **richdhan** » Thu Feb 12, 2009 4:34 am

Hi,

Check if the job is being monitored in the Director. Just change the view in Director from log view to status view.

Let us know what happens.

There are also other options in Director like Clean up resources and Clear status file which can be used to release the locks if any.

HTH
--Rich

Alethesnake · Post by **Alethesnake** » Thu Feb 12, 2009 5:50 am

looking at the unix console no lock seems to be active on the job.
Note, I can run, reset, edit and save the job. I 'only' cannot compile it.

Alethesnake · Post by **Alethesnake** » Thu Feb 12, 2009 5:54 am

richdhan wrote:Hi,

Check if the job is being monitored in the Director. Just change the view in Director from log view to status view.

Let us know what happens.

There are also other options in Director like Clean up resources and Clear status file which can be used to release the locks if any.

HTH
--Rich

I also tried to close the director, but the problem remains.

ray.wurlod · Post by **ray.wurlod** » Thu Feb 12, 2009 1:56 pm

Could anyone else in the organization be monitoring the job or have it open ? Just because you close the Director does not preclude that possibility. The locks are on the server.

If this is a parallel job with a Transformer stage, try a Force Compile.

Alethesnake · Post by **Alethesnake** » Mon Feb 16, 2009 4:14 am

Actually I'm the one with access permission to the project, and from the consolle no other connections seems active to the server.
The problem rose when the Sequence remained running before the attachment of a job by doing nothing and I killed its pid from the unix shell.
It seems like the executable of the sequence has remained read-only (it's only an hypotesis). Is it possible to manually delete/chmod the executables? Which is their path?
Thanks a lot.

ray.wurlod · Post by **ray.wurlod** » Mon Feb 16, 2009 2:30 pm

Do not, ever, use kill -9 on DataStage processes.

You will only deepen the hole you have already dug.

Use the DS.TOOLS menu or Cleanup Resources in Director.

Alethesnake · Post by **Alethesnake** » Tue Feb 17, 2009 3:44 am

ray.wurlod wrote:Do not, ever, use kill -9 on DataStage processes.

You will only deepen the hole you have already dug.

Use the DS.TOOLS menu or Cleanup Resources in Director. ...

I understand, I will never again use the kill -9 on datastage processes.
I finally unlock my sequence by cleaning up all resources in the director, I initially had some problems to catch the right process to release.

Thanks a lot to all for your suggestions.

Bye,

Ale.