Enabling in-depth monitoring from the command line for DB2

Last published : Sep 11, 2026
You can dynamically configure in-depth monitoring. Veritas recommends that you successfully run DB2 with the agent's default (shallow) monitoring before you start the in-depth monitoring. In the MPP configuration, make sure the database can be accessible locally by the database partition.
For locales other than English, add the following lines to the $INSTHOME/sqllib/userprofile file.
The following example adds Japanese language support:
export LANG=Ja_JP
You need to have custom monitoring scripts. Refer to the following table for information on the Indepth Monitor attribute:
See About the Db2udb resource types and attribute definitions.
To start the in-depth monitor for a given instance
  1. Make the VCS configuration writable:
    \# haconf -makerw
    1. Freeze the service group so VCS does not perform actions automatically based on an incomplete reconfiguration:
    \# hagrp -freeze db2udb_group
  2. Enable in-depth monitoring using the command:
    \# hares -modify resource DatabaseName name\# hares -modify resource IndepthMonitor 1
For example:
\# hares -modify db2udb DatabaseName SAMPLE
\# hares -modify db2udb IndepthMonitor 1
\# haconf -dump -makero
\# hagrp -unfreeze db2udb_group