IBM DB2 Query Patroller Administration Guide

Troubleshooting QueryEnabler

Whenever a problem occurs, you should check the following:

• The DB2 server is started.
• The application can connect to the DB2 server directly using the DB2 cataloged names.

In order to help identify problems, IBM support representatives may employ the following tracing mechanisms collectively or separately:

• JDBC trace
• DB2 CLI trace
• DB2 trace
• ODBC trace (if you are using ODBC)

DB2 trace will activate the Java Trace tool for QueryEnabler. The Java trace file will be created in the DQP_RUNTIME/log/ directory on UNIX, or in the DQP_RUNTIME\log\ directory on Windows. Once a log file has been created, trace information created subsequently will be appended to this log file. You can name your own Java log file by setting the DB2 Query Patroller profile variable DQP_TRACEFILE. For more information on setting DB2 Query Patroller profile variables, see DB2 Profile Variables.

Trace facilities are described in the Troubleshooting Guide. Refer to this document for detailed instructions.

Common QueryEnabler Problems

1. The application is unable to connect to DB2:
   • Verify that the application is able to connect to DB2. If this fails, refer to the Troubleshooting Guide for information on how to resolve a connectivity problem.
   • Ensure that the user account and user password are correct.
2. The application is unable to access the QueryEnabler query submission dialogs:
   • Check the path for the database configuration parameter, JDK11_PATH and check the setting for JAVA_HEAP_SZ. JDK11_PATH and JAVA_HEAP_SZ are both used to start the Java Virtual Machine (JVM).
   • Ensure that QueryEnabler has been installed correctly.
   • Ensure that the DYN_QUERY_MGMT database configuration parameter has been set to ENABLE in the database configuration file on the server.
3. The QueryEnabler dialogs appear unexpectedly:
   • Ensure the application is using the correct database alias name.
   • Increase the Cost Management Threshold parameter in the profile of the submitting user. This will allow queries that do not exceed the threshold to run against the data source without user intervention via the QueryEnabler tool.
4. The query application is unable to submit a query to the DB2 Query Patroller server using QueryEnabler:
   • Ensure the DB2 Query Patroller server stored procedures have been installed on the DB2 server.
   • Ensure the user has been granted the proper DB2 access to the stored procedures.
   • Ensure that the User Management Threshold parameter for the user is set to an appropriate value. If the cost of the query does not exceed the management threshold, the QueryEnabler interface will not appear.
5. The application has submitted a query to the DB2 Query Patroller server but the query is not being executed:
   • Ensure that the DB2 Query Patroller server is running correctly. It may be necessary to restart the DB2 Query Patroller server.
   • Use QueryMonitor to inspect the details of the Job. The job may be held because the query exceeded user thresholds. A DB2 Query Patroller administrator or operator must release this job.
   • The job may be in the queued state because system resources have exceeded configured limitations. Under these conditions, the query will execute once the system resources fall within acceptable limits as configured by the DB2 Query Patroller administrator.