dbmevtdisp creates lots of "zombie" processes

[Former Member]

On all of our installation (starting with about 7.6.1 - don't remember exactly), I can see a lot of zombie/defunct proccess started by dbmevtdisp:

# pstree -Gp | more
init(1)─┬─cron(12179)
        ├─dbanalyzer(29083)
        ├─dbmevtdisp(14331)─┬─dbmevtdisp(17655)
        │                   ├─dbmevtdisp(3346)
        │                   ├─dbmevtdisp(7483)
        │                   ├─dbmevtdisp(3437)
        │                   ├─dbmevtdisp(28238)
        │                   ├─dbmevtdisp(7942)
        │                   ├─dbmevtdisp(12409)
        │                   ├─dbmevtdisp(17270)
        │                   ├─dbmevtdisp(17376)
        │                   ├─dbmevtdisp(20242)
        │                   ├─dbmevtdisp(20965)
        │                   ├─dbmevtdisp(20995)
        │                   ├─dbmevtdisp(21304)
        │                   ├─dbmevtdisp(23833)
        │                   ├─dbmevtdisp(24216)
        │                   ├─dbmevtdisp(29256)
        │                   ├─dbmevtdisp(1833)
        │                   ├─dbmevtdisp(3190)
        │                   ├─dbmevtdisp(19376)
        │                   ├─dbmevtdisp(22896)
        │                   ├─dbmevtdisp(22923)
        │                   ├─dbmevtdisp(22965)
        │                   ├─dbmevtdisp(23173)
        │                   ├─dbmevtdisp(23384)
        │                   ├─dbmevtdisp(25419)
        │                   ├─dbmevtdisp(31904)
        │                   ├─dbmevtdisp(7655)
        │                   ├─dbmevtdisp(13950)
        │                   ├─dbmevtdisp(21156)
        │                   └─dbmevtdisp(26918)
        ├─dbmsrv(14333)───dbmsrv(14334)

# ps 3346
  PID TTY      STAT   TIME COMMAND
 3346 ?        Z      0:00 [dbmevtdisp] <defunct>

# ps 22896
  PID TTY      STAT   TIME COMMAND
22896 ?        Z      0:00 [dbmevtdisp] <defunct>

# ps -ef | grep defun | wc -l
33

I have no clue why this process is started by default, the last time I logged on to the system I had > 100 defunc processes.

Is this problem of those "zombies" known?

Regards,

Markus

[former_member229109 · Accepted solution]

Hello Markus,

1) 'dbmevtdisp' is Event Dispatcher MaxDB process.

2) Could you please provide additional information:

What is the current version of the database on your system?

< I would like to see the build too. >

What is the version of the OS of the database server? < OS-Kernel patch ? >

Please update with output of the following commands:

dbmcli -s db_enum

sdbregview -l

xinstinfo <database_name>

dbmcli -d <database_name> -u <dbm_user>,<password> dbm_configget RunEventDispatcher

dbmcli -d <database_name> -u <dbm_user>,<password> param_directget _MAXEVENTTASKS

dbmcli -d <database_name> -u <dbm_user>,<password> auto_extend show

dbmcli -d <database_name> -u <dbm_user>,<password> auto_update_statistics show

dbmevtdisp version

dbmevtdisp list /sapdb/data/wrk/<SID>/dbmsilevt.cfg

dbmevtdisp state -d <database_name> -u <dbm_user>,<password>

3) Documentation about 'Event-Dispatcher' could be found at

https://www.sdn.sap.com/irj/sdn/maxdb -> The Complete MaxDB Documentation Set

Basic Information -> Glossary -> Event Dispatcher

( see more at Tools -> Utilities, "Event Dispatcher" doc )

4) Please check the protocol dbmevtdisp.prt located in the database RUNDIRECTORY.

5) Please review the PTS 1151090 .

Did you have the auto_extend on or auto_update_statistics on in your database when the internal Event Dispatcher was active?

Could you please use the workaround from PTS & please check, if Event Dispatcher zombies (defunct processes) will be NOT shown up in process overview after that.

Thank you and best regards, Natalia Khlopina

[markus_doehr2 · Accepted solution]

Hi Natalia,

> ) 'dbmevtdisp' is Event Dispatcher MaxDB process.

>

> uld you please provide additional information:

>

> ersion of the database on your system?

> < I would like to see the build too. >

[code]$ dbmcli db_enum

OK

P01 /sapdb/P01/db 7.6.03.08 fast running

P01 /sapdb/P01/db 7.6.03.08 quick offline

P01 /sapdb/P01/db 7.6.03.08 slow offline

P01 /sapdb/P01/db 7.6.03.08 test offline[/code]

> hat is the version of the OS of the database server?

> < OS-Kernel patch ? >

[code]# SPident

CONCLUSION: System is up-to-date!

found SLES-9-x86_64-SP3

1. uname -a

Linux XXXXXXXX 2.6.5-7.244-smp #1 SMP Mon Dec 12 18:32:25 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux[/code]

[code]$ sdbregview -l

DB Analyzer /sapdb/programs 7.6.03.08 64 bit valid

Server Utilities /sapdb/programs 7.6.03.08 64 bit valid

PCR 7300 /sapdb/programs 7.3.00.58 valid

PCR 7301 /sapdb/programs 7.3.01.21 valid

PCR 7500 /sapdb/programs 7.5.00.46 64 bit valid

SAP Utilities /sapdb/programs 7.6.03.08 64 bit valid

Base /sapdb/programs 7.6.03.08 64 bit valid

Redist Python /sapdb/programs 7.6.03.08 64 bit valid

JDBC /sapdb/programs 7.6.03.03 valid

Messages /sapdb/programs MSG 0.5603 valid

ODBC /sapdb/programs 7.6.03.08 64 bit valid

Database Kernel /sapdb/P01/db 7.6.03.08 64 bit valid

Loader /sapdb/programs 7.6.03.08 64 bit valid

SQLDBC /sapdb/programs 7.6.03.08 64 bit valid

SQLDBC 76 /sapdb/programs 7.6.03.08 64 bit valid

Fastload API /sapdb/programs 7.6.03.08 64 bit valid

$ xinstinfo P01

IndepData : /sapdb/data

IndepPrograms : /sapdb/programs

InstallationPath : /sapdb/P01/db

Kernelversion : KERNEL 7.6.03 BUILD 008-123-159-187

Rundirectory : /sapdb/data/wrk/P01

$ dbmcli -U c dbm_configget RunEventDispatcher

OK

yes

$ dbmcli -U c param_directget _MAXEVENTTASKS

OK

_MAXEVENTTASKS 2

$ dbmcli -U c auto_extend show

OK

OFF

$ dbmcli -U c auto_update_statistics show

OK

ON

$ dbmevtdisp version

MaxDB Event Dispatcher, Version 7.6.03.08

Copyright 2000-2007 by SAP AG

$ dbmevtdisp list /sapdb/data/wrk/P01/dbmsilevt.cfg

OK

ID 1

Condition: ((Name == "UPDSTATWANTED"))

Command: dbmcli -d $DBNAME$ -u $DBMUSERPW$ sql_updatestat_per_systemtable

$ dbmevtdisp state -d P01 -U c

OK

[/code]

[...]

>

> 4) Please check the protocol dbmevtdisp.prt located

> in the database RUNDIRECTORY.

[...]

[code]2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name ERROR not dispatched (count 285)

2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name ERROR not dispatched (count 286)

2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name ERROR not dispatched (count 287)

2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name ERROR not dispatched (count 288)

2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name ERROR not dispatched (count 289)

2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name ERROR not dispatched (count 290)

2007-10-15 19:04:52 0x000037fb INF 6 DBMEd event with name BACKUPRESULT not dispatched (count

291)

2007-10-15 23:29:38 0x000037fb INF 6 DBMEd event with name AUTOSAVE not dispatched (count 292

)

2007-10-15 23:30:09 0x000037fb INF 6 DBMEd event with name AUTOSAVE not dispatched (count 293

)

2007-10-15 23:30:09 0x000037fb INF 6 DBMEd event with name AUTOSAVE not dispatched (count 294

)

[/code]

> 5) Please review the PTS 1151090 .

> Did you have the auto_extend on or

> auto_update_statistics on in your database when the

> internal Event Dispatcher was active?

> Could you please use the workaround from PTS &

> please check, if Event Dispatcher zombies (defunct

> processes) will be NOT shown up in process overview

> after that.

This PTS seems to be the cause of the problem. After stopping and starting auto_update_statistics the zombies are gone.

Is that something that needs to be done regularly until this is fixed (in some build)?

Thank you for analyzing!!

Regards,

Markus

[former_member229109 · Accepted solution]

Hello Markus, Thank you for the update.

According the provided by you information your case is known and reported in PTS 1151090. The issue planned to be fixed as of database version 7.6.05.01.

In your case the internal Event Dispatcher was active (auto_update_statistics was on) and events were being dispatched.

If you have the auto_update_statistics on in your dabase, please check time to time if

Event Dispatcher zombies (defunct processes) show up in process overview, then you could use the workaround before the database will be updated.

Please review the information in PTS at www.sapdb.org/webpts -> search by given number 1151090.

Regards, Natalia Khlopina