On a frequent basis my jobs get locked at the Server

[trokosz]

First, if your getting excessive locking, "job designed not found", "can't save DS OBJECTS" and all of those weird messages then its more than likely pointing towards a Job design issue. An issue where there are more locks being generated than being released.

For example, if you have Jobs using the "enable lock for updates" output selection on a Hash File Stage then immediately change to "enabled" or preferably "disabled". Please do not use the enable lock for updates selection anywhere (refer to to the DataStage Server Guide for details).

Also, never cancel a Job by allowing developers to Kill or Kill -9 which I see too many people revert towards.

If the locks get too much for a specific Project to handle then unlocking may not work anymore and actually that Project would shutdown. At this point you need to clear all shared memory segments (root only) by using DS.Tools, unlocking, and flushing all orphaned processes.

The bottomline I find is if excessive locking occurs its how a Job was designed.

[trokosz]

1. Deadlock Daemon is found in cd $DSHOME and the file is dslockd.config. After you change start to 1 then save and stop/start the DS Engine. Look at the DataStage install guide.

2. For dsadm to have many rights like root then look at the DataStage install guide post configuration steps. Most importantly make sure impersonation mode is turn-on.

3. You can use DS.TOOLS to unlock but an easier way is to log into DS Administrator and click command:

3a. LIST.READU EVERY shows all the locks and users
3b. Note the user having the problem and write down every UserNo assciated with that person.
3c. For the first time you need to SET.FILE UV UV.VOC, hit enter, then COPY FROM UV.VOC TO VOC UNLOCK, and hit enter. Once you do this on a server your done.
3d. UNLOCK USER <UserNo written> ALL....do this over and over for each UserNo written

[jayankurianvarghese]

Check it out weather you exceeded the licenced ports or not. If you exceedes then the systems in the network may get hanged. Or it may happen if one of the system in the network may face some particular hard ware problem. This problem we faced. Later on we removed the system from the network. Now it is fine. Try it.

[faheemrao]

What you can do is go to Director and select the job which is in question. and then select "Job" menu select the option "Cleanup resources" , you may get an error messege that no process were found for the job. ignore that and press ok. You will get a new popu window you will see 2 pans in the window. Lower pan and upper pan go to lower pan id nothing is listed there select the radio button show all and then look for your job name under item id columns , find out all the PID for the your item and then note them down on papers. Now go to upper pan and select "show All" radio button and then look for all those precess IDs and press Logout button for all those process ids.
You should be good.

Rao

We have just installed Ascential DataStage 6.01 on Hp Ux server.

For all the projects we are facing the following problem.

On a frequent basis our jobs are getting locked on the DataStage Server.
In the administrator we had set the Inactivity Timeout setting to do not timeout but still our jobs are getting locked.

Can someone tell us why this is taking place and how to resolve it.