On a properly functioning DB2 Query Patroller server, the following processes will be active:
An DB2 Query Patroller agent will have the following processes active:
| Note: | Other DB2 Query Patroller processes are transitory and will be started and stopped as required. |
If any of these processes have quit before completion, the DB2 Query Patroller system should be restarted. This process should be performed by systematically shutting down all DB2 Query Patroller agents followed by the DB2 Query Patroller server. The DB2 Query Patroller system can then be restarted by bringing up the server first, followed by the DB2 Query Patroller agents.
Under extreme circumstances, it may be necessary to generate a detailed DB2 Query Patroller server trace file to send to IBM support. In order to enable tracing, start the DB2 Query Patroller server or agent and implementing the trace option. More specifically, for the DB2 Query Patroller server specify iwm start all trace, and for an DB2 Query Patroller agent specify iwm start agent trace. The detailed trace will be written to the syserr.log file in the path specified by the DB2 profile variable IWMLOG. The trace results will continually be written to the log until DB2 Query Patroller is stopped and restarted without the tracing option.
| Note: | This file can grow quickly and should reside on a file system with a large amount of free disk space. |
DB2 Query Patroller is also integrated with DB2 trace. The IBM service organization may request a DB2 trace in order to help identify and localize a problem. Refer to the Troubleshooting Guide for details on how to perform a DB2 trace.