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
Configuring the VCS Agent for DB2 by editing the main.cf file
The VCS agent for DB2 comes with three sample VCS configuration files, which are in the /etc/VRTSagents/ha/conf/Db2udb/sample_db2udb directory.
The samples are as follows:
A single-partition instance configuration
A multi-partition instance SMP configuration
A multi-partition instance MPP configuration.
The appropriate file can be used as reference to directly modify your present main.cf configuration file. When you use this method, you must stop and restart VCS to implement the configuration.
After you complete these steps, go to one of the following sections that describe configuring the agent.
To prepare to edit the main.cf file
- Log on to System A as root.
- Save your existing configuration to prevent any changes while you modify the main.cf file:
# haconf -dump -makero
- Make sure to stop VCS while you edit main.cf. Use the hastop command to stop the VCS engine on all systems and leave the resources available:
# hastop -all -force
- Make a backup copy of the main.cf file:
# cd /etc/VRTSvcs/conf/config # cp main.cf main.cf.orig