Cannot get Exclusive Access to Job to Compile it

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
nani0907
Participant
Posts: 155
Joined: Wed Apr 18, 2007 10:30 am

Cannot get Exclusive Access to Job to Compile it

Post by nani0907 »

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.
thanks n regards
nani
DWH-M
Premium Member
Premium Member
Posts: 46
Joined: Thu Sep 06, 2007 5:26 am

Re: Cannot get Exclusive Access to Job to Compile it

Post by DWH-M »

hI

simply close the datastage designer and open that job and complile it,
it will works fine.

by ASH
nani0907
Participant
Posts: 155
Joined: Wed Apr 18, 2007 10:30 am

Post by nani0907 »

No Luck. Stiil the same issue
thanks n regards
nani
Sainath.Srinivasan
Participant
Posts: 3337
Joined: Mon Jan 17, 2005 4:49 am
Location: United Kingdom

Post by Sainath.Srinivasan »

Can you check from webconsole
GJ_Stage
Participant
Posts: 131
Joined: Mon Oct 27, 2008 6:59 am

Post by GJ_Stage »

Go to Directory and select the cleanup resources and logout this job.
dipanzan
Participant
Posts: 5
Joined: Thu Mar 19, 2009 12:33 pm

Post by dipanzan »

Open the director and close the log for that job and then try to compile your job..
Dipanjan
mandyli
Premium Member
Premium Member
Posts: 898
Joined: Wed May 26, 2004 10:45 pm
Location: Chicago

Post by mandyli »

Hi

Best option via Director do 1st clear the stat file and then cleanup resource.

If you still facing same issue. try to delete RT_LOGnnn file and RT_STATUSnnn file from datastage project folder or else reboot the DS server.


Thanks
Man
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
jgkayser
Participant
Posts: 3
Joined: Tue Feb 09, 2010 2:25 am

Post by jgkayser »

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.
Post Reply