Not able TO release the locked job
Moderators: chulett, rschirm, roy
Not able TO release the locked job
Hi All,
I am not able to release my locked job from the director....Yesterday suddenly the connection is broken from the server. After that when I tried opening the job it is saying "ACCESSED BY ANOTHER USER".. Till today it is displaying the same error..
Please help me in this regard...
Rgds,
Shiva.
I am not able to release my locked job from the director....Yesterday suddenly the connection is broken from the server. After that when I tried opening the job it is saying "ACCESSED BY ANOTHER USER".. Till today it is displaying the same error..
Please help me in this regard...
Rgds,
Shiva.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard.
Curiously you are not the first to encounter this, not even the 1000th. It results from the defunct process (the agent process whose connection was broken) no longer being accessible to be told to free the lock.
If you look at the menu at the top of this page you will see a Search option. You can find this question, and its resolution.
Curiously you are not the first to encounter this, not even the 1000th. It results from the defunct process (the agent process whose connection was broken) no longer being accessible to be told to free the lock.
If you look at the menu at the top of this page you will see a Search option. You can find this question, and its resolution.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
<color=blood>
Premium membership helps to pay for the bandwidth costs of DSXchange. It only costs a few cents per day, and it's definitely worth it, not least because it helps to ensure that DSXchange remains alive.
</color>
Premium membership helps to pay for the bandwidth costs of DSXchange. It only costs a few cents per day, and it's definitely worth it, not least because it helps to ensure that DSXchange remains alive.
</color>
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.
Hay....
1: if the error is "Job being accessed by another user"that means same job is opened in another session.Please close that session or close dat job from datastage canvas.
2:if your job is hanged up and nothing is working then restart the server.
but before doing dat please try to kill that process.
Thanks,
Akumar1
1: if the error is "Job being accessed by another user"that means same job is opened in another session.Please close that session or close dat job from datastage canvas.
2:if your job is hanged up and nothing is working then restart the server.
but before doing dat please try to kill that process.
Thanks,
Akumar1
Re: Not able TO release the locked job
Dear Shiva,
Have you tried to unlock your job from DS administrator DS tool?
Rgds,
Have you tried to unlock your job from DS administrator DS tool?
Rgds,
Team_2007 wrote:Hi All,
I am not able to release my locked job from the director....Yesterday suddenly the connection is broken from the server. After that when I tried opening the job it is saying "ACCESSED BY ANOTHER USER".. Till today it is displaying the same error..
Please help me in this regard...
Rgds,
Shiva.
-
- Participant
- Posts: 10
- Joined: Fri May 12, 2006 12:31 am
Shiva,
you are getting this message because the session that was aborted had the job locked and this lock has not been released. There are many ways of releasing this lock and all of them have been described in detail in other posts on this site.
The preferred (and documented) method is to use the "cleanup resources" menu option from the director client.
you are getting this message because the session that was aborted had the job locked and this lock has not been released. There are many ways of releasing this lock and all of them have been described in detail in other posts on this site.
The preferred (and documented) method is to use the "cleanup resources" menu option from the director client.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Your second point is singularly poor advice. One should identify the owner of the lock and determine whether they are still connected; if so they can be asked to close the edit window they have open on the object. Then, if there is a defunct process owning the lock, the lock may be released, for example from the DS.TOOLS menu. No need to kill anything, no need to restart DataStage.Akumar1 wrote:Hay....
1: if the error is "Job being accessed by another user"that means same job is opened in another session.Please close that session or close dat job from datastage canvas.
2:if your job is hanged up and nothing is working then restart the server.
but before doing dat please try to kill that process.
Thanks,
Akumar1
Grammatical Note
The word "dat" is inappropriate in this context.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
More information is required. Including:
- Why do you "shout" (bad netiquette, definitely bad in a professional forum)?
Where did you learn to spell? (I'd be seeking a refund.)
Are you aware that Cleanup Resources does not pick up locks held by defunct processes?
How does one identify "all processes for that job" in the Cleanup Resources window?
Why do you advise "kill" when it's already been documented on the forum as bad advice?
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.