Friday, January 21, 2011

DS - UNLOCK OBJECT

ACCESS TO DATASTAGE UNIVERSE ::
Although DataStage is going to abandon Universe as its repository, it is still useful if you have not yet migrate to version 8. You may also found some useful utilities in the universe admin interface. Here is the details :
(1) To retrieve job information …
$DSHOME/bin/uvsh “select * from DS_JOBS;”
(2) To list and unlock all present lock ….
LIST.READU EVERY
UNLOCK ALL
(3) Invoke admin tool …
DS.TOOLS
(4) To delete and recreate a log file …
DELETE.FILE DATA RT_LOG182
CREATE.FILE DATA RT_LOG182 30
the number in “RT_LOGxxx” can be found using (1) …
*************************************************
       *********   UNLOCK DATASTAGE OBJECT **************

Just find a useful thread in IBM’s forum : How to unlock a job accessed by another user. 
Removing locks when you receive the error: Cannot get exclusive access

1. Login to DataStage Administrator as an administrative user.
2. Go to the Command Prompt for that Project.
3. Look at the locks by executing:  LIST.READU
4. The last column is the item id. Look for item id’s like:  jobname
This is the record you will want to unlock. Now you can note the inode or user no, whichever uniquely identifies the record.
5. The unlock command is not available by default in the projects. To create an entry to use unlock execute the following two commands:
>SET.FILE UV VOC UV.VOC
>COPY FROM UV.VOC TO VOC UNLOCK
Note: This only needs to be done the first time in each project.
6. To unlock by either INODE or User No use the commands:
UNLOCK INODE inodenumber ALL
UNLOCK USER usernumber ALL
Another approach :
1. telnet to DS server machine as ds administrative account (dsadm or root for example);
2. cd to $DSHOME;
3. source dsenv by “. ./dsenv”; (read as dot_space_dot_dsenv)
4. run “bin/uvsh” to enter TCL prompt;
5. run “>LIST.READU EVERY”, are you able to find any lock for the project under Active Record Locks? If yes, mark down the Userno for the command below;
6 run “>UNLOCK USER userno ALL”;
7. run “>LIST.READU EVERY” again to verify the lock for the user is gone;
8. repeat step 6 and 7 until all locks for the project is clear;
9. run “>LO” to exit TCL prompt.
10. try login to the project again.

**************************************************************

1 comment:

  1. Nice post.I just download and use "Long Path Tool" guarantees to fix your error fast and easy.

    ReplyDelete