Hi
Ia m gettign an erro when I try to open a job:
' job <jobname> is locked by the user isadmin'.
I am logging into Datastge as isadmin.
I tried to unlock it by going to DSEngine directory and run following commands:
[dsadm@lxdscon DSEngine]$ bin/dssh
DataStage Command Language 8.0 Licensed Materials - Property of IBM
(c) Copyright IBM Corp. 1997, 2006 All Rights Reserved.
DSEngine logged on: Wednesday, February 20, 2008 12:00
>LIST.READU
Active Record Locks:
Device.... Inode.... Netnode Userno Lmode Pid Login Id Item-ID.............
64770 18335 0 39007 14 RL 26529 dsadm dsdev&!DS.ADMIN!&
>UNLOCK USER 39007 ALL
Clearing Record locks.
Clearing GROUP locks.
Clearing FILE locks.
>LIST.READU
No locks or semaphores active.
But when I try to open same job it is showing the same message again.
Please help!
Thanks in advance.
unlocking the job
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 644
- Joined: Sat Aug 26, 2006 3:59 pm
- Location: Mclean, VA
unlocking the job
Attitude is everything....
Can you try this and check if you could UNLOCK your job:
1. Login to the server with your UNIX id and get into bourne shell , here in example, dev.it.server.com
2. Change you current working directory to DataStage engine directory.
here in example,
$ pwd
/server/etl/ascential/Ascential/DataStage/DSEngine
3. sh
Set the dsenv path
$ . ./dsenv
4. Login to uv
$ uv
>LOGTO PROJECTNAME
>DS.TOOLS
select option 4 from the first menu
select option 4 again from the second menu
5. Look for your job name, if it is locked by your id. If so get the pid (immediate left to your id). note down the pid.
6. Keep pressing "press any continue", until you are out of the list,
7. Select option 9 and give the pid.
Enter pid#=111
OK to logout process 738? (N): Y
You will be all set. Note: This can also be done by logging in to administrator.
1. Login to the server with your UNIX id and get into bourne shell , here in example, dev.it.server.com
2. Change you current working directory to DataStage engine directory.
here in example,
$ pwd
/server/etl/ascential/Ascential/DataStage/DSEngine
3. sh
Set the dsenv path
$ . ./dsenv
4. Login to uv
$ uv
>LOGTO PROJECTNAME
>DS.TOOLS
select option 4 from the first menu
select option 4 again from the second menu
5. Look for your job name, if it is locked by your id. If so get the pid (immediate left to your id). note down the pid.
6. Keep pressing "press any continue", until you are out of the list,
7. Select option 9 and give the pid.
Enter pid#=111
OK to logout process 738? (N): Y
You will be all set. Note: This can also be done by logging in to administrator.
Thanks and Regards!!
dspxlearn
dspxlearn
No locks or semaphores active.
There aren't any locks to release. Therefore, this issue is something related to 8.0 lock management. Sorry I can't help out here, but 8.0 is not at my disposal right now. My guess is that there's something in the repository locked, not in the DS engine.
There aren't any locks to release. Therefore, this issue is something related to 8.0 lock management. Sorry I can't help out here, but 8.0 is not at my disposal right now. My guess is that there's something in the repository locked, not in the DS engine.
Kenneth Bland
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
Rank: Sempai
Belt: First degree black
Fight name: Captain Hook
Signature knockout: right upper cut followed by left hook
Signature submission: Crucifix combined with leg triangle
-
- Premium Member
- Posts: 644
- Joined: Sat Aug 26, 2006 3:59 pm
- Location: Mclean, VA
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Premium Member
- Posts: 644
- Joined: Sat Aug 26, 2006 3:59 pm
- Location: Mclean, VA
Courtesy: ArndW
At version 8 the locking mechanism is no longer exclusively controlled within the DataStage server engine as it was in the past, there are now other components involved on the IBM Information Server side.
Open up and connect to "http://{servername}:9080" in a browser, login with "isadmin", click on the "administration" tab, select "Session Management" then "active sessions", locate the offending session and click on "disconnect".
At version 8 the locking mechanism is no longer exclusively controlled within the DataStage server engine as it was in the past, there are now other components involved on the IBM Information Server side.
Open up and connect to "http://{servername}:9080" in a browser, login with "isadmin", click on the "administration" tab, select "Session Management" then "active sessions", locate the offending session and click on "disconnect".
Attitude is everything....