Learn more about the DB2 Universal Database process (3)

Example

The following example shows the output that may be obtained when running the ps-ef command on AIX:

After db2start:
Root 49504 1 0 13:13:07-db2wdog
Db2inst1 22142 49180 0 13:13:10-db2gds
Db2inst1 43072 49180 0 13:13:17-db2syslog
Db2inst1 45294 74134 0 12:12:43 pts/2/usr/bin/ksh
Db2inst1 49180 49504 0 13:13:10-db2sysc
Db2inst1 55920 49180 0 13:13:19-db2resync
Db2inst1 59012 22142 0 13:13:19-db2srvlst
Db2inst1 60680 49180 0 13:13:17-db2ipccm

The Database Manager configuration file has the following settings, which affect the process you first saw:

Max number of existing agents (MAXAGENTS) = 200
Agent pool size (NUM_POOLAGENTS) = 100 (calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0

Because NUM_INITAGENTS is 0, no "db2agent (idle)" process is displayed at db2start. If you set NUM_INITAGENTS to 5 before running the db2agent, the following additional processes are displayed:

Db2inst1 35542 59814 0 16:25:57-db2agent (idle)
Db2inst1 43096 59814 0 16:25:57-db2agent (idle)
Db2inst1 49628 59814 0 16:25:57-db2agent (idle)
Db2inst1 58170 59814 0 16:25:57-db2agent (idle)
Db2inst1 64012 59814 0 16:25:57-db2agent (idle)
Example

The following example shows the output that may be obtained when running the ps-ef command on AIX:

After db2start:
Root 49504 1 0 13:13:07-db2wdog
Db2inst1 22142 49180 0 13:13:10-db2gds
Db2inst1 43072 49180 0 13:13:17-db2syslog
Db2inst1 45294 74134 0 12:12:43 pts/2/usr/bin/ksh
Db2inst1 49180 49504 0 13:13:10-db2sysc
Db2inst1 55920 49180 0 13:13:19-db2resync
Db2inst1 59012 22142 0 13:13:19-db2srvlst
Db2inst1 60680 49180 0 13:13:17-db2ipccm

The Database Manager configuration file has the following settings, which affect the process you first saw:

Max number of existing agents (MAXAGENTS) = 200
Agent pool size (NUM_POOLAGENTS) = 100 (calculated)
Initial number of agents in pool (NUM_INITAGENTS) = 0

Because NUM_INITAGENTS is 0, no "db2agent (idle)" process is displayed at db2start. If you set NUM_INITAGENTS to 5 before running the db2agent, the following additional processes are displayed:

Db2inst1 35542 59814 0 16:25:57-db2agent (idle)
Db2inst1 43096 59814 0 16:25:57-db2agent (idle)
Db2inst1 49628 59814 0 16:25:57-db2agent (idle)
Db2inst1 58170 59814 0 16:25:57-db2agent (idle)
Db2inst1 64012 59814 0 16:25:57-db2agent (idle)
Db2agent (SAMPLE) is changed to db2agent (idle ). This is because NUM_POOLAGENTS is set to greater than 0, which means that the proxy is still allocated to the buffer pool, although it is idle in time and space. If NUM_POOLAGENTS is set to 0, the db2agent process does not run after "connect reset.

The database configuration file of the SAMPLE database has the following settings:

Number of asynchronous page cleaners (NUM_IOCLEANERS) = 1
Number of I/O servers (NUM_IOSERVERS) = 3

Note that there are three db2pfchr processes, which correspond to the NUM_IOSERVERS value. One db2pclnr process corresponds to the NUM_IOCLEANERS value.

Summary

Many other processes may or may not appear, depending on different DB2 behavior and configuration settings. We demonstrated how to investigate which processes are running, what information these processes are displaying, and how they are affected by database settings. Now you can use this knowledge to improve the ability to manage DB2 databases.