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.
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
# haconf -makerw
# hagrp -freeze db2udb_group
# 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