Product Documentation
Abstract
This document lists the problems that have been fixed in the IBM Data Studio client and InfoSphere Optim Query Workload Tuner, Version 4.1.
Content
| Description | Affected Products |
|---|---|
| Running the Statistics Advisor or Workload Statistics Advisor would sometimes repeat recommended RUNSTATS commands after they had already been run. | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
| Running the stored procedure SYSPROC.EXPLAIN_SQL on non-unicode databases sometimes failed. | InfoSphere Optim Query Workload Tuner for DB2 for Linux, UNIX, and Windows |
| Tuning a large, complex SQL statement from the workflow assistant sometimes resulted in lock escalations on catalog tables. | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
| When tuning an SQL statement that references created global temporary tables, an error sometimes occurred. | InfoSphere Optim Query Workload Tuner for DB2 for Linux, UNIX, and Windows |
| When attempting to run the Index Advisor on a database that was connected to with Kerberos, an error sometimes occurred. | InfoSphere Optim Query Workload Tuner for DB2 for Linux, UNIX, and Windows |
| When attempting use the Capture Query Environment or Capture Workload Environment to collect service data, an error occurred if the input value contained alphabetic characters. | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
| Attempting to generate an access plan graph on subsystems that contain extended binary coded decimal interchange code sometimes returned catalog values with unreadable strings. | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
| Explaining an SQL statement from a user-defined function that returns a table sometimes resulted in the error message "An internal error occurred. Contact IBM Support for assistance." | Data Studio client |
| Tuning an SQL statement that uses range-list index scan in its access path sometimes failed with a -4470 SQLCODE. | Data Studio client |
| When running the Index Advisor or the Workload Index Advisor using a secondary authorization ID as the current SQLID, an error sometimes occurred. | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
| Tuning an SQL statement captured from a catalog plan or package sometimes failed with -104 SQLCODE if the statement contained a cursor name with the string "FOR". | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
| Invoking the advisor with a User Defined Function (UDF) in DB2 for z/OS v10 compatible mode sometimes failed with -440 SQLCODE. | InfoSphere Optim Query Workload Tuner for DB2 for z/OS |
[{"Product":{"code":"SS7LB8","label":"InfoSphere Optim Query Workload Tuner for DB2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Product":{"code":"SS7L9Q","label":"InfoSphere Optim Query Workload Tuner for DB2 for z\/OS"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":" ","Platform":[{"code":"PF035","label":"z\/OS"}],"Version":"4.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27038550