IBM Support

Why db2bp processes are orphan process

Troubleshooting


Problem

db2bp processes are shown as orphan processes in ps output. Is this a problem?

Symptom

As shown in the following ps output, the parent process ID of db2bp is 1 (init),
which means the db2bp is an orphan process :
db2inst1@yaba:~> ps -ef|grep db2inst1|grep db2bp
db2inst1 31479 1 0 16:02 pts/1 00:00:00 /home/db2inst1/sqllib/bin/db2bp 31476A1001 5 A
db2inst1 31716 23738 0 16:02 pts/1 00:00:00 grep db2bp

Cause

db2bp is designed to be persistent so that it can maintain connection to DB2 server.
The parent process of db2bp will exit once db2bp process is cloned. Hence db2bp becomes orphan process. This is working as designed and normally does not cause any problems.
However if db2bp processes are not cleaned up properly as they are supposed to be,
please check whether the APAR in Related URL applies to your scenario.

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"DB2 Tools - Troubleshooting","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"10.1;10.5;9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 June 2018

UID

swg21987754

Page Feedback