Page 1 of 3
Job locked, cant delete/modify but it can be run
Posted: Wed Apr 22, 2009 5:22 am
by manuel.gomez
Hi guys,
New problems with locked job.
Once again, message Cannot get exclusive access to job when wanting to rename it (but the job runs every night)
I got into the console and executed this:
But no locks showed up for this process
I then went to DS.TOOLS, Administrer Locks, logout all process in a job
When I am asked to enter job name and I do, I am returned the following message:
DataStage Process and Lock Administration
1. List all processes
2. List state of a process
3. List state of all processes in a job
----------------------------------------------
4. List all locks
5. List locks held by a process
6. List locks held by all processes in a job
----------------------------------------------
7. Clear locks held by a process
8. Clear locks held by all processes in a job
----------------------------------------------
9. Logout a process
10. Logout all processes in a job
11. Clear status file for a job
Which would you like? ( 1 - 11 ) ?10
Enter job name or <CR> for list=JS_ATN
Cannot find job %1
But the job is clearly there:
LIST DS_JOBS WITH JOBNO EQ 253 13:17:44 04-22-09 PAGE 1
Job name.... JS_ATN
Description.
No.......... 253
Category.... \Drop3_FINAL\Actions
ToNCRM
This also worked:
LIST DS_JOBS WITH NAME EQ "JS_ATN" 13:24:01 04-22-09 PAGE 1
Job name.... JS_ATN
Description.
No.......... 253
Category.... \Drop3_FINAL\Actions
ToNCRM
1 records listed.
Can anybody please help me to unlock this job?
By the way, my locked job is actually a sequence
Posted: Wed Apr 22, 2009 6:24 am
by sjfearnside
Here is some documentation I have on releasing locks from my support vendor.
Pblm:
The Folder 'Jobs' is locked by user 'xmeta'
(SessionID 'xmeta-1')'
Reply from DS Support
"Go to the default IS installation (/IBM/app/InformationServer/ASBServer/bin) directory and run the cleanup_abandoned_locks.sh script from a telnet session while logged in as root. Please make sure that all users are logged out before you do this.
$ ./cleanup_abandoned_locks.sh
Enter the IS admin user and password when prompted. Once the process has completed, you will be returned to the UNIX command line and may not see any informational messages."
Running the Script solves my problem. Hope you find it useful.
Posted: Wed Apr 22, 2009 8:19 am
by chulett
DS.TOOLS in no longer the proper place for activties like this in the 8.x release.
Posted: Wed Apr 22, 2009 8:23 am
by manuel.gomez
sjfearnside wrote:Here is some documentation I have on releasing locks from my support vendor.
Pblm:
The Folder 'Jobs' is locked by user 'xmeta'
(SessionID 'xmeta-1')'
Reply from DS Support
"Go to the default IS installation (/IBM/app/InformationServer/ASBServer/bin) directory and run the cleanup_abandoned_locks.sh script from a telnet session while logged in as root. Please make sure that all users are logged out before you do this.
$ ./cleanup_abandoned_locks.sh
Enter the IS admin user and password when prompted. Once the process has completed, you will be returned to the UNIX command line and may not see any informational messages."
Running the Script solves my problem. Hope you find it useful.
Thanks again for answering
I tried the script, but it did not work
Posted: Wed Apr 22, 2009 8:41 am
by dsuser_cai
Use this,
list.readu
then select the user, and use this command to unlock
unlock user <specify user number> all
this will release/unlock all jobs for that particular user.
Posted: Wed Apr 22, 2009 8:52 am
by sjfearnside
Do you have the opportunity to stop and restart DataStage, InformationServer and WebSphere? You would need to get everyone logged off DataStage and no job running.
My support provider has stated that WebSphere at times gets confused and needs to be restarted. Not a technical explanation but it has worked for me in the past to release locks.
If that is not an option, can you see the PID associated with the locked job? If you identify the correct PID, you can kill the PID but be careful that you do not kill a running process that is required.
It may be wise, if you have the time, to see if Craig or Ray offer better/safer alternatives.
Posted: Wed Apr 22, 2009 9:35 am
by manuel.gomez
dsuser_cai wrote:Use this,
list.readu
then select the user, and use this command to unlock
unlock user <specify user number> all
this will release/unlock all jobs for that particular user.
the problem is that the job does not show when i do
LIST.READU EVERY
So that the user to enter there
Posted: Wed Apr 22, 2009 9:35 am
by dsuser_cai
If you want to unlock the jobs based on process id, then use this.
In DS Admin
Ds.tools
Choose option 4 (Administer processes/locks)
Choose option 4 (List All Locks)
Note the PIDs
Choose option 7 and enter PID
Posted: Wed Apr 22, 2009 9:37 am
by manuel.gomez
dsuser_cai wrote:If you want to unlock the jobs based on process id, then use this.
In DS Admin
Ds.tools
Choose option 4 (Administer processes/locks)
Choose option 4 (List All Locks)
Note the PIDs
Choose option 7 and enter PID
thanks for your help
as I just told you, my job does not show here
Posted: Wed Apr 22, 2009 9:39 am
by manuel.gomez
sjfearnside wrote:Do you have the opportunity to stop and restart DataStage, InformationServer and WebSphere? You would need to get everyone logged off DataStage and no job running.
ufff......production server......If we have any problem restarting services....this issue with this job will be the most insignificant thing to worry about, hahaha
Posted: Wed Apr 22, 2009 9:45 am
by JRodriguez
manuel.gomez,
Did you see any open session in the Web Console realted to that job?
If any active session related to that job just try to disconnect it ....
Posted: Wed Apr 22, 2009 9:57 am
by manuel.gomez
JRodriguez wrote:manuel.gomez,
Did you see any open session in the Web Console realted to that job?
If any active session related to that job just try to disconnect it ....
no sessions at all, that was my first check
Actually, when executed script suggested by sjfearnside , all sessions where closed
final solution
Posted: Wed Apr 22, 2009 10:05 am
by edison
copy the sequencer and delete the original job,and re-name the copied job,it will work fine
Re: final solution
Posted: Wed Apr 22, 2009 10:10 am
by manuel.gomez
edison wrote:copy the sequencer and delete the original job,and re-name the copied job,it will work fine
as you can see in the topic title, cant delete the job either due to this same problem
Posted: Wed Apr 22, 2009 10:30 am
by chulett
Are you sure it is actually locked? "Cannot get exclusive access to job" doesn't necessarily mean locked, but could mean running or perhaps even someone browing the job log. Or did it specifically tell you it was locked?