Administering SQL Tuning Services

Use the information in this section to administer and maintain your SQL Tuning Services environment.

Changing the repository database user ID and password
You will likely need to change the password for the sqlts_repodb_id at regular intervals based on your password-expiration policies or if you encounter authentication issues with the SQL Tuning Services repository database. Similarly, you might need to assign a different user to the sqlts_repodb_id at some point.
Changing the password for a tuning profile
When you create a tuning profile, the user ID and password for the Db2 for z/OS target database is stored in the repository database. Whenever that password changes, you must update the password for the tuning profile.
Reconfiguring SQL Tuning Services
To change your SQL Tuning Services configuration after the initial installation and configuration, you need to modify one or more configuration files depending on the types of changes that you want to make.
Configuring SQL Tuning Services logging
By default, SQL Tuning Services logs are written to a single file that you must manually maintain. To automate the maintenance of SQL Tuning Services logs, you can enable logging with rollovers.
Enabling multiple tokens for a single user
By default, an SQL Tuning Services server allows only one authentication token to be active at a time for a single user. This behavior causes authentication problems for users who want to use multiple clients simultaneously, such as Db2 Developer Extension and Db2 Administration Foundation, to access the same SQL Tuning Services server.
Upgrading SQL Tuning Services
When you upgrade to a new release of SQL Tuning Services, you need to modify several configuration parameters to use the new release. You might also need to upgrade the repository database as part of the upgrade process.

Parent topic: IBM SQL Tuning Services