Posted: Mon Oct 04, 2004 6:20 pm
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.
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.