After Shutting down the Livecache in SCM4.1

[Former Member]

Hi,

We have newly implimented SCM4.1 server when we shut down our LiveCache server which have Database "MAXDB" and Application SCM4.1 Run on Oracel 9.2.07 Database.

whenever we shut down our complete Application SCM4.1

we have found that there are still some services of MAXDB is running.

Sun Microsystems Inc. SunOS 5.10 Generic January 2005

1. ps -ef |grep sap

sdb 14831 14830 0 May 10 ? 0:00 /sapdb/programs/pgm/vserver start

sdb 14830 23636 0 May 10 ? 0:00 /sapdb/programs/pgm/vserver start

sdb 14829 23636 0 May 10 ? 0:00 /sapdb/programs/pgm/niserver

root 20351 20346 0 10:07:16 pts/5 0:00 grep sap

#

Please let us know .

1. What is this services Mean?

2. Why this services running after the complete shutdown of application?

3. is there any bad impcat on the server if we poweroff system during running these services

Please let us know

Regards,

Vivekanand Pandey

[former_member229109]

Hello Vivekanand,

Please update the ticket with additional information:

- Do you have the liveCache & APO running on the same server?

- What is the version of the liveCache instance on your system?

- How did you "complete shutdown of application"?

<

Did you run the following steps:

- stop liveCache in the LC10 transaction;

- stop the application server & Oracle database ( if it's needed);

- close all DBMGUI & dbmcli sessions ( connected to the liveCache);

- stop the 'x_server' on the liveCache server ( 'x_server stop');

>

Please update with the output of the following commands:

Dbmcli -s inst_enum

Dbmcli -s db_enum

Sdbregview -l

-

---

1. What is this services Mean?

***

The vserver process is a communication server process that uses TCP/IP sockets. If the application is running on a separate host, tcp/ip via vserver process is used for the communication to the liveCache .

And the "vserver" process handles the communication between an application running on a remote host (in point of view of the liveCache) and the corresponding liveCache task.

Each connection (liveCache task < > remote application) is handled

by its own "vserver" process.

- number of vserver = number of connections to the liveCache from remote running applications + 1 coordinator(parent)

The niserver is used to connect our support team to the customers using a secure connection. It is of no use outside of SAP installations. And 'x_server start' / 'x_server stop' will also starts up /stops the niserver processes in the SAP environment.

If you've got access to OSS/Service Market Place, then please review the Notes:

820824 FAQ: MaxDB

767598 Available documentation

202344 Setting up SAP DB connection

***

- According your information there are the child processes of the 'vserver' & 'niserver' running on the server.

Please provide output of the following command:

Ps -efe | grep 23636

( to check if the parent process is still running )

Please check, if you have DBMGUI & dbmcli sessions

( connected to the liveCache).

2. Why this services running after the complete shutdown of application?

- May be the 'x_server' was stopped incorrectly.

( review xserver_<server-name>.prt in /sapdb/data/wrk ).

Please check with 'x_server stop' & 'x_server start' commands.

3. is there any bad impact on the server if we power off system during running these services

-If you don't have the parent 'vserver' process running on the server, we need to find the reason, why the child processes of the 'vserver' & 'niserver' still running on the server.

If you are the official SAP customer, I recommend you to create the ticket to SAP on 'BC-DB-LVC' queue.

Thank you and best regards, Natalia Khlopina