DataStage Unix Help
Posted: Mon Mar 10, 2003 12:09 am
Hi,
We are using DataStage on Unix installation. Also the DataStage jobs are used to connect/load data into SAP-BW.
We have following problems encounterd almost everyday.
After certain time of usage in a day, additional users are not able to connect to DataStage Engine. We have total 10 licences.
As soon as the problem is faced,we does the following at UNIX server
connect through dsadm and
$ netstat -a | grep uvrpc
The report shows 5-6 connections as "ESTABLISHED" and many other in FIN_WAIT1, FIN_WAIT2, CLOSE_WAIT etc.
My questions are
1) what are these FIN_WAIT1, FIN_WAIT2, CLOSE_WAIT status in netstat report?
2) Are these active connections OR terminated connections which are stoping me to establish more connections?
3) How to identify process-id for these jobs listed in netstat report so that i can kill those processes from unix prompt?
4) Will killing of these processes will affect any of DataStage jobs?
5) Most important, How do I prevent having such jobs occuring with netstat report status FIN_WAIT1, FIN_WAIT2, CLOSE_WAIT?
Currently we observe the practise of restarting DataStage Engine when we face the problem. However practically we wait for more then 15-20 minutes to automatcially clear all such processes after stopping the DataStage engine.
Please suggest.
Thanks in advance.
Sanjay Desai
We are using DataStage on Unix installation. Also the DataStage jobs are used to connect/load data into SAP-BW.
We have following problems encounterd almost everyday.
After certain time of usage in a day, additional users are not able to connect to DataStage Engine. We have total 10 licences.
As soon as the problem is faced,we does the following at UNIX server
connect through dsadm and
$ netstat -a | grep uvrpc
The report shows 5-6 connections as "ESTABLISHED" and many other in FIN_WAIT1, FIN_WAIT2, CLOSE_WAIT etc.
My questions are
1) what are these FIN_WAIT1, FIN_WAIT2, CLOSE_WAIT status in netstat report?
2) Are these active connections OR terminated connections which are stoping me to establish more connections?
3) How to identify process-id for these jobs listed in netstat report so that i can kill those processes from unix prompt?
4) Will killing of these processes will affect any of DataStage jobs?
5) Most important, How do I prevent having such jobs occuring with netstat report status FIN_WAIT1, FIN_WAIT2, CLOSE_WAIT?
Currently we observe the practise of restarting DataStage Engine when we face the problem. However practically we wait for more then 15-20 minutes to automatcially clear all such processes after stopping the DataStage engine.
Please suggest.
Thanks in advance.
Sanjay Desai