Clearing orphan datastage processes

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
NigeGriff
Premium Member
Premium Member
Posts: 46
Joined: Mon Nov 24, 2003 5:46 am

Clearing orphan datastage processes

Post by NigeGriff »

As part of our housekeeping processes to get rid of orphan datastage processes we schedule a weekly start/stop of datastage. Unfortunately the stop sometimes fails as daemon drsrpcd will not shutdown - the Datastage documentation for this that I have found on the Internet indicates that the process should timeout and die after approx 15 mins. Unfortunately that seems to be hit and miss and we have often ended up rebooting the our server to get Datastage up and running again.

Is there a script which will perform the stop/start with no risk of leaving Datastage in a state that may require a reboot?
Thanks
Nigel
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The period is primarily driven by the TCP wait timeout. If there are any connected processes to port 31538, even if they're in a SLEEP_WAIT or other "waiting to finish" state, then dsrpcd (the listener on that port) can not shut down. If you kill dsrpcd it won't restart (unless you reboot the server or clean up the TCP-connected processes). You get "bind bombed" error.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply