Troubleshooting

Use the information in this topic to troubleshoot common SQL Tuning Services usage problems.

Problems with tuning profiles

When you are using a tuning profile to tune a single query, the tuning job will fail in the following situations:

A change was made in the Db2® environment after a tuning profile was created, and the tuning profile has not been updated to reflect this change; for example, the connection information associated with the tuning profile is changed.
The user credential associated with the tuning profile has expired.

A tuning profile encapsulates its owner’s credential and the Db2 subsystem properties such as host, port, location, and server type. If any of these values change, the profile becomes invalid and tuning jobs that run with this profile will fail.

Take either of the following actions to solve this issue:

Delete the existing tuning profile and create a new profile that reflects the current Db2 environment.
Attempt to run the tuning job without specifying a tuning profile. Note that because tuning profiles require ongoing maintenance, the recommended approach is to tune SQL without specifying a tuning profile.

Contacting IBM Support

If you encounter problems while using SQL Tuning Services that you are unable to solve on your own, use the following information to gather diagnostic information before contacting IBM® Support for assistance.

Locate the log information in the TMS_HOME/logs directory for the period of time when problem occurred.
If you are able to re-create the problem, enable detailed logging by setting logger.ibm.level=trace in the application.properties file. Then restart SQL Tuning Services and perform the actions that cause the problem to occur.
Download the log from the server.
Download the application.properties, tmsserver_override.properties, and repodb_override.properties files from the TMS_HOME/Config directory.
Open a support case at https://www.ibm.com/mysupport/s/.
Attach the log and properties files to the support case.