DSXchange

Hi,

I cannot access my job as it says it's being accessed by another user. Any remedies for this ?


Thanks

First check if that job is being accessed by another user. In that case you will have to ask that user to close the job for you to access. Else what you need to do is go to director and check if you have the rights to do a clean up (You get this feature only if this is checked in administrator). In case you have you can try this from 'job' tag. Well if you don't hvae that option you will have to do this from unix.

First rememdy would be to search here for your message 'accessed by another user'. I got 48 matches where this topic has been discussed, I'm sure you'll find an appropriate answer out there.

Hi I tried doing a clean up, but it doesnt take effect....Would you mind telling me the steps and also how i can do it unix.

Thanks

cosec wrote:Hi,

I cannot access my job as it says it's being accessed by another user. Any remedies for this ?


Thanks

Did you not have any luck searching? It's all out there, having been discussed in detail many times before this. Why make someone type it all up again?

ps. For it to 'take effect' you need to be cleaning up either your own processes or doing it as dsadm. But then if you'd searched and done some self discovery you would have known that. :D

The only way you can "do it unix" (sic) is to re-boot the server, which is overkill. You need, using DataStage tools, to identify the owner of the lock, determine whether the lock is validly held and - only if it is not validly held - unlock it. If it is validly held you should negotiate with the current owner.

HI,
Follow these steps to release the lock:
In Directory->In Toolbar Select job->Select Job Resource->Select show all in both Processes and Locks->In locks option find out the PID with crosponding job name->then select the PID of the job in Processes option->finaly press logout tab, then alert tab will gets, just press ok and close

Welcome aboard.

Your advice is poor. One first needs to establish that the lock is not validly held - for example someone else may be editing that job.

Arbitrarily releasing locks is "worst practice" and can lead to lost work.

One of the best solution is to find out if the Job which is Locked is being really accessed by another user ......If its not then just tell all your team members working on DS to save their work and close the application.
After this just restart your DS server....this will release all the Locks.

If no one seems to have this job open, but still you get this error, you dont have to restart DS server, you can just RESET so these orphaned processes/locks get released.

Issue a "uvadmin -reset", when logged in as DS admin on UNIX

Asking rest of team members to save work and close application is not something you can do everytime such a thing happens.. with reset everyone can keep working..