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.

Procedure

  1. After you complete the SMP/E installation of a new SQL Tuning Services release, edit the new tmsservice.config file and specify the same values that you used in the previous version of the tmsservice.config file.
  2. Stop the SQL Tuning Services server if it is running.
  3. If you have a license for IBM® Db2® Query Workload Tuner for z/OS®, create a copy of the existing wlp_user_dir/servers/server_name/license folder and save it to a folder other than the wlp_user_dir folder.
  4. Run the tmsservice.sh script and specify the new tmsservice.config file to create a new SQL Tuning Services server: 
    ./tmsservice.sh tmsservice.config
  5. Copy the license folder that you saved in step 3 to the new wlp_user_dir/servers/server_name folder.
  6. Check the information in the APAR to determine if the SQL Tuning Services repository database must be upgraded at this time. If so, complete this step.
    Note: Before the availability of APAR PH55158, the /tuningservice/v1/repodb API was used to both create a new repository database and to upgrade an existing repository database. APAR PH55158 and subsequent APARs provide JCL that simplifies the process of upgrading the SQL Tuning Services repository database.
    After the SMP/E installation of APAR PH55158 or a later SQL Tuning Services APAR is complete, the following two JCL jobs are available in the SDSN5TSA data set:
    • DSN5UPR1 upgrades the repository database from SQL Tuning Services 1.0 to the most current version.
    • DSN5UPR2 upgrades the repository database from SQL Tuning Services 2.1 to the most current version.
    After the SMP/E installation of APAR PH56970 or a later SQL Tuning Services is complete, the following additional JCL job is available in the SDSN5TSA data set:
    • DSN5UPR3 upgrades the repository database from SQL Tuning Services 2.1 (PH56970) to the most current version.

    Select the job that is appropriate for your version of SQL Tuning Services, modify it for your environment, and run it to upgrade an existing repository database.

  7. In some cases, upgrading SQL Tuning Services requires you to rebind packages. Check the information in the APAR to determine if any packages must be rebound and, if so, follow the instructions in the APAR to rebind them.