Performance issue

ArndW · Post by **ArndW** » Fri Mar 21, 2008 6:16 am

No, you won't directly be able to kill this process without root access. After stopping DataStage what does the "ipcs -a | grep 0xade" command show?

arsheshadri · Post by **arsheshadri** » Fri Mar 21, 2008 6:32 am

[quote="ArndW"]No, you won't directly be able to kill this process without root access. After stopping DataStage what does the "ipcs -a | grep 0xade" command show? ...[/quote]

Below are the results.

[/DataStage/product/Ascential/DataStage/DSEngine]$ [b]./bin/uv -admin -stop[/b]
Unable to remove the following shared memory segment(s) during shutdown:
m 3145730 0xadec7512 --rw-rw-rw- root system 1364054 1126422
m 84934708 0xadee7512 --rw-rw-rw- root system 1765440 1126422
Stopping JobMonApp
JobMonApp has not been started from: /DataStage/product/Ascential/DataStage/PXEngine
2 error(s) encountered during shutdown procedure.
DataStage Engine 7.5.1.2 instance "ade" may be in an inconsistent state.

[/DataStage/product/Ascential/DataStage/DSEngine]$ [b]ipcs -a | grep 0xade[/b]m 3145730 0xadec7512 --rw-rw-rw- root system root system 0 6925448 1364054 1126422 12:05:48 12:10:34 13:00:59
m 84934708 0xadee7512 --rw-rw-rw- root system root system 0 905400 1765440 1126422 12:05:48 12:10:34 13:00:59

[/DataStage/product/Ascential/DataStage/DSEngine]$ [b]ps -ef|grep -e dsrpc[/b] root 253966 1 0 Feb 15 - 0:00 /DataStage/product/Ascential/DataStage/DSEngine/bin/dsrpcd

Thanks & Regards
Shesha

ArndW · Post by **ArndW** » Fri Mar 21, 2008 6:36 am

You might need to get root to kill the process for you.
Try "ipcrm -m 3145730 " and "ipcrm -m 84934708 " and another shutdown.

p.s. You don't need to quote my posts in your replies.

arsheshadri · Post by **arsheshadri** » Fri Mar 21, 2008 6:39 am

I am getting below error -
ipcrm: 0515-021 shmid(3145730): The user does not have the appropriate privileges to perform this operation.

After stop command, the netstat|grep dsrpc is giving below results

tcp4 0 0 172.22.162.228.dsrpc 172.24.130.60.4393 ESTABLISHED
tcp4 37 0 172.22.162.228.dsrpc 147.146.138.89.boomera CLOSE_WAIT
tcp4 37 0 172.22.162.228.dsrpc 147.146.138.89.pacmand CLOSE_WAIT
tcp4 37 0 loopback.dsrpc loopback.63563 CLOSE_WAIT
tcp4 37 0 loopback.dsrpc loopback.63566 CLOSE_WAIT
tcp4 37 0 172.22.162.228.dsrpc 172.24.130.28.webemsht CLOSE_WAIT
tcp4 37 0 172.22.162.228.dsrpc 172.24.130.28.ndsp CLOSE_WAIT
tcp4 0 0 172.22.162.228.dsrpc 172.24.130.28.topflow CLOSE_WAIT
tcp4 37 0 172.22.162.228.dsrpc 172.24.130.28.rsom CLOSE_WAIT

Thanks & Regards
Sheshadri

ArndW · Post by **ArndW** » Fri Mar 21, 2008 6:39 am

you will need root access after all, with root I think using the "uv -admin -stop" should work.

arsheshadri · Post by **arsheshadri** » Fri Mar 21, 2008 6:44 am

Thanks ArndW for all your support and valuable time. I will try to get hold of SA and kill these processes.

Thanks Again
Shesha

bcarlson · Post by **bcarlson** » Fri Mar 21, 2008 3:16 pm

These are some directions I was given for start/stop server:

DataStage - Start and Stop server
==============================

Note: This must be done as dsadm or run via JIL: EDWDDB_DSADMz_B0001 (run C1, C2, C4 manually).

1) Determine if DataStage is running: $DSHOME/bin/uv -admin -info
2) Stop server: $DSHOME/bin/uv -admin -stop
3) Make sure DS is down, repeat step1 . Also, you can't bring DataStage back up until all connections are dropped. Use:
netstat -a | grep dsrpc
Rows returned are connections that have not been dropped yet. Wait until all connections are dropped.

You can also use the following (runs faster):
netstat -nAa |grep 31538
See notes below if TCP connections are taking a long time to disconnect

4) Start srever: $DSHOME/bin/uv -admin -start
5) Repeat step 3 to determine if it is running OK. The netstat command should return 1 record:
edwdev2:/home/dsadm> netstat -a | grep -i dsrpc
tcp4 0 0 *.dsrpc *.* LISTEN
edwdev2:/home/dsadm>

Brad.

ray.wurlod · Post by **ray.wurlod** » Fri Mar 21, 2008 5:24 pm

What's in the "notes below" regarding long-waiting TCP connections?

bcarlson · Post by **bcarlson** » Mon Mar 24, 2008 8:55 am

Didn't even notice that reference... Here is the rest:

TCP connections are taking along time to disconnect
=============================================
1. Determine if anyone has any outstanding DataStage sessions open:

# Note: this is also in dsadm@myserver:/home/dsadm/find_open_sessions.sh
netstat -nAa |grep 31538 | awk '{print $6}' | cut -d '.' -f1-4 | sort -u | while read useripaddr
do
who | grep $useripaddr
done

2. Per Jon K, determine who is tied to a TCP connection. Use netstat -a to get connections, then use lsof.

myserver:/home/dsadm> netstat -a | grep -i dsrpc
tcp4 0 0 localhost.dsrpc localhost.60118 CLOSE_WAIT
tcp4 0 0 localhost.dsrpc localhost.38549 CLOSE_WAIT
myserver:/home/dsadm> lsof -i 4tcp@localhost:38549
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
dbx 7929986 userid01 4u IPv4 0xf100020008978390 0t0 TCP localhost:dsrpc->localhost:38549 (CLOSE_WAIT)
lsof: WARNING: /home/dsadm/.lsof_myserver was updated.

* What is lsof? From Wikipedia:

lsof is a command used in many Unix-like systems that is used to report a list of all open files and the processes that opened them. It works in and supports several UNIX flavors.

Open files in the system include disk files, pipes, network sockets and devices opened by all processes. One use for this command is when a disk cannot be unmounted because (unspecified) files are in use. The listing of open files can be consulted (suitably filtered if necessary) to identify the process that is using the files.

Links: http://www.netadmintools.com/html/lsof.man.html

Brad.