Managing the DB2 diagnostic log file

In PATROL for DB2 UDB, you can use a browser facility to view and use the information in the db2diag.log file. The diagnostic log contains information about administrative events and errors.

Through the following procedures, you can manipulate the DB2 diagnostic log file and manage its content. You can configure keywords that will trigger an alarm in the PATROL console when they are written to the log, and you can also specify the action invoked when the keyword appears in the log.

You can use the alphanumeric characters to configure the log keyword. However, the expressions preceded by 0 (zero) are not accepted (for example, 0x and 0gh).

To browse, prune, and configure keywords in the diagnostic log

1. Right-click on the db2diag.logicon in the DB2 instance object window and select one of the following commands: 
   • Display Diagnostic Log
   • Configure Log File Keywords
   • Modify Log File Keywords
   • Configure Maximum DiagLogSize
   • Prune Diagnostic Log File
   • Acknowledge DiagLogOK Alarm
2. If you select Display Diagnostic Log, use the following navigation options to browse records in a log file:
   • Click Backward, Forward, Top, or Bottom and click Update to navigate through the log.
   • Select all and click Update to view all entries.
   • Select dumps and click Update to view all log entries with references to a dump.
   • Select alerts and click Update to view all log entries with references to an alert.

   • Select string: and enter a keyword to view all references to a specified keyword and click Update.

     Warning

     Note

     For more information about the log file, see Setting-the-maximum-size-of-the-diagnostic-log-file.