Enabling in-depth monitoring from the command line
Prev Setting up in-depth monitoring of DB2 UDB instance Next

Enabling in-depth monitoring from the command line

You can dynamically configure in-depth monitoring. Symantec recommends that you successfully run DB2 UDB 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 Table: Optional attributes for the agent for DB2.

To start the in-depth monitor for a given instance

  1. Make the VCS configuration writable:

    # haconf -makerw

  2. Freeze the service group so VCS does not perform actions automatically based on an incomplete reconfiguration:

    # hagrp -freeze db2udb_grp1

  3. 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_grp1
Prev Up Next
Enabling in-depth monitoring of DB2 UDB instance Home Handling DB2 error codes during in-depth monitoring