IBM DB2 Query Patroller Administration Guide

Troubleshooting Tracker

Tracker is a JAVA application that uses JDBC to access the DB2 Query Patroller schema in DB2 in order to provide reports that display database usage history for queries that have been managed by DB2 Query Patroller.

Diagnostic information for Tracker can be obtained from four sources:

• the DB2 diagnostic log
• ODBC traces
• CLI traces
• DB2 traces

The Tracker tool may be launched from the command line with a -t switch, which will cause a console to appear for a Java trace, or a --tf filename switch causing the trace information to be output to a file. Note that the current directory must be set to DQP_RUNTIME\qp directory on Windows, or the DQP_RUNTIME/qp path on UNIX, where DQP_RUNTIME is the DB2 Query Patroller installation path. To initiate a Java trace for the Tracker tool and have the trace information output to a file, execute the following command from the DQP_RUNTIME\qp directory on Windows, or the DQP_RUNTIME/qp path on UNIX:

  db2track -tf filename

where filename is a fully qualified path and file name for the Java trace to place diagnostic information.

Common Tracker Problems

1. Tracker is unable to access DB2:
   • Ensure that the correct DB2 data source name, user name, and password have been specified.
2. Tracker does not display any data:
   • Ensure that the DB2 Query Patroller server has been configured to capture this information.
   • From QueryAdministrator, check that the Accounting option has been enabled.
   • Ensure that the date range specified in the Tracker application is set correctly to a time period when queries were in progress.
3. The data displayed by Tracker is not up-to-date:
   • Ensure the Tracker server on the DB2 Query Patroller server is scheduled to execute periodically. The Tracker server component may be executed interactively to generate up-to-date statistics.