Page 1 of 1

job being monitored eror

Posted: Wed Dec 14, 2005 10:08 am
by knowledge
Hi ,

Now recently whenever I am tying to compile a job , I am often getting the message , job is being monitored I am enable to compile the job ,

pl suggest , as we have critical dead line , I am stuck in between

thnks

Posted: Wed Dec 14, 2005 10:12 am
by kcbland
Someone somewhere has a Director Monitor open on that job. Start by exiting all Director sessions on your PC and try again. If that doesn't work, starting asking everyone to get out and try again. If every single person is out, then recycle the DS services as something is obviously wrong internally with the locking mechanisms.

Posted: Wed Dec 14, 2005 3:04 pm
by ray.wurlod
Is the message IS being monitored, or MAY BE being monitored? The second of these can occur if any kind of lock on the job exists in the Repository - if the job is open in Monitor, Designer or Monitor, for example.

Posted: Wed Feb 15, 2006 12:28 pm
by us1aslam1us
Hi all,

I am having this error when i am trying to delete the job from the repository.
Cannot get exclusive access to the executable file for job
Also if i am trying to compile it its giving following error
Job may be being monitored
Thanks in advance

Posted: Wed Feb 15, 2006 3:39 pm
by ray.wurlod
Even having the job log open in Director can lead to "may be being monitored".

Posted: Wed Feb 15, 2006 5:52 pm
by us1aslam1us
After closing the job logs still i am having the same problem.Also i checked for any locks but none are there.

Thanks
sam

Posted: Wed Feb 15, 2006 5:54 pm
by ray.wurlod
HOW did you "check for locks"?

Posted: Wed Feb 15, 2006 5:57 pm
by us1aslam1us
From the cleanup resources in the director.

Thanks
sam

Posted: Wed Feb 15, 2006 11:32 pm
by ray.wurlod
That doesn't show locks held by defunct processes. You need to get to the Administrator client window or to the server and issue a LIST.READU command. If you can get to a UNIX prompt, even better is to issue the command from UNIX, so that you can pipe the output through grep and just search for that job name.

Code: Select all

. $DSHOME/dsenv
$DSHOME/bin/list_readu | grep jobname

Posted: Thu Feb 16, 2006 3:43 am
by Nageshsunkoji
Hi All,

Even i faced the same problem with my jobs sometime back. The main reason behind this is your job is running internally in the server.This is due to you forcefully close your job ( by using alt+ctrl+del in windows) or some other reason. The solution for this is kill your job by using Kill command ( know the PID first) in Unix or you can use Datastage director to Logout from this job by using Cleanup resources option in Tool in DS Director or you can come out of this problem by restarting your server.

Regards
Nagesh.

Posted: Thu Feb 16, 2006 9:19 pm
by MTA
You need to run UNLOCK from UVSH utility by logging onto the project from command line. If this does not work you may have to reboot the server

Posted: Thu Feb 16, 2006 10:46 pm
by us1aslam1us
Hi all,

It is solved!!

Just logged out of each process from the Director>>Cleanup Resources.

Thanks all for sharing your knowledge
sam