Question & Answer
Question
How to turn off IBM DB2 Health monitor ?
Cause
The autonomic computing daemon (db2acd) hosts the health monitor and automatic maintenance utilities. If you kill the db2acd, it will be restarted by the db2sysc process. There is always at least one db2acd process running for each DB2 instance, Furthermore, only setting HEALTH_MON to OFF does not actually turn off the health monitor.
Answer
Here are the steps to disable health monitor if you do not need to use to use it at all:
db2 update dbm cfg using health_mon off
db2 update db cfg for <dbname> using auto_maint off
db2 update db cfg for <dbname> using auto_tbl_maint off
db2 update db cfg for <dbname> using AUTO_RUNSTATS off
db2 update db cfg for <dbname> using AUTO_STATS_PROF off
db2 update db cfg for <dbname> using AUTO_REORG off
db2 update db cfg for <dbname> using AUTO_DB_BACKUP off
db2 "update alert cfg for databases using db.apps_waiting_locks set thresholdschecked no"
db2 "update alert cfg for databases using db.auto_storage_util set thresholdschecked no"
db2 "update alert cfg for databases using db.catcache_hitratio set thresholdschecked no"
db2 "update alert cfg for databases using db.db_backup_req set thresholdschecked no"
db2 "update alert cfg for databases using db.db_heap_util set thresholdschecked no"
db2 "update alert cfg for databases using db.db_op_status set thresholdschecked no"
db2 "update alert cfg for databases using db.deadlock_rate set thresholdschecked no"
db2 "update alert cfg for databases using db.fed_nicknames_op_status set thresholdschecked no"
db2 "update alert cfg for databases using db.fed_servers_op_status set thresholdschecked no"
db2 "update alert cfg for databases using db.hadr_delay set thresholdschecked no"
db2 "update alert cfg for databases using db.hadr_op_status set thresholdschecked no"
db2 "update alert cfg for databases using db.lock_escal_rate set thresholdschecked no"
db2 "update alert cfg for databases using db.locklist_util set thresholdschecked no"
db2 "update alert cfg for databases using db.log_fs_util set thresholdschecked no"
db2 "update alert cfg for databases using db.log_util set thresholdschecked no"
db2 "update alert cfg for databases using db.max_sort_shrmem_util set thresholdschecked no"
db2 "update alert cfg for databases using db.pkgcache_hitratio set thresholdschecked no"
db2 "update alert cfg for databases using db.shrworkspace_hitratio set thresholdschecked no"
db2 "update alert cfg for databases using db.sort_shrmem_util set thresholdschecked no"
db2 "update alert cfg for databases using db.spilled_sorts set thresholdschecked no"
db2 "update alert cfg for databases using db.tb_reorg_req set thresholdschecked no"
db2 "update alert cfg for databases using db.tb_runstats_req set thresholdschecked no"
Some points to be noted here :
You need to confirm if you need AUTO_RUNSTATS, AUTO_REORG, or AUTO_BACKUP features of Automatic maintenance (ATM). You can disable HEALTH_MON but if you still need the ATM features, the following updates should be avoided :
db2 update db cfg for <dbname> using auto_maint off
db2 update db cfg for <dbname> using auto_tbl_maint off
db2 update db cfg for <dbname> using AUTO_RUNSTATS off
db2 update db cfg for <dbname> using AUTO_STATS_PROF off
db2 update db cfg for <dbname> using AUTO_REORG off
db2 update db cfg for <dbname> using AUTO_DB_BACKUP off
ATM tasks do not depend on the database manager configuration settings of HEALTH_MON, which means, even if you disable the HEALTH_MON parameter and AUTO_MAINT, AUTO_TBL_MAINT, AUTO_RUNSTATS parameters are enabled, AUTO_RUNSTATS will still work.
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21646336