The following is a list of issues addressed and enhancements implemented in this release of Toad for IBM DB2.
|Feature||Resolved Issue||Defect ID|
|Data Compare & Sync||Issues involving comparing Decimal column values have been resolved.||TSY-1512/2985032-1|
|Added option for Data Compare to treat blank values as null.||TSY-1576/2906856-1|
|Data Compare can now export to XLSX format.||TSY-1549/2897802|
|Data Compare does not cause errors when comparing decimal column.||TDB-2108|
|Compare Object||Toad now shows progress when saving report files.||TDB-2103/2838693-1|
|Comparing identical schemas does not result in DROP/CREATE of a procedure.||TDB-2045/2838693-1|
|Compare Object does not load all database objects at once anymore, which improves its overall performance.||TDB-2429/3040952-1|
|Code Completion||Code Completion now offers all creators.||TDB-1280/2594500-1|
|Object Details||Grid controls for Excel export were added to the grid.||TDB-1735/2772256-1|
|Debugger||Toad has a new option to control port for communication with the z/OS Debug Session Manager. Select Options | Debugger | DB2 to change it.||TDB-2409/3045782-1|
|Explain Plan||Explain plan does not cause errors on SAP environment with Unicode set anymore.||TDB-2394|
|Explain plan now uses Default schema/auth ID instead of login ID.||TDB-2289/2962270-1|
|General||Data Sharing member name is now shown. See the z/OS section for more information.||TDB-1748|
|Code units are not displayed incorrectly for Unicode tables anymore.||TDB-2298/2967012-1|
|Toad does not set DB2CODEPAGE to CCSID 1208 anymore.||TDB-2404/3037683-1|
|Migration||"Include DROP statements" option now works correctly.||TDB-2229|
|Object Details (DOV)||Error when getting detailed space usage information was fixed.||TDB-2313/2969045-1|
|Object Editor||When DEFER is specified in Index creation, RUNSTATS is not generated after the Index has been created.||TDB-1861|
|Script Generation||New CREATE TABLE syntax from z/OS 11 is now supported.||TDB-1891/2821895-1|
|Plans for z/OS now work correctly.||TDB-2440|
|SQL Editor||Tab pop up menu now works correctly.||TDB-1650|
|Cancelled long running DML scripts do not hold locks anymore. If a transaction is cancelled, ROLLBACK is issued automatically.||TDB-2041/2849385-1|
|Editor does not have doubled menus on right clicks anymore.||TDB-1650|
The following is a list of issues known to exist at the time of this release.
|Feature||Description||Support Case/Defect ID|
|Object Details||When a DB2 object is created, DB2 implicitly creates authority for the user who created that object. In the system catalog tables those are shown as SYSIBM as the Grantor. When migration\compare\extended alter scripts are generated Toad does not generate GRANT statements in those scripts for authorizations granted by SYSIBM because those are granted implicit authorizations that have been created by DB2.||TDB-870|
|Dashboard||Dashboards created in beta version may not always open successfully in subsequent beta drops. You may need to remove and create new dashboards during the beta cycle.||TDB-2479|
You might encounter issues with initializing Unified Debugger sessions if the version of the DB2 for LUW server on which you are debugging is earlier than 10.1 fix pack 2.
Workaround: If the DB2 server version is earlier than DB2 for LUW 10.1 fix pack 2, copy DB2DBGM.JAR from the Toad client installation to the following location on the server:
If the DB2 server version is DB2 for 10.1 fix pack 2, use the JAR file supplied with your DB2 version. If replacing the JAR file as described in the workaround, make sure you back up the original JAR file on the server before replacing it with the one from the Toad client installation.
|You may encounter problems setting breakpoints and variable watches when using the Unified Debugger on LUW instances 10.1 fixpack 2 and higher.||ST110352|
|Currently, the debugger does not support Unicode schema names.||ST41770|
After a STEP OUT request, the Debugger momentarily returns to the line just after the call to the inner procedure and then proceeds to execute to the end of the calling procedure.
Workaround: Set a breakpoint after the call to the inner procedure.
|Export Wizard/ One Click Export||Avoid using Excel for exporting if your data has numeric values that require a high precision because Excel's precision is limited to 15 digits. If you export numbers with more precision, the values are rounded. If you export boundary numbers (max, min), rounded numbers will exceed the data type limit.||N/A|
Extract DDL(z/OS) When extracting DDL for Database with "Include objects that are dependent upon those originally selected" the indirectly dependent objects (e.g. tables, indexes, etc.) are not included in the script if the tablespace was excluded.
Workaround: Instead of selecting the Database and invoking Extract DDL, select the Tables and invoke Extract DDL Or Select the Database and invoke the Migrate Object feature. Then select “Include Objects that are dependent’ and ‘Process multiple object levels’. Then you can selectively include or exclude the DDL for specific objects.
Attempting to launch Toad results in a System.Security.Policy.PolicyException error.
Workaround: Ensure that the system administrator has placed Toad in the correct code group with permissions to execute code.
|Customized options defined in Toad's Configuration wizard are not applied if you are running as a Restricted user.||CR216699|
Toad z/OS Components reference QUEST.QC200ZPARM function, which leads to the S378 Abend, when running IBM DB2 z/10 subsystem in Conversion mode with older versions of Toad.
Workaround: DROP QUEST.QC200ZPARM function from your DB2 z/OS 10 subsystem. This will eliminate the possibility of the function being called into the WLM environment procedure and causing the S378 abend. We do not recommend you to just STOP QUEST.QC200ZPARM function on the mainframe side, without actually dropping it, because that may cause Toad or batch process (QCEXEC – remote job execution) hang. Dropping QUEST.QC200ZPARM function is recommended.
|Installation||The Toad installation process installs a DB2 client in the specified Toad installation path. If the user chooses to override the default Toad installation path, the new path cannot include Unicode characters because the DB2 client installation does not support such characters.||N/A|
|Network and LAN installations are currently not supported.||N/A|
When installing Toad using Quest Installer on Windows 7 64-bit, Program Compatibility Assistant may appear with “This program might not have installed correctly” message.
Workaround: Select This program installed correctly to continue installation.
For more information, see here.
Toad uses hardcoded values instead of some variables such as %USERNAME% in several path names and therefore App-V environment is not supported.
For installation adhere to Windows Installer Best Practices, see here.
|Pivot Grid||TIMESTAMP is not detected as date column in pivot grid.||ST90996|
If running Toad for IBM DB2 6.0 or earlier in a pureScale environment and the QUEST.SH_SNAPSHOT procedure had been installed, the procedure will have to be redefined. Please, follow these steps:
When using Korean symbols in comments (beginning with "--") for SQL script, the comment line and any following lines in the statement are treated as comments.
Korean symbols should not be used in comments beginning with "--"
Block style comments should be specified like "/* comment */"
|Toad does not handle DBMS_OUTPUT in the SQL Editor.||ST90710|
When using Utilities as the data preservation method and the length of a column tied to columns from other tables via RI is reduced. When executing the alter script the load fails with a DSNU334I INPUT FIELD INVALID error pointing to the altered column. The load cards show the old length for the altered column which appears to be the problem.
The following is a list of third party issues known to exist at the time of release of Toad for IBM DB2 6.2.
|Feature||Description||Support Case/Defect ID|
In case Toad and a 9.5, 9.7 or 10.1 DB2 client is installed on Windows 8 or Windows Server 2012 IBM setup recommendation #1618434 has to be applied.
|LUW Procedure Script Tab||
After installing DB2 LUW v10.1.3, the script tab for LUW procedures is empty. This is due to an issue introduced by IBM in fixpack 3 regarding the NULLIF SQL function.
IBM APAR IC96725 addresses this issue.
|DB2 z/OS invalid Timestamp values returned||
When the IBM DB2 Analytics Accelerator is used in conjunction with DB2 z/OS, along with an IBM DB2 .Net Data Provider v10.1.3, timestamp values returned from queries are invalid. Since Toad DB2 v5.6 uses the IBM DB2 v10.1.3 .Net Data provider, invalid timestamp values can be returned within Toad 5.6. IBM PMR 8862756 has been opened on this topic.
Please consult that PMR for a work-around.
|LUW Procedure Debugging||
When the user is running DB2 Server 10.1.3 with a database that has been migrated from a previous release, the debugger will fail with a reference to SYSDEBUGPRIVATE. This occurs from an IBM bug in the db2updv10 update utility.
IBM APAR IC96837 addresses this issue. This has been resolved in IBM DB2 10.1 FixPack 4.
The Debugger may not advance to the next line under certain circumstances. Those circumstances include DECLARE statements with multiple variables defined on a single line and IF statements with multiple conditions defined on a single line.
In procedures that are to be debugged: The procedure text should be modified to separate DECLARE variables onto different lines and IF statements separated to have conditions on separate lines.
LUW: The following error message is displayed when you attempt to modify a watch value during a Debug session on a DB2 for LUW 9 database: "ERROR  [IBM][DB2/NT] SQL0954C Not enough storage is available in the application heap to process the statement. SQLSTATE=57011" The call to modify the watch value fails on DB2, and the server runs out of heap memory.
Workaround: To avoid the heap memory issue, increase the application heap size on the server.
|General||A double-byte character cannot be inserted into a database with a single-byte codepage. IBM PMR30857,756,000 states that this configuration is not supported.||CR220327|
If an Excel file is open in Toad, you cannot open the same file in a separate Excel instance.
To review this and other limitations when using Excel in the Web Browser, see "Considerations When Using the WebBrowser Control" at Microsoft Support.
|Export Wizard/ One Click Export||
To export to an Office 2003 or 2007 Excel instance, the Office Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from one of the following locations:
Date formatting issues occur when exporting table data to an Excel file or instance. These issues seem to occur especially when exporting dates previous to 1900.
Workaround: For better results, try exporting the data to a CSV file.
|Object Editor (DOE)||
z/OS: Executing a procedure causes "Invalid SQL syntax" message when parameter listing has a new line character separating parameters. IBM has opened PMR 80539,756 to investigate this issue.
Workaround: Remove the new line character and separate the parameters by the spaces.
DB2 LOAD utility with IGNOREREFIELDS YES does not work with DEFLOAT(34) field, gets error message: DSNU3381 DSNURUFL - INVALID COLUMN SPECIFICATION FOR TEST_CREATE_DEFLOAT1
Refer to IBM PM53520 for more information.
LOAD statement fails on partitioned table with 138 columns and leads to loss of data.
Refer to IBM PMR 00276,756 for more information.
The Toad release package contains the following products:
See the Toad for IBM DB2 Installation Guide for more information.