Setup requirements in a UNIX environment for DB2 UDB EE and EEE

Setup requirements depend on the operating system environment and version of DB2 that you are running. The following sections discuss the setup steps and requirements for PATROL for DB2 UDB.

Following are the setup requirements for DB2 UDB EE and DB2 UDB EEE in UNIX environment:

• For a single partitioned DB2 EE environment install the DB2UDB.kml on the physical node, where the PATROL Agent and DB2 UDB instance is present.
• For a multi-partitioned DB2 EEE environment:
  • If the PATROL Agent is installed on each physical node where the DB2 database is spread, install the DB2UDB_EEE.kml on each physical node. In this scenario, start and configure the PATROL Agent for DB2 UDB monitoring only on one physical node. The KM collects data for each physical node by creating a separate channel on each node.
  • If the PATROL Agent is installed on one physical node and is mounted across other physical nodes, install DB2UDB_EEE.kml only on the primary physical node where the Agent is installed. In this scenario, start and configure the PATROL Agent for DB2 UDB monitoring only on the primary physical node. The KM collects data for each physical node by creating a separate channel on each node.
• The parameters under all application classes in the DB2_DB container or the DB2EEE_DB container will appear offline. To make them online and to collect data, you need to do one of the following for each database being monitored:
  • Create a connection to the database using the following command:
    
    db2 connect to databaseName
  • Activate the database using the following command:
    
    db2 activate database databaseName
• To monitor tablespaces, log on as the instance owner and set the bufferpool monitor switch, DFT_MON_BUFPOOL to ON by entering the following command:
  db2 update dbm cfg using DFT_MON_BUFPOOL ON

 Setup requirements for monitoring DB2 UDB EEE in UNIX

If you are going to monitor DB2 UDB EEE in partitioned UNIX environment, it is recommended that the following conditions are set.

• The directory containing the PATROL product must be accessible from all systems that are part of the DB2 multinode environment with the configure default account user.
• You must have the user account - Configure Default Account on all the physical nodes where the KM and Agent is installed. This user should have the same user name, user ID, group ID, group name on all the physical nodes.
• You must be able to communicate across nodes. For the DB2 UDB EEE to start UNIX services across nodes, you must ensure that the default account user can execute any command on all nodes defined in the db2nodes.cfg file, using the rshcommand. To accomplish this task, perform one of the following actions:
  • Create an .rhosts file in the $HOME directory ($HOME/.rhosts ).

  • Create a hosts.equiv file in the etc directory (/etc/host.equivfile).

    InformationThe contents of an .rhosts file might look as follows: everestn1.bmc.com donna everestn2.bmc.com donna everestn3.bmc.com donna
    
    Verify that the KM is installed correctly, and ensure that you have configured the default account discussed in Setting up default accounts for EE and EEE.
    
    The KM uses $PATROL_HOME/bin/db2km_services.eee to add entries in the*/etc/services* file. Ensure that this file is owned by root and has file permissions set as follows:
    
    -rwsr-sr-x
    
    If the file is not owned by root or does not have the correct permissions, you can issue the following UNIX commands to assign root ownership and set permissions:chown root db2km_services.eeechmod u+s db2km_services.eee
    
    In an rsh enabled environment, use the To Configure the Default Ports for a UNIX System task to configure the TCP/IP ports. In an rsh disabled environment, use Disabling rsh Dependency in a High-security Environment task to configure TCP/IP ports.

  UNIX requirements for RSH

1. Ensure that as the PATROL user or Configure Default Account User you can perform the following tasks successfully on each physical node:
   1. rsh localHostName ls
   2. rsh remoteHostName ls
      
      The above commands should not ask for password authentication.

 UNIX requirements for SSH

Ensure that as the PATROL user or Configure Default Account User you can perform the following tasks successfully on each physical node:

• ssh localHostName ls
• ssh remoteHostName ls

The above commands should not ask for password authentication.

However, the KM can be configured to monitor the environment in which rsh is disabled and/or LOGIN is disabled. Monitoring in a rsh disabled environment requires significant manual configuration and loss of functionality. See Configuring an environment in which rsh is disabled or rsh and login disabled (No Protocol Used)