Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Agent for DB2 Installation and Configuration Guide - Linux
Last Published:
2025-04-14
Product(s):
InfoScale & Storage Foundation (9.0)
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
Upgrading the VCS Agent for DB2
To upgrade without saving previous configuration information you must disable the agent, remove it, and reinstall it.
The steps to upgrade and re-use previous configuration information is as follows:
To upgrade from DB2 agent
- Disable and remove the agent.
For more information see the following:
Disabling the agent for DB2
Removing the agent for DB2 UDB
- From the disc that has the HA agent for DB2, add the new package.
- Make sure that you have copied the Db2udbTypes.cf file from the /etc/VRTSagents/ha/conf/Db2udb/ directory to the /etc/VRTSvcs/conf/config directory.
Make sure to update the newly copied Db2udbTypes.cf file with all the type-level changes that you had made to the older Db2udbTypes.cf file. For example, if you had changed the value of the MonitorInterval attribute from the default 60 to 120 seconds, the Db2udbTypes.cf file gets updated. You must apply these type-level changes manually to the newly copied Db2udbTypes.cf file.
- To continue to use in-depth monitoring, use the custom monitoring sample script or any user-defined scripts.