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
Defining user and group accounts for DB2
Before you install DB2 UDB binaries and create instances, you must define DB2 UDB user and group accounts for each instance on each system.
Note the following requirements:
The IDs for DB2 users and groups must be exactly the same across all cluster nodes.
The DB2 instance owner's home directory must be accessible from each node. This directory is the mount point that the DB2 instance uses. The database that you want to mount must be on shared storage. Create the mount point directory locally on each node, if it does not already exist.
All DB2 user accounts must exist on the local systems. Arctera does not recommend the use of NIS or NIS+ for users, because these services are not highly available. If their service is interrupted, VCS may not be able to work correctly.