Cannot get Exclusive Access to Job to Compile it
Moderators: chulett, rschirm, roy
Cannot get Exclusive Access to Job to Compile it
Hi,
Iam unbale to compile the job . It shows the below message.
Cannot get Exclusive Access to Job to compile it. For the first time i am able to compile and the next day when i open .it gives above message. this job is not accessed byany ne.
Please help me out.
Iam unbale to compile the job . It shows the below message.
Cannot get Exclusive Access to Job to compile it. For the first time i am able to compile and the next day when i open .it gives above message. this job is not accessed byany ne.
Please help me out.
thanks n regards
nani
nani
Re: Cannot get Exclusive Access to Job to Compile it
hI
simply close the datastage designer and open that job and complile it,
it will works fine.
by ASH
simply close the datastage designer and open that job and complile it,
it will works fine.
by ASH
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This problem can be caused simply by having the log view for the job open in Director.
Log view sets a lock that prevents the job from being changed while the log is being viewed - a reasonable precaution, if you think about it.
Log view sets a lock that prevents the job from being changed while the log is being viewed - a reasonable precaution, if you think about it.
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.
Can you open this link ?
http://www-01.ibm.com/support/docview.w ... ss=ct14db2
Also go to the Director and run the "Cleanup Resources" for this job, logging out all of the possible processes locking the job, but ensure that no user is acessing the job and it is not scheduled to run.
http://www-01.ibm.com/support/docview.w ... ss=ct14db2
Also go to the Director and run the "Cleanup Resources" for this job, logging out all of the possible processes locking the job, but ensure that no user is acessing the job and it is not scheduled to run.