IBM Support

How to stop the db2acd (db2hmon) process in DB2 Version 9.x

Technote (FAQ)


The db2acd process in DB2 Version 9.x will still run when database configuration parameters HEALTH_MON and AUTO_* are set to OFF


DB2® Version 9.x process db2acd is a single process that runs in parallel for both health monitor and automatic maintenance functions.
When HEALTH_MON=OFF and AUTO_* database configuration parameters are set to OFF, db2acd will still wakeup approximately every 2 hours to check for active database automatic maintenance.


Setting registry variable DB2_FMP_COMM_HEAPSZ to 0 will prevent db2acd from starting. This means no set is created, and as a result, no fenced routines can be invoked. It also means that the health monitor and the automatic database maintenance functionality (such as automatic backups, statistics collection, and REORG) will be disabled since this functionality relies on the fenced routine infrastructure.

If DB2_FMP_COMM_HEAPSZ is not (cannot be) set to 0, we cannot disable db2acd completely due to its original design. The db2 system controller (db2sysc process) will restart db2acd process if it is killed and this checking is done every 15 minutes.

Note: Setting DB2_FMP_COMM_HEAPSZ=0 will prevent ALL non-SQL routines from executing. This includes built-in DB2 routines and user routines as well!!

For more detail on setting DB2 registry variable and DB2 Database Manager Configuration, please see section "Related Information".

Related information

Changes in the db2hmon process in DB2 UDB Version 8.2
How to stop the db2hmon process in DB2 Version 8.2
db2set - DB2 profile registry command
Update Database Manager Configuration

Document information

More support for: DB2 for Linux, UNIX and Windows
Database Objects/Config - Instance

Software version: 9.1, 9.5, 9.7

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1259046

Modified date: 04 March 2008