Monitoring DB2 agents and applications

DB2 Universal Database applications and agents are not automatically discovered in PATROL for DB2 UDB unless you configure application discovery settings. In DB2 UDB EEE, you must also configure application discovery for subagents to be discovered. For DB2 Universal Database 7.1 and later, you can configure the level at which the KM monitors applications.

Additionally, you can configure PATROL for DB2 UDB to save information that correlates each DB2 application with the coordinating DB2 agent or agents for the application. You can also use PATROL for DB2 UDB to change the default files and location in which the current and historical agent and application correlation information is saved.

Finally, you can use the PATROL History Loader product to access this information to extract the history data stored in a DB2 database for each agent.

Note

For information about running the application reports, see Managing DB2 applications and agents, or for DB2 UDB EEE see Managing DB2 applications, agents, and subagents.

Reduced number of activated parameters

The majority of DB2_AGENT, DB2EEE_AGENT, and DB2EEE_SUBAGENT parameters are inactive at installation. In addition to configuring application discovery, be sure to set all parameters that are relevant to your DB2 Universal Database environment to Active.

By default the majority of the parameters in the following application classes are set to Inactive:

  • DB2_AGENT
  • DB2EEE_AGENT
  • DB2EEE_SUBAGENT

This should reduce the overhead in instances where a large number of applications exist. You should review all the parameters in these application classes to determine the relevant parameters to your DB2 UDB environment before setting them to Active.

Note

Several DB2_AGENT instances are discovered under the DB2_APP application class. The label for each instance of DB2_AGENT application class displays the identification number of the agent. The label for the DB2 application under the DB2_APP application is the username, application name, and application identification number.

The following table lists the parameters in these application classes that are still set to Active.The [confluence_table-plus] macro is a standalone macro and it cannot be used inline.

To set up the level of monitoring for application discovery

Note

This option is valid only for DB2 Universal Database 7.1 and later.

  1. From the SETUP menu, select Configuration > Configure Application Discovery.
  2. In the Configure KM Application Discovery Settings for DB2 window, select one of the following options:
    • Suspend Discovery of Applications (default)
    • Discover all Applications
    • Discover Selected Applications Specify the application name or a string in the Enter Complete or Partial Application Names box. If you select this option, you can select the option for the KM to monitor an application that Contains or Does NOT contain the string or application name.
    • Discover Top Applications Specify a subset of applications for the KM to monitor in the Number of Applicationsbox and select one of the following parameters:
      • CPUTimebyAgent
      • CPUTimebyStmt

      • ApplIdleTime

        Note

        You can enter any number of applications to discover. Because the KM creates objects for each application, however, you should specify a number fewer than 100. The larger the number that you enter, the more system resources required by the PATROL Agent.

To save correlation information about DB2 agents and applications

  1. From the SETUP menu, select Configuration > Configure Application Discovery.
  2. In the Configure KM Application Discovery Settings for DB2 window, select the Enable DB2 Agent/Application Correlation.
    The KM saves the following information for each agent:
    • Agent ID
    • Authorization ID
    • Agent Instance Name
    • Application Name
    • Application ID
    • Application Process ID

To change the correlation information default files

In the Configure KM Application Discovery Settings for DB2 window, change the directory path in one or both of the following boxes:

  • Location of Current Agent/Application File
     By default, the path is $HOME/db2kmapp.cur (for UNIX) or %DB2PATH%\instance\db2kmapp.cur (for Windows NT).

  • Location of History Agent/Application File
     By default, the path is $HOME/db2kmapp.hst (for UNIX) or %DB2PATH%\instance\db2kmapp.hst(for Windows NT).

    Note

    The DB2 default account used to configure the DB2 DBM instance must have write permission to the directory path of the default files.

    The variable instance is the name of the instance for which you are configuring default settings.

To access history data per agent by using the PATROL History Loader

  1. Enable DB2 agent/application correlation by using the option described on step 2.
  2. Configure the PATROL History Loader to extract PATROL history data and load it into a DB2 database. See the PATROL History Loader User Guide for more information about this process.
  3. Using a user-supplied program, build primary keys out of the agent and application correlation data stored in the agent and application correlation files. From these primary keys, you can write a DB2 application program to query the database to analyze trends and to complete capacity planning for each DB2 application on the system that you are monitoring.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*