Toad® for IBM DB2

Version 3.1.1

Release Notes

April 2008


Contents

Welcome to
Toad for DB2

New in this Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information


Welcome to Toad for DB2

Toad for DB2 is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to DB2 expertise.

Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.

All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.


New in This Release

Toad for DB2 3.1.1 provides fixes to customer issues. For a description of these issues, see Resolved Issues and Enhancements in 3.1.1.

For a description of the updates and new features available in the previous Toad for DB2 3.1 release, see the following sections:

For a description of the updates and new features available in the previous Toad for DB2 3.0 and 3.0.1 releases, see the following sections:

Updates in Toad for DB2 3.1

This release includes updates in the following areas:

For a description of the updates in Toad for DB2 3.0 and 3.0.1, click here.

General

Database Administration

Data Management

Query Development

 

New Features in Toad for DB2 3.1

This release offers new features in the following areas:

For a description of new features in Toad for DB2 3.0 and 3.0.1, click here.

General

Database Administration

Query Development

Version Control

Updates in Toad for DB2  3.0

Toad for DB2 3.0 and 3.0.1 included updates in the following areas:

General

Connection Management

Customization

Database Administration

Data Management

Query Development

Database Development

Reporting

Project Management

New Features in Toad for DB2 3.0

Toad for DB2 3.0 and 3.0.1 offered new features in the following areas:

Installation

Connection Management

Database Administration

Data Management

Query Development

Reporting

Troubleshooting

Version Control

Project Management


Resolved Issues and Enhancements

Click the following links to view issues addressed and enhancements implemented in the Toad for DB2 3.x releases, including this latest release 3.1.1:

Resolved Issues and Enhancements in 3.1.1

Feature

Resolved Issue

Change Request

Editor (Toad for DB2 for z/OS) The Explain now handles the SQL0220N error that is generated for a non-DB2-standard column length in FUNCTION_TABLE as a warning. Instead of failing, the Explain now proceeds when it encounters this error. CR#46,862

Case#521808-2

Log Reader for DB2 Log Reader no longer generates the incorrect message about the current DB2 client being an unsupported version. CR#47,575
Case#577110-1

 

Resolved Issues and Enhancements in 3.1

Feature

Resolved Issue

Change Request

General
Toad has resolved additional character issues that occur when Regional Options is set to Turkish on the client computer. This fix is related to the CR#224551, resolved in Toad for DB2 3.0.1. CR#225285
Case#555563-1
Connection Manager (DB2 for LUW only) The issue with Toad reducing log-on ID authority and causing licensing problems has been resolved. CR#222916
Case#543533
Advanced ALTER Toad now provides the option to use either temporary tables or DB2 commands and utilities (including EXPORT and IMPORT for DB2 for LUW and UNLOAD and LOAD for DB2 for z/OS) during advanced ALTERs. CR#226760
Case#565223-1
Database Browser/Object Palette
(DB2 for LUW only) The object editor for Tables now supports data partitioning. CR#202703
(DB2 for z/OS) Performance when browsing objects in DB2 for z/OS is greatly improved if you create additional indexes on certain system catalog tables. See Recommended Indexes to Improve Toad Performance in DB2 for z/OS for more details. CR#214406,
CR#227223
(DB2 for LUW only) Native EXPORT and IMPORT utilities are now available in Toad. You can export to or import from IXF, ASCII, or worksheet formats. Additionally, the user interface for either utility allows you to run the utility on multiple tables. You can accept the command option defaults in the utility window or change them as needed to execute the multiple commands. CR#215819,
CR#216566
Case#525202
When you generate the script to add, remove, or alter an index column or change the index type, the script also contains a warning message about the effects on the update on dependent constraint definitions. CR#219910
The issue with a materialized query table name displaying multiple times in the Database Browser is resolved. CR#224709
Case#556353
(DB2 for LUW only) Controls for the MAXSIZE and INCREASESIZE options are now included in the Tablespace object editor. CR#226589
Case#565019
The Database Browser no longer displays incomplete scripts for triggers with long definitions. CR#226763
Case#558376
The timestamp format in the data grid no longer incorrectly shows a hyphen between the date and time. CR#227855
Case#565520
Toad no longer generates incorrect syntax for table columns created with the NOT NULL WITH DEFAULT attribute. CR#228001
Case#572279
Debugger The parameter size-limitation issue is resolved. CR#225757
Case#560631
Data Diff Viewer Comparing a script results grid with an XSD file now works. CR#219662
Editor Toad can execute SQL scripts in the Editor whether or not syntax highlighting is enabled (Tools | Options | Editor | Highlighting Styles). CR#167980
The error generated during Explains is resolved. CR#215661
Case#521808
Stored procedures now display in the object list generated when you press Ctl + . (period). CR#226017
Case#562313
Invalid error messages are no longer generated when you cancel a script execution. CR#227743
Case#569738
Help The link to tutorials has been removed from the Welcome to Toad page (Help | Contents | Welcome to Toad) in the help for 3.1 since no tutorials were available at the time of this release. However, these tutorials are now available post-release, and the link will be restored in the Toad for DB2 4.0 help. Click here to link to the current tutorials: http://www.toadworld.com/Portals/0/ToadDB2/Videos/Chap00.htm CR#229748
Case#583127
Log Reader for DB2 Log Reader now supports code page 819. CR#229407
Case#580081
Toad Security Toad Security is now disabled for Toad for DB2 DBA licenses. CR#221808

 

Resolved Issues and Enhancements in 3.0.1

Feature

Resolved Issue

Change Request

General
Toad has resolved the character issue that occurs when Regional Options is set to Turkish on the client computer. CR#224551
Case#555563
Editor
If a user attempts to close the Editor when a lock exists on an object because of an uncommitted transaction, the Editor notifies the user of this condition. CR#224712
Case#540318
Schema Compare Schema Compare is automatically enabled for users with commercial or term licenses for the Standard, Professional, or Xpert editions of Toad for DB2 2.5 or earlier. CR#223702
Case#550259

 

Resolved Issues and Enhancements in 3.0

Component

Resolved Issue

Change Request

General Korean code page issuesrepeating characters in the Editor and import and export issueshave been addressed or resolved. CR#201538
Case#484626
Option to have Toad remove comments from SQL before execution has been implemented under Tools | Options | Database | DB2. CR#213765
Case#529227
Connection information is now being properly added to the support bundle. CR#213808
Installation Silent installation is now available. CR#200792
Case#481561
Connection Manager
In the Client Configuration wizard, the Authentication field now has an Not Specified (NOSPEC) option. CR#201753
Case#481133
The Operating System drop-down list on the Add a Host  page in the Client Configuration wizard now uses a single Windows option to represent all Windows types. CR#204638
Case#491829
Previously, if you upgraded IBM DB2 for LUW version 9 from FixPak 0 to FixPak 1, specifying the Work with Existing option, Toad for DB2 might issue an exception error when you tried to establish a database connection. To resolve the issue, Toad for DB2 version 3.0 now ships with the IBM DB2 for LUW version 9 FixPak 1 modules. CR#204844
Database Browser/ Obj Palette
You can now remove columns when altering a table. CR#156271
Case#391667
Performance time in generating table scripts has improved significantly. CR#191534
Case#460284
The expand bar between the Parent Table Information and the This Table sections is working properly. CR#192553
Case#462812
You can now generate DDL for dependencies (for example, triggers, views, grants, indexes, procedures, and so on) from the Script tab if you select Generate script for dependent objects. CR#195671
Case#468471
The USER and GROUP keywords are now properly generated in the GRANT statement of the table DDL. CR#196653
Case#472046
Newly created indexes are now showing in up on the Indexes tab on the right-hand side of the browser. CR#197858
Case#474681
Issues with separators in trigger scripts has been resolved. CR#201407
Case#480305
DDL script now shows ALLOW REVERSE SCANS on indexes. CR#201389
Case#484643
Table editor now supports both COMPRESS and VALUE COMPRESSION. CR#202702
Case#490028
CLOB columns now display their size with the correct byte designation. CR#204490
Case#494668
You can now generate the DDL for the selected objects and its dependencies from the Script tab if you select Generate script for dependent objects. CR#204491
Case#494685
Adding a container to a tablespace no longer generates the error "SQL0104N An unexpected token '-' was found following 'ADD TO STRIPE SET.'" CR#204658
Case#493644
DDL script now shows WITH DEFAULT clause. CR#206226
Case#498970
The error generated when processing a view script no longer occurs. CR#209844
Case#507431
The user can now use the lower-left green button to toggle between edit and read-only mode on the Data tab. CR#209106
Case#511935
The error "Object reference not set to an instance of an object" generated when browsing the Used By tab for tables could not be reproduced. CR#214721
Case#522183
The errors generated when clicking between different tables in the browser cannot be reproduced. CR#214723
Case#522187
Generating the script for a view on the Script tab no longer produces a script-processing error. CR#218072
Case#531345
You can now filter by the number of rows when setting schema filters. CR#187906
Trigger DDL no longer displays as an unformatted single row on the Triggers tab for a table. CR#201408
Double-clicking on a trigger on the Trigger tab for a table now takes you to that trigger in the browser. CR#201410
Debugger The "Unable to initialize debug session" error that is generated when you attempt to debug procedures in DB2 for LUW is a DB2-related issue. A future release of a DB2 unified debugger should help reduce the occurrence of this issue. CR#213765
Case#517909
Case#529227
Editor Toad has normal limitations on the performing row counts. CR#199771
Case#479827
If user changes the schema in the drop down, both SET CURRENT SCHEMA and SET CURRENT SQLID statements will be executed. CR#205955
Case#497777
The data grid no longer locks down after data is changed and the query rerun. CR#210700
Case#502892
You can now use the same parameter name more than once for multiple tables in a query. CR#163853
The inability to generate a DDL script when the code pages on the server and client do not match is no longer an issue. CR#136103
Explain Plan The explain plan now supports Korean characters. CR#184449
Export Data (Toad core feature) When exporting a large amount of data, the user is now prompted to re-execute the currently running query to avoid reading the complete dataset into memory. CR#201720
Case#484690
Log Reader for DB2
The code page issue has been resolved. Connecting to a database no longer generates the error "Object reference not set to an instance of an object" and shuts down Toad. CR#219371
Case#534404
Search conditions in the Log Reader Advanced Search feature are processed with OR logic, not AND logic. CR#194746
A message now displays on the Redo tab on the DML/DDL page if UPDATE command is not supported. CR#202373
Log Reader now generates the correct Undo script to insert BLOB, CLOB, DATALINK, or LONG VARCHAR values in a table. CR#202602
An exception error is no longer generated when the user attempts to select a transaction on the Transactions page after canceling a rerun of the Read Log File wizard. CR#202699
Migration Issue with migrating Oracle stored procedures to DB2 is resolved. CR#172843
Case#422459
Object Search You can search Unicode databases. CR#166781
Schema Compare Schema Compare now shows differences in the DB2-generated name for the same procedure on the source and target, but will not generate an ALTER script. CR#218070
Case#529304
SQL Modeler (now Query Builder) SQL generated in the SQL Modeler could not be executed in the Modeler. This has been fixed. CR#183510
Case#441482
SQL Optimizer

(DB2 for LUW only) The SQL Optimizer toolbar icon is enabled only when you have Quest SQL Optimizer for DB2 installed. You can download SQL Optimizer from the following location as part of the Toad for DB2 Xpert Edition trial:

http://www.quest.com/toad-for-db2/Software_downloads.aspx

Once installed, click the SQL Optimizer toolbar icon in Toad to launch the SQL Optimizer.

CR#153015
SQL Recall You can now see the entire SQL query when you move the mouse cursor over the SQL Text entry in the SQL Recall window. CR#177941
Version Control Previously, some error messages are currently available with English language content only. This issue has been resolved by an overall design change. CR#140084

Known Issues

The following is a list of issues known to exist at the time of the Toad for DB2 release.

Feature

Known Issue

Change Request

General Customized options selected in the Configuration wizard are not applied if you are running as a Restricted user. CR#216699
Installation/

Upgrade

If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing to avoid losing functionality in some DB2 native tools. CR#192879
Case#462823
If you have multiple versions of Toad for DB2 or Toad for Data Analysis installed and you uninstall the product that was installed first, you might encounter errors when you start up the other Toad products. The error contains a call stack trace:
 

"System.NullReferenceException
Object reference not set to an instance of an object.
Stack Trace:
   at Quest.Toad.DB2.Common.DB2Utils.EnumerateClients
   (ClientInfo&defaultClient)
   at Quest.Toad.DB.DB2Provider..ctor()"

Workaround:
If you encounter the above error when you start up a remaining Toad product, do the following:

  1. Close the Toad product.
  2. Select Start | Programs | IBM DB2 | Toad_DB2_copy | Setup Tools | Default DB2 Selection Wizard, where Toad_DB2_copy is the DB2-installed copy of the Toad product (for example, TOADC31).
  3. Run the Default DB2 Selection wizard, specifying the Toad product as the default DB2 copy.
  4. Restart the Toad product.
CR#228164
Advanced ALTER (DB2 for LUW only) When performing an advanced ALTER on a view on which a trigger is defined, the advanced ALTER process does drop and recreate the trigger, thus invalidating it. CR#44,163
The advanced ALTER process currently does not propagate column name changes to dependencies. CR#44,495
(DB2 for z/OS only) When you alter a table to reduce the size of a column referenced in other tables via RI, the LOAD phase in the advanced ALTER fails with a DSNU334I INPUT FIELD INVALID error. The load cards show the original column length. CR#44,753
(DB2 for z/OS only) Any action that results in an advanced ALTER on a table that contains constraints results in the tablespace being placed in a check pending state. This occurs because Toad loads the table data before re-creating the constraints.

Workaround:

Run the IBM DB2 Check Data utility to remove the pending state from the affected tablespace. The data loads correctly and the constraints are enforced.
CR#222564
(DB2 for z/OS only) Toad cannot perform an advanced ALTER on a table that has a large number of columns. CR#227637
(DB2 for z/OS only) An advanced ALTER on a table that resides in an implicit tablespace does not execute RUNSTATS on the table once the table is re-created. CR#227672
Connection Manager
Manually configuring a connection using the Client Configuration wizard fails on a Windows 2003 64-bit machine. CR#202308
If Toad is running on a Vista machine that does not have another DB2 client installed, problems might occur when you use the Connection Manager to catalog databases. After you specify the connection information for a database, its catalog information does not display on the Client Configuration wizard Results window. Consequently, Toad cannot connect to the database.

Workaround:
Use either method:

  • Use the Client Configuration wizard to import connections.
  • Right-click the Toad for DB2 icon on your desktop, and select Run as. On the Run As window, select The following user and specify an administrator in the User name field. This workaround should enable you to use the Add Catalog Entry feature in the Client Configuration wizard to catalog databases.
CR#227752
Data Reports Currently, you cannot crate a Label Report in the Toad Data Report wizard. CR#215945
Database Browser/Obj Palette
Under certain conditions (currently being determined), a system exception error pops up on the Script tab for a selected tablespace when you select to generate the script for dependent objects.

Workaround: Click OK to close the error popup, and proceed.
CR#43,825
Currently, you cannot grant privileges to a tables' columns for users. CR#184359
Performance problems might occur when browsing a large number of database objects.

Workaround:
If performance issues do arise and caching is enabled (that is, Enable caching is selected in Toad on the Tools | Options | Database | Cache page), do the following to help maximize performance: Verify that the Maximum in-memory size value specified on the Cache page is greater than or equal to the Current in-memory value displayed. If necessary, increase the Maximum in-memory size value.

CR#220761
(DB2 for LUW only) Selecting the Uses tab for a package generates the DB2 database error "String data right truncation." CR#228752
Debugger Currently, the debugger does not support Unicode schema names. CR#184638