Configuring discovery options

To optimize the use of system resources during discovery, some of the discovery phase is optional. Depending on the complexity of your environment, you can select to discover or suspend discovery of various items as needed.

The following items are not discovered by default in PATROL for DB2 UDB.

DB2 application discovery in DB2 UDB

In the DB2 Universal Database, DB2 application discovery is optional. You must configure application discovery in the SETUP menu if you want your DB2 applications to be discovered.

To configure DB2 application discovery

1. Right-click DB2_SETUP (or DB2EEE_SETUP for EEE), and select Configuration > Configure Application Discovery.
2. From the Configure KM Application Discovery Settings window, you can select one of the following options:
   • Suspend Discovery of Applications (default)
   • Discover all Applications
   • Discover Selected Applications
   • Discover Top Applications
     
     See To set up the level of monitoring for application discovery for details.

 Remote database discovery in DB2 UDB EE

In the DB2 Universal Database EE component, remote database discovery is optional. You must configure remote database discovery in the SETUP menu if you want your remote databases to be discovered.

 Remote database discovery limitations for SYSADMIN, SYSCTRL, SYSMAINT

Keep in mind the following limitations when you set up remote database discovery:

• The following features are not available when you discover remote databases:
  • backup and restore menu commands
  • monitoring of SMS tablespaces (only the TblspState, PhyReads, and PhyWrites parameters are monitored)
  • monitoring of backups directory (BackupCount parameter)
  • monitoring of log files and history recovery files
  • the SQL Viewer
  • the SQL Explain
  • the SQL processor
  • advanced performance monitoring
  • deadlock detection
  • LogFSFreeSpace and LogFSPctUsed parameters
• Remote database discovery is available only in the PATROL KM for DB2 UDB Extended Edition and is not available in the PATROL KM for DB2 UDB Enterprise - Extended Edition KM.

To configure remote database discovery in DB2 UDB EE

1. Right-click on DB2_SETUP, and select Configuration > Configure KM Defaults > DB2 Instance Settings.
    If more than one instance exists, the Configure KM Defaults window appears.
2. Select the DB2 instance to which the setting will apply from the selection box and click OK.
3. In the Configure KM Defaults: DB2 Instance Settings for DB2_Instance window, select the Discover Remote Databases check box.
    This option is active when a check appears in the check box.
4. Right-click on the DB2_SETUP, and select Configure > Configure Default Account.
5. Select the remote database listed and configure the default account for this remote database.

Subagent discovery in DB2 UDB EEE

In the DB2 UDB EEE component, subagents discovery is optional. In DB2 Enterprise - Extended Edition, a large multipartitioned database system can have a large number of subagents running to process parallel operations across nodes. To monitor the subagents in your environment with PATROL for DB2 UDB EEE, you must configure subagent discovery.

To configure subagent discovery in DB2 UDB EEE

1. Right-click DB2EEE_SETUP, and select Configuration > Configure Application Discovery command.
2. select the Discover subagents check box.

Additional discovery options

Additional discovery options are available from the Configure KM Default Settings setup command. For more information about customizing discovery for your PATROL sessions, see Monitoring DB2 health with PATROL