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
Checking /etc/services for DB2
On each system in the cluster, use the more command to check the file /etc/services.
Remember to perform the following:
Make sure each partition has a port number assigned. The number of reserved ports depends on the number of partitions.
Make sure that no other services use the ports. Manually assign new numbers if necessary.
Make sure all systems in the cluster have the same entries in the /etc/services file.
The following is an example for two DB2 instances: db2inst1 and db2inst2. Both instances have two partitions each. Each instance requires two ports plus one port per partition, hence four lines per instance.
# more /etc/services DB2_db2inst1 60000/tcp DB2_db2inst1_1 60001/tcp DB2_db2inst1_2 60002/tcp DB2_db2inst1_END 60003/tcp DB2_db2inst2 60004/tcp DB2_db2inst2_1 60005/tcp DB2_db2inst2_2 60006/tcp DB2_db2inst2_END 60007/tcp
Inspect the file and verify that no duplicate port numbers exist.