Customizing discovery options

For various reasons including performance considerations, you can monitor only specific DB2 instances at any given time. You can control which objects are being monitored by setting default discovery options in the SETUP menu. In an active session, the setting takes effect at the next discovery cycle.

1. From the SETUP menu, select Configuration > Configure KM Defaults > DB2 Instance Settings.
2. If more than one instance exists, select an instance from the selection box and click OK.
3. In the Configure KM Defaults:DB2 Instance Settings window, select the following options:
   • Discover Remote Databases (available in DB2 UDB EE only)
     
     Select this option to enable remote database discovery in the PATROL for DB2 UDB EE component.
     
     Be aware that the following features are not available when you discover remote databases:
     • using backup and restore menu commands
     • monitoring SMS tablespaces (only the TblspState, PhyReads, and PhyWrites parameters are monitored)
     • using the SQL Viewer
     • using SQL Explain
     • using the SQL Processor
     • using advanced performance monitoring
     • detecting deadlocks
     • monitoring of backups directory (BackupCount parameter)
     • monitoring of log files and history recovery files
   • Suspend Discovery of this Instance
     
     Select this option to suspend discovery and collection of information about the selected DB2 instance, beginning with the next polling cycle.
   • Suspend discovery of this Instance if following file exists
     
     Enter the name of the file that will trigger the KM to suspend discovery and collection of information about the specified DB2 instance. This feature is useful for DBAs who want to perform maintenance procedures without directly accessing the console to suspend the discovery of an instance.
   • DB2ServerOK parameter action
     
     Select the type of action that you require for the DB2ServerOK parameter. By default, no action is taken. See Configuring the PATROL response to the DB2ServerOK alarm for details.
   • ConnToDBOK parameter action
     
     Enter a comma separated list of SQL messages on which to warn if the ConnToDBOK parameter unsuccessfully connects to the database. By default, the parameter will warn on the following messages: SQL1116N (backup pending), SQL1032N (database manager not started), and SQL1035N (database in use).
   • Update Database and Tablespace Options
     
     Select this option to suspend discovery of one or more selected databases in an instance, and to specify tablespaces to discover. You can select from the following options after you enter a database to update and click OK:
     • Discover only DMS tablespaces
     • Discover all tablespaces
     • Do not discover any tablespaces

     • Discover the following tablespaces (based on their names)

       Note

       Tablespaces do not appear in the console until discovery runs. The default tablespace discovery cycle is set at more than three hours. To verify your changes, force start a new discovery cycle. To force application discovery on a monitored host, see Triggering-application-discovery. When the discovery cycle is completed, the PATROL desktop is repopulated with the newly discovered applications.

       If you select Discover the following tablespaces, highlight the tablespaces that you want to discover in the scrollable list provided. (You can also click on highlighted tablespaces to stop the KM from discovering them.) A limit of 2,000 tablespaces will be displayed. Also, you cannot select more than 100 tablespaces. If you select more tablespaces, a warning message is displayed stating that only the first 100 will be processed.