Please enter search query.
Search <book_title>...
Cluster Server 7.4.2 Agent for DB2 Installation and Configuration Guide - Linux
Last Published:
2020-06-14
Product(s):
InfoScale & Storage Foundation (7.4.2)
Platform: 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
About running the info agent function to get database information for VCS agent for DB2
You can run the info agent function to return database information. In this example, the info agent function retrieves the database information.
To retrieve database information
- Make the configuration writable:
# haconf -makerw
- Specify the periodic interval in seconds that the info agent function is invoked. The default value of 0 means info agent function is not invoked.
# hatype -modify Db2udb InfoInterval 300
In this command, Db2udb is the name of the DB2 resource type. InfoInterval 300 is the duration (in seconds) after which the info agent function executes the info script. The script gets the information of the processes that the agent monitors.
- Show the requested ResourceInfo value. The following example output shows the processes that the agent monitors for the DB2 resource.
The value needs to be overridden at the resource level using the following command:
# hares -override db2udb3_2 InfoInterval
Note that ResourceInfo refreshes every 300 seconds (five minutes), since you set the InfoInterval to 300 in the previous step.
# hares -value db2udb1 ResourceInfo State Valid Msg PARTITION: 0 PID TTY TIME CMD 413924 - 0:00 db2sysc TS Fri Jan 14 18:11:52 2011
- Make the configuration permanent:
# haconf -dump -makero