InfoScale™ 9.0 Cluster Server Agent for DB2 Installation and Configuration Guide - Linux
- Introducing the Cluster Server Agent for DB2
- About agent functions for VCS Agent for DB2
- About IMF Integration functions for VCS Agent for DB2
- Installing and configuring DB2
- VCS requirements for installing DB2
- Setting up the DB2 configuration
- Installing and removing the Cluster Server Agent for DB2
- Configuring VCS service groups for DB2
- About DB2 configurations in VCS
- Before configuring the service group for DB2
- Configuring the VCS Agent for DB2 from Cluster Manager (Java Console)
- Configuring the VCS Agent for DB2 by editing the main.cf file
- Setting up in-depth monitoring of a DB2 instance
- Administering VCS service groups for DB2
- Appendix A. Troubleshooting Cluster Server Agent for DB2
- Appendix B. Resource type information for Cluster Server Agent for DB2
- Appendix C. Resource type attributes for DB2
- Appendix D. Sample configurations
Enabling in-depth monitoring from the command line for DB2
You can dynamically configure in-depth monitoring. Arctera 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 accessed locally by the database partition.
Copy the required custom monitoring scripts from /etc/VRTSagents/ha/conf/Db2udb/sample_db2udb
to /opt/VRTSagents/ha/bin/Db2udb
.
In case of a single-node cluster configuration, make sure to copy the monitor_custom_db2inst1_0
script and set its file permissions to 755 by using the following command:
# chmod 755 /opt/VRTSagents/ha/bin/Db2udb/monitor_custom_db2inst1_0
See About the Db2udb resource types and attribute definitions.
To start the in-depth monitor for a given instance
- Make the VCS configuration writable:
# haconf -makerw
- Freeze the service group so VCS does not perform actions automatically based on an incomplete reconfiguration:
# hagrp -freeze db2udb_group
- 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