Job access by other and cant unlock

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

swades
Premium Member
Premium Member
Posts: 323
Joined: Mon Dec 04, 2006 11:52 pm

Job access by other and cant unlock

Post by swades »

When I am opening the job it says that the Job is being access by other user but when I see in Director for cleanup resource it says me :

ERROR: Cannot find any process numbers for stages in job hir_lre_aro_side

I tred in Admin. also by 'ds.tools' but it also giving me same massage.

How can I resolve this ?

Thanks in advance
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

This has been dealt with many times.
Check this one for a start
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
swades
Premium Member
Premium Member
Posts: 323
Joined: Mon Dec 04, 2006 11:52 pm

Post by swades »

Thanks for posting link that resolve my problem. I used following from that post:
Click on ok, and under locks, select Show All.
You might find your job. Note down the PID. Select the PId from Process block.
Now again click on show by process under Locks.
Click on release All.
Try to use dsadm user id
Thanks
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

On reading one of Ray's post, got to know that the good thing about 8.0 will be that - you get to know who has actually opened it.
So you tell that person to close it, rather than doing the clean up.
But I guess this situation is still going to continue, if the job does not get closed gracefully.
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

If a job was locked under your id, someone else cannot get rid of it. Only you have to go in with your id and unlock it. "Who unlocked the job" can also be determined in the present versions by going into the cleanup resources and bringing up current active threads. It will tell you the id right there.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Irrespective of the users, dsadm will have the full control of that.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

DSguru2B wrote:"Who unlocked the job" can also be determined in the present versions by going into the cleanup resources and bringing up current active threads. It will tell you the id right there.
Nice to know, I did not know we had a way to find out "Who unlocked the job".
I dont have access to Datastage right now, need to look into that feature.
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

O yea, forgot to add that. Thanks kumar.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

narasimha wrote: Nice to know, I did not know we had a way to find out "Who unlocked the job".
I dont have access to Datastage right now, need to look into that feature.
And in the DataStage admin, you can type LIST.READU to pull up the same info. Even that will give you a list of all the live/locked threads along with pid's and user id's.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

DSguru2B wrote:
narasimha wrote: Nice to know, I did not know we had a way to find out "Who unlocked the job".
I dont have access to Datastage right now, need to look into that feature.
And in the DataStage admin, you can type LIST.READU to pull up the same info. Even that will give you a list of all the live/locked threads.
I am familiar with finding the locked jobs, I was more interested in option of getting to know how to get to know who unlocked the job.
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Narasimha - LIST.READU brings user id as well. Wont it?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Yup. It sure will.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
narasimha
Charter Member
Charter Member
Posts: 1236
Joined: Fri Oct 22, 2004 8:59 am
Location: Staten Island, NY

Post by narasimha »

Guys, may be I am missing somethiing here.
LIST.READU gives us the the list of locked jobs, user-id, ... ,... - Agree.

It does not give you anything as to "who unlocked the jobs", right?
Narasimha Kade

Finding answers is simple, all you need to do is come up with the correct questions.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

User Id tells you that.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Now I see the reason of couple of your previous post. Missed that prominent word. I should be Locked rather than Unlocked.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Post Reply