The MaxDB database instance and database tools generate a number of operating system processes.
On Linux systems without NPTL (Native Posix Thread Library), each thread is simulated by a clone process. As a result, in the process list you may find several MaxDB processes with the same name.
MaxDB Processes
Process |
Process |
Function |
- |
niserver |
Part of the X Server, responsible for NI support in SAP systems |
dbanalyzer.exe |
dbanalyzer |
Database Analyzer |
dbmcli.exe |
dbmcli |
Database Manager CLI |
dbmevtdisp.exe |
dbmevtdisp |
Event Dispatcher |
DBMGui3.exe |
- |
Database Manager GUI |
dbmsrv.exe |
dbmsrv |
DBM Server |
dbmsrvscd.exe |
dbmsrvscd |
Event Scheduler |
kernel.exe |
kernel |
Database system kernel Every database instance has its own kernel process. |
loadercli.exe |
loadercli |
Loader |
serv.exe |
vserver |
MaxDB X Server On UNIX/Linux, a new child process is started for each database connection. |
sqlcli.exe |
sqlcli |
SQLCLI |
SQLSto.exe |
- |
SQL Studio |
vmksrv.exe |
vmksrv |
VMAKE server |
wahttp.exe |
wahttp |
MaxDB Web Server |
See also: