To enable access to a special database, the DB2 instance process responsible 

for the database must be running on the DB2 server. When an instance process 

is started, several processes are created and interact with each other to maintain 

connected applications and the database. There are several background 

processes in DB2 that are pre started, others start on a need only basis. This 

section explains some of the important background processes.

DB2 UDB processes

The DB2 UDB server activities are performed by Engine Dispatchable Units 

(EDU) that are defined as background processes on Linux systems.

Some DB2 background processes are started with the instance, and others are 

initialized when the database is activated by a connection. Figure 1 3 shows the 

necessary background processors of the DB2 UDB server at the instance, 

application, and database level. In the following sections, we discuss some of the 

important processes on the respective level.

Per Instance

Per Application

Per Database

db2pfchr

db2agent

db2pclnr

db2ipccm

db2agent

db2dlock

db2tcpcm

db2agent

db2loggr

db2loggw

Per Application

Per Database

db2pfchr

db2ipccm

db2agent

db2pclnr

db2agent

db2dlock

db2tcpcm

db2agent

db2loggr

db2loggw

db2gds

db2sysc

db2wdog

db2fmtlg

db2syslog

Figure 1 3   DB2 processes

8 

MySQL to DB2 UDB Conversion Guide