Monday, May 27, 2019
SQL Optimizer for IBM® DB2® LUW maximizes SQL performance by automating the manual, time-intensive and uncertain process of ensuring that SQL statements are performing as fast as possible. SQL Optimizer for IBM® DB2® LUW analyzes, rewrites, and evaluates SQL statements within multiple database objects, files, or SQL statements captured by the DB2 Event Monitor. Whether you are a developer, DBA, or performance tuner, you can let SQL Optimizer for IBM® DB2® LUW analyze and optimize all the problem SQL from multiple sources. SQL Optimizer for IBM® DB2® LUW also provides you a complete index optimization and plan change analysis solution, from index recommendations to simulated index impact analysis, through comparison of multiple SQL access plans.
SQL Optimizer for IBM® DB2® LUW 4.2 is a maintenance release.
The following is a list of issues addressed and enhancements implemented in this release of SQL Optimizer for IBM® DB2® LUW:
|Resolved Issue or enhancement||Defect ID|
|A bug when row count was different than the original SQL after optimization has been fixed||
The following is a list of issues known to exist at the time of this release.
|Feature||Known Issue||Defect ID|
|General||Due to the program name change in version 3.0, the location where the Options (formerly called Preferences) are stored in the Windows registry was changed. Therefore, if you are upgrading from a version earlier than 3.0, all the Options have been reset to the defaults and you will have to customize them again if you had made any changes in a previous version.||N/A|
The directory where the program data is stored was changed in version 3.0. To use the data from a previous version, you will need to either change the Options setting to the former location or to copy the data into the new location.
Former directory (default): C:\Documents and Settings\username\Application Data\Software\Quest Software\QCUDB
New directory: C:\Documents and Settings\username\Application Data\Quest Software\Quest SQL Optimizer for DB2 LUW
SQL statements that contains parameter markers or host variables as the operands of the same operator are unsupported. For example: select * from employee where ? = ?
You will receive this error:
"[IBM][CLI Driver][DB2/NT] SQL0417N A statement string to be prepared contains parameter markers as the operands of the same operator. SQLSTATE=4. "
|Column detection of table functions with host variables or columns as table function parameters are not supported. These columns will be defined as host variables.||N/A|
A SQL statement cannot have more than 2047 characters on one line in the SQL Text pane in the SQL Optimizer or the Index Expert function due to a size limitation of the SyntaxMemo component used for editing.
Workaround: Format a large SQL statement so that it is on several lines.
|Edit Data||A table name or column name that has a double quote ("), single quote (') or a period (.) in the name will cause an error when using the Edit Data function to INSERT, UPDATE, or DELETE.||ST39349|
In the SQL Repository, when you refresh the access plan of a SQL statement that uses a temporary table, the temporary table must exist in order to retrieve the current access plan. If the temporary table does not exist, SQL Optimizer for IBM® DB2 LUW prompt you to create the table and then copy the DDL for creating the table to the User-Defined Temp Table module so you can create the table. (This works correctly.)
If a temporary table does exist, it checks to see if the table definition for the existing table is the same as the one needed to refresh the plan. If it is the same, it should use the temporary table that already exists. Instead it prompts you to create the table and then fails when you try to create the table.
Workaround: Manually remove the temporary table in the User-defined Temp Table module before you refresh the access plans.
|SQL Scanner||If you have not set up a default printer on your PC, you will get an access violation when you try to save the Scanned SQL Report in the "Adobe Acrobat Document (*.PDF), HTML Document (*.HTM), or RTF Document (* .RTF) formats.||ST39378|
An error message displays when you try to get a plan for a SQL function with a variable parameter.
Workaround: replace the function with a variable parameter with a variable.
Before installing Quest SQL Optimizer for IBM® DB2® LUW , ensure your system meets the following minimum hardware and software requirements:
|Platform||1 GHz recommended minimum|
|Memory||1 GB of RAM recommended minimum|
|Hard Disk Space||50 MB hard disk space|
Microsoft Windows 7 (32-bit and 64-bit)
Microsoft Windows 2008 R2
Windows Server 2012
Windows Server 2012 R2
Microsoft Windows 8 (32-bit and 64-bit)
Microsoft Windows 8.1 (32-bit and 64-bit)
Microsoft Windows 10 (32-bit and 64-bit)
Microsoft Windows Server 2016
|Database Client||PC client connection to DB2 LUW with DB2 LUW Client Software version 9.5 or higher|
|Database Server||DB2 for LUW 9.5 or later on Windows, UNIX, OS/2, Linux, AIX, HP-UX, Solaris platform|
Adobe Acrobat Reader 7.0 or later (for viewing the Installation Guide)
Microsoft Internet Explorer 6.0 or later
Limited testing has been performed for Citrix XenApp 6.5 on Windows Server 2008 R2.
Note: SQL Optimizer for IBM®DB2® LUW may work in virtualization environments other than the ones in which it was tested.
The Quest SQL Optimizer for IBM® DB2® LUW release package contains the following products:
Product documentation, including:
Refer to the Quest SQL Optimizer for IBM® DB2® LUW Installation Guide for installation instructions.
Get the latest product information, find helpful resources, and join a discussion with the SQL Optimizer for IBM® DB2® LUW team and other community members. Click here to join the SQL Optimizer for IBM® DB2® LUW community.
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release supports any single-byte or multi-byte character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
This release has the following known capabilities or limitations: (same as that in version 2.8.0).