Cluster Server 7.4.2 Agent for DB2 Installation and Configuration Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Linux
  1. Introducing the Cluster Server Agent for DB2
    1.  
      About the Cluster Server Agent for DB2
    2.  
      How Cluster Server Agent for DB2 makes DB2 highly available
    3.  
      How the DB2 agent supports intelligent resource monitoring
    4.  
      Supported software for VCS agent for DB2
    5. About agent functions for VCS Agent for DB2
      1.  
        About the online agent function for VCS agent for DB2
      2.  
        About the offline agent function for VCS agent for DB2
      3.  
        About the monitor agent function for VCS agent for DB2
      4.  
        About the clean agent function for VCS agent for DB2
      5.  
        About the info agent function for VCS agent for DB2
      6.  
        About the action agent function for VCS agent for DB2
      7. About IMF Integration functions for VCS Agent for DB2
        1.  
          About the imf_init function for VCS agent for DB2
        2.  
          About the imf_register function for VCS agent for DB2
        3.  
          About the imf_getnotification function for VCS agent for DB2
      8.  
        About running the info agent function to get database information for VCS agent for DB2
    6.  
      Typical DB2 configuration in a Cluster Server
    7.  
      Road map for setting up DB2 UDB in a VCS environment
  2. Installing and configuring DB2
    1. VCS requirements for installing DB2
      1.  
        Preparing to install DB2 UDB non-MPP versions
      2.  
        Preparing to install DB2 UDB MPP versions
      3.  
        Creating the file systems for non-MPP instances for DB2
      4.  
        Creating the shared file systems for MPP instances for DB2
      5. Defining user and group accounts for DB2
        1.  
          Creating user group accounts for DB2
        2.  
          Adding user accounts for DB2 on Linux
    2.  
      Installing DB2 in a VCS environment
    3. Setting up the DB2 configuration
      1.  
        Checking /etc/services for DB2
      2.  
        Enabling password less communication for DB2 users among all cluster nodes
      3.  
        Modifying the $DB2InstHome/sqllib/db2nodes.cfg file for DB2
      4.  
        Confirming the DB2 installation
  3. Installing and removing the Cluster Server Agent for DB2
    1.  
      Before you install or upgrade the VCS Agent for DB2
    2.  
      Installing the VCS agent for DB2 software
    3.  
      Upgrading the VCS Agent for DB2
    4.  
      Disabling the VCS Agent for DB2
    5.  
      Removing the VCS Agent for DB2
  4. Configuring VCS service groups for DB2
    1.  
      About configuring service groups for DB2
    2. About DB2 configurations in VCS
      1.  
        Non-MPP configuration service groups for DB2
      2. MPP configuration service groups for DB2
        1.  
          Parallel CVM service group for MPP configuration for DB2
        2.  
          Failover service group for MPP configuration for DB2
    3. Before configuring the service group for DB2
      1.  
        Importing the Db2udbTypes.cf file
    4. Configuring the VCS Agent for DB2 from Cluster Manager (Java Console)
      1.  
        Adding service group for DB2 MPP using the Cluster Manager (Java Console)
      2.  
        Adding a service group for DB2 non-MPP with the Cluster Manager (Java Console)
    5. Configuring the VCS Agent for DB2 by editing the main.cf file
      1.  
        Configuring the agent to use the DB2 MPP configuration
      2.  
        Configuring the agent to use the DB2 non-MPP configurations
      3.  
        Verifying the configuration for VCS agent for DB2
    6. Setting up in-depth monitoring of a DB2 instance
      1.  
        Enabling in-depth monitoring of a DB2 instance
      2.  
        Enabling in-depth monitoring from the command line for DB2
      3. Enabling and disabling intelligent resource monitoring for Db2udb resource
        1.  
          Administering the AMF kernel driver
      4.  
        Handling DB2 error codes during in-depth monitoring
      5.  
        Disabling in-depth monitoring for DB2
  5. Administering VCS service groups for DB2
    1.  
      About administering service groups for DB2
    2.  
      Bringing the DB2 service group online
    3.  
      Taking the DB2 service group offline
    4.  
      Switching the DB2 service group
    5.  
      Disabling the agent for DB2
  6. Appendix A. Troubleshooting Cluster Server Agent for DB2
    1.  
      Creating a db2profile for environment variables for DB2
    2.  
      Setting the RestartLimit attribute for VCS agent for DB2
    3.  
      Partition/Node switch-over scenarios for DB2 in MPP mode
  7. Appendix B. Resource type information for Cluster Server Agent for DB2
    1. About the resource type definitions for DB2
      1.  
        DB2 UDB type definition file: Db2udbTypes.cf on Linux
  8. Appendix C. Resource type attributes for DB2
    1.  
      About the Db2udb resource types and attribute definitions
  9. Appendix D. Sample configurations
    1. Sample configuration files for VCS agent for DB2 on Linux
      1.  
        Non-MPP main.cf configuration for VCS agent for DB2 on Linux
      2.  
        MPP main.cf configuration for VCS agent for DB2 on Linux

Enabling in-depth monitoring from the command line for DB2

You can dynamically configure in-depth monitoring. Veritas recommends that you successfully run DB2 with the agent's default (shallow) monitoring before you start the in-depth monitoring. In the MPP configuration, make sure the database can be accessible locally by the database partition.

You need to have custom monitoring scripts. Refer to the following table for information on the Indepth Monitor attribute:

See About the Db2udb resource types and attribute definitions.

To start the in-depth monitor for a given instance

  1. Make the VCS configuration writable:
    # haconf -makerw
  2. Freeze the service group so VCS does not perform actions automatically based on an incomplete reconfiguration:
    # hagrp -freeze db2udb_group
  3. Enable in-depth monitoring using the command:
    # hares -modify resource DatabaseName name

    # hares -modify resource IndepthMonitor 1

    For example:

    # hares -modify db2udb DatabaseName SAMPLE
# hares -modify db2udb IndepthMonitor 1
# haconf -dump -makero
# hagrp -unfreeze db2udb_group