
Toad® for IBM DB2
Version 4.0.1 (Click here for previous versions)
Release Notes
November 12, 2008
| Third Party Known Issues | ||||
| System Requirements |
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.
Toad for DB2 4.0.1 is a maintenance release containing primarily internal fixes and enhancements to the 4.0 release, especially to the Object Migration feature.
For a description of resolved customer issues resolved in this release, see Resolved Issues and Enhancements in 4.0.1.
For a review of the updates and new features in the previously released Toad for DB2 4.0, refer to Updates in Toad for DB2 4.0 and New Features in Toad for DB2 4.0.
Note: The Log Reader component for Toad for DB2 (LUW) has been sunset and no longer ships with Toad for DB2.
Click to review enhancements in the following areas:
Updates to overall Toad environment include the following:
Additionally, new index recommendations are available to optimize overall Toad performance in your DB2 for z/OS environments. See Recommended Indexes to Optimize Toad Performance in DB2 for z/OS.
This release includes enhancements to the following areas of database administration:


After you specify the options for the overall migration on the Customize Migration page, you can update whether to migrate DDL, data, and statistics for individual objects:
Advanced alter scripts in DB2 for z/OS now generate -STOP and -START tablespace commands when necessary.
This release includes enhancements to the following data management features:
You can also save a result set and later use it for comparison. This is useful from the Database Explorer's Data tab when, over time, the data might be changing and can then be compared against this data that was saved.
This release includes enhancements to the following query development functionality:
If you select this action to generate an INSERT, UPDATE, DELETE, or CREATE statement with a single table or view already in the Query Builder, you cannot add another table or view because this action can only apply to a single table or view. Also, if you add more than one table or view to the Query Builder, this action is disabled because it only applies to a SELECT statement.
You cannot execute an UPDATE or CREATE statement in the Query Builder. Instead, click to send the statement to the editor and execute it there.
Note: If the cursor is positioned at the end of a line, the script runs from the beginning of that line through the end of the script.
To add this button to the editor toolbar, click
on the toolbar, and select Add or Remove Buttons | Editor| Execute From
Cursor.
Code completion options are located in Tools | Options | Editor | Code Completion:
The latest release of SQL Optimizer for DB2 LUW (3.0) is now available for Toad for DB2.
This release includes the following updates to version control functionality:
Toad now supports the Team Foundation Server (TFS) version control provider. In order to use TFS, you must install the Visual Studio Team Foundation Server MSSCCI Provider on the same computer as Toad.
Note: This is not the same client that you install with Visual Studio. You can download the MSSCCI Provider from one of the following locations:
2005 MSSCCI Provider: http://www.microsoft.com/downloads/details.aspx?FamilyID=87e1ffbd-a484-4c3a-8776-d560ab1e6198&DisplayLang=en
2008 MSSCCI Provider: http://www.microsoft.com/downloads/details.aspx?familyid=FAEB7636-644E-451A-90D4-7947217DA0E7&displaylang=en
For more information about configuring TFS, see Configuration Prerequisites in the help.
To eliminate identification errors, Version Control stores procedures with a new name format.
The following new features were added to this version of Toad for DB2:
The Automation tool is now available with Toad for DB2. Automation helps you build a script containing a sequence of activities--common SQL tasks--that you can execute immediately or schedule for later execution using Toad Job Management functionality. To invoke Automation, select Tools | Automation. Here are some of the Automation features:
| Select to File | Execute an existing SQL script or
Query Builder query and export the results to an Excel, HTML, or CSV
file. You can then use additional activities to add the exported
result file to a zip file, attach the file to an email, or copy the
file. Note: Bind variables are not supported for this activity. If bind variables are detected, a message alerts you during the test run of the automation script. |
| Execute SQL | Execute an existing SQL script or
Query Builder query. Note: Bind variables are not supported for this activity. If bind variables are detected, a message alerts you during the test run of the automation script. |
| Select to Editor with Results | Execute an existing SQL script or Query Builder query and save it and any results sets in a Toad editor file (.tef). This file format is useful for building scripts that have large result sets that you do not want to continue executing or for saving results when you have not finished building a script. |
| Export Wizard | Export data from databases, tables, views, or query into a CSV, Excel, or other file. You can save the export settings as a template that you can use for scheduled automation scripts. |
| Import Wizard | Import data from a CSV, Excel, or other file into a new table or append to an existing table. You can save the import settings as a template that you can use for scheduled automation scripts. |
| Toad Pivot Grid | Refresh an existing Toad pivot grid and export results to a report. You can then use additional activities to add the pivot grid to a zip file, attach it to an email, or copy it. |
| Delete File | Delete one or more files from a specified location. |


Toad for DB2 offers a new set of features that manage space in your DB2 for LUW environments:
Space Estimator (when creating a tablespace)
Space Calculator lets you simulate adding and deleting objects and updating object sizes to determine the impact these changes might make on space usage in a DB2 for LUW tablespace. Space Calculator also provides options to run maintenance utilities on objects and to generate scripts that actualize your space-usage scenarios.
Note: To provide accurate SMS tablespace information, Toad requires that the BUFFERPOOL database manager monitor switch be turned on.
To access this feature, right-click one or more tablespaces, tables, or indexes in the Database Explorer or Object Explorer, and select Space Management | Space Calculator. Or right-click objects in an object list, and select Tablespace (or Table or Index) | Space Management | Space Calculator.

The Space Exceptions feature is an online report that identifies those tables and indexes in your DB2 for LUW database that would benefit from a reorganization to improve space usage and performance. From the report, you can open a Toad for DB2 Reorg or Runstats session on those objects that require maintenance.
To access this feature, right-click one or more tables or indexes in the Database Explorer or Object Explorer, and select Space Management | Identify Exceptions. Or right-click objects in an object list, and select Table (or Index) | Space Management | Identify Exceptions. You can also select Tools | Identify Exceptions and drag objects on to the report.

The Table Partition Analysis tool helps you determine how best to redistribute the data among the current data partitions in a DB2 for LUW table. Using this tool, you set up data distribution scenarios. Table Partition Analysis then calculates the number of table rows that DB2 would store in each partition for the current scenario and shows a graphical depiction of this data distribution. Once you determine the best scenario for redistributing the data, you can have Table Partition Analysis generate the script that alters the data partitions using the scenario values and redistributes the table data accordingly.

The new Space Usage tab for Tablespaces in the Database Explorer reports current space-related information (gathered from the system catalog) for a selected tablespace in your DB2 for LUW database. The tab shows space allocation for the tablespace itself, for the containers that make up the tablespace, and for the objects that reside in the tablespace.
Note: To provide accurate SMS tablespace information, Toad requires that the BUFFERPOOL database manager monitor switch is turned on.

When you create a DB2 for LUW tablespace, use the Space Estimator page in the Create Tablespace window to estimate the size of the tablespace you are creating. You can then apply these estimations to help you adjust container space or select appropriate containers in the tablespace definition.

Toad introduces SQL Tuning for DB2 z/OS to help you optimize SQL that you execute in your DB2 for z/OS environment. SQL Tuning provides an interactive workspace in which you tweak the SQL in various scenarios and then run Explains on the scenarios to compare their access plans, costs, I/O and CPU usage, and results. To assist you in optimizing SQL, SQL Tuning generates and implements tuning advice for each scenario.
SQL Tuning is integrated with other components in Toad for DB2 to accommodate your workflow. For example, during your Toad session you can do the following:



New functionality supports even more DB2 utilities and commands:
Toad provides an easy way to compare and synchronize data in your tables. The Data Compare wizard (Tools | Compare | Data Compare) sets up and runs data comparisons based on specific columns and keys in one or more source and target tables:

Data Compare then builds the synchronization script for you:

The editor now provides the DB2 for z/OS command support described below. This support requires that the Quest IBM DB2 z/OS component, available with Toad for DB2 3.0 or later, be installed. For more details, see the Quest IBM DB2 z/OS Component Installation Guide that resides in your Toad installation folder.
You can now reverse engineer queries from the Editor or Query Builder. For more information, see Reverse Engineer Queries in the help.
Toad automatically saves a backup copy of open editor files that have been modified at five minute intervals (default). It also saves a backup copy anytime you execute the SQL. If the application does not terminate normally, the next time you open Toad the backup copies automatically open in the editor so you can either save changes to your regular file or discard them.
You can specify the backup interval in Tools | Options | Environment | General:

Note: You cannot load multiple copies of Toad when this option is selected.
This release adds new functionality to edit catalog statistics for tables; edit multiple tables and tablespaces from one Alter window; rebuild indexes, triggers, and views; and manage array types in your DB2 for LUW environment.
Click the following links to view issues addressed and enhancements implemented in the Toad for DB2 4.0 releases, including this latest release 4.0.1:
|
Feature |
Resolved Issue |
Change Request |
| Advance Alter | Under certain alteration scenarios, Toad for DB2 no longer attempts to perform an advanced alter when it should perform a native alter. |
CR#55,919 Case#669082 |
The following is a list of issues addressed and enhancements implemented in Toad for DB2 4.0:
|
Feature |
Resolved Issue |
Defect ID |
| General | Toad properly recognizes and opens files with customized extensions. |
ST#43,045 Case#581738 |
| The maximum row size property on the Properties tab for tables and in Space Calculator now displays the correct value. |
ST#43,717 CR#23009 Case#137125 |
|
| Launching the ToadSoft page when you start Toad no longer generates a runtime error. |
ST#47,130 Case#606245 |
|
| Documentation has been updated to reflect accurate system requirements. |
ST#49,398 Case#611732 |
|
| Installation/Upgrade | 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 no longer encounter errors when you start up the other Toad products. |
ST#42,863 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 handles the dependent trigger properly. | ST#44,163 |
| Advanced ALTERs properly propagate column name changes to dependencies. | ST#44,495 | |
| (DB2 for z/OS) CHECK DATA runs properly and no data is lost. |
ST#42,478 CR#222564 |
|
| (DB2 for z/OS) The Editor now provides an error message, stating that utility statements in the script are too long for DSNUTILU to execute. |
ST#42,800 CR#227637 |
|
| (DB2 for z/OS) 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. |
ST#42,805 CR#227672 |
|
| Synonyms are now being correctly dropped and recreated during advanced alters on tables. |
ST#49,317 Case#623821 |
|
| (DB2 for LUW) IMPORT statement used to reload data is now correct. |
ST#51,564 Case#638205 |
|
| Data Grid | Row counts in data grids now factor in any filters currently in effect. |
ST#42,212 CR#218084 Case#531359 |
| You can now sort the grid on timestamp columns. |
ST#42,831 CR#227854 Case#565520 |
|
| The DateTime Format option in Tools | Options | Environment | Grid lets you customize the format of DATE data types. |
ST#46,825 Case#604546 |
|
| Grid is handling LOB data correctly. |
ST#53,071 Case#649374 |
|
| Database Explorer/Object Explorer | The Script tab correctly generates script for constraints. |
ST#42,095 CR#214719 Case#522646 |
| The "Generate script for dependent objects" option has been removed from the Script tab. Instead, use the DDL Script wizard or the Migration feature to generate scripts for objects and their dependencies. (In the Object Migration wizard, select Empty database for the target Connection type field.) | ST#43,825 | |
| (DB2 for LUW) Selecting the Dependencies tab (or any tree node listed on this tab) does not generate a string data truncation error. (The Uses tab no longer exists.) | CR#228752 | |
| Selecting to view table properties no longer generates an error. |
ST#43,591 Case#584688 |
|
| This issue is closed as duplicate of ST#42,714. The issue, which requests the ability to revoke all permissions for a user, is slated as an enhancement in Toad for DB2 4.5. |
ST#43,715 CR#13731 Case#385909 |
|
| The Properties tab for tables now contains the Average Row Size property. |
ST#43,718 CR#25896 Case#123556 |
|
| (DB2 for LUW) Toad now generates the correct SECQTY value in table, tablespace, and index DDL scripts. |
ST#46,377 CR#224710 Case#555187 |
|
| (DB2 for LUW) Toad now generates the correct LOCKSIZE value in table DDL scripts. |
ST#46,755 Case#603740 |
|
| (DB2 for z/OS) A procedure compiles successfully after you alter the procedure to add a DATE parameter. |
ST#46,881 Case#602203 |
|
| (DB2 for LUW) This release has add support for multi-dimensional clustering in tables. |
ST#47,073 Case#606985 |
|
| Errors generated on the Uses and Used By tabs are resolved with the new Dependencies tab, which replaces both tabs. |
ST#47,473 Case#609367 |
|
| The AS LOCATOR is maintained correctly in procedures. |
ST#48,262 Case#614750 |
|
| (DB2 for z/OS) Toad is now handling columns with the DATE data type correctly in scripts. |
ST#48,358 Case#609803 |
|
| (DB2 for z/OS) Toad handles runtime errors during procedure execution correctly. |
ST#48,558 Case#618140 |
|
| (DB2 for z/OS) Template support is now available for the tablespace editor. |
ST#48,805 Case#620485 |
|
| (DB2 for LUW) Browsing wrappers no longer generates an SQL error when you attempt to view the nicknames (on the right side) belonging to a server using the wrapper. |
ST#51,272 Case#636134 |
|
| DDL Wizard | When generating the DDL for an entire database, the DDL Script wizard correctly includes the DDL for tablespaces. |
ST#42,601 CR#225294 Case#558303 |
| The wizard is now correctly generating DDL for indexes for a table when the option to include DDL for dependents is selected. |
ST#42,798 CR#227632 Case#570062 |
|
| The BIND step is now located in the correct location within the DDL script for tablespaces when the option to include DDL for dependents is selected. |
ST#47,459 Case#609087 |
|
| When the wizard generates the script for an entire database, the table DDL is now correctly positioned before the view DDL. |
ST#48,185 Case#614918 |
|
| Editor | The editor is now correctly showing and using the default schema. |
ST#42,648 CR#225945 Case#558865 |
| The View Objects at Cursor feature (object lookup) now works correctly for DB2 functions and procedures. |
ST#42,676 CR#226267 Case#562264 |
|
| Code completion lists are behaving properly in the editor. |
ST#43,396 Case#584404 |
|
| When you select Generate SQL | To Editor from the Object Explorer, a new editor document opens. (Previously, the SQL statement was appended to an already opened editor.) This new behavior is consistent with selecting the option from the Database Explorer. |
ST#50,462 Case#629170 |
|
| Export Data (Toad core feature) | The export of a large number of rows (more than one million) to Excel 2007 does not generate errors. |
ST#42,006 CR#211832 |
| All Toad components are working as designed. The Toad Export wizard does not invoke DB2 utilities and therefore does not allow data export to an IXF format. However the Toad for DB2 Export feature, available with the DBA edition, does support the DB2 EXPORT utility and therefore provides the option to export to an IXF format. |
ST#47,849 Case#613403 |
|
| Import Data (Toad core feature) | When running in the foreground, the Import wizard has no issues with quitting. |
ST#48,310 Case#609914 |
| Migration | (DB2 for z/OS only) On the Define Transformation Rules and Migration Options page in the Migration wizard, you can now use a non-qualified name to map to an non-existent tablespace. Migration qualifies the tablespace with the default database DSNDB04. | ST#44,127 |
| (DB2 for LUW only) The wizard now allows you to map container paths to support migration between Linux, Unix, and Windows platforms. | ST#44,537 | |
| (DB2 for z/OS only) The script correctly references mapped bufferpools or storage groups for implicit tablespaces you are migrating. |
ST#43,026 CR#229351 |
|
| Customer was notified that the existing Ignore foreign key differences option in the wizard suppresses migration of foreign keys when the Include objects referenced... and Include objects that are dependent... options are not selected. |
ST#43,721 CR#225723 Case#560060 |
|
| AUTORESIZE is now included in migration script. |
ST#53,533 Case#653042 |
|
| Query Builder | The HAVING condition is now a Builder component you can apply to any column as long as the query includes the GROUP BY clause. |
ST#42,039 CR#212986 Case#518043 |
| When you drag and drop a table containing a column name identical to a column name in another table already on Query Builder drawing surface, the drawing now longer appends a _1 to the column name in the newly added table. While the name with the appended _1 was simply an alias, it was confusing. | ST#44,499 | |
| Schema Compare | Schema Compare does not lose modal control when you switch to other applications and then return to Toad for DB2. |
ST#42,918 CR#228524 Case#572883 |
| Utilities (DB2 for LUW) | This release includes an easy-to-use interface for the SET INTEGRITY utility. |
ST#43,224 ST#43,719 CR#33134 Case#584024 Case#153951 |
| Version Control |
(CVS only)
You can now enter the user name in the Username or Server field. If a conflict exists, Version Control asks you to clarify. |
ST#42,867 CR#228200 |
The following is a list of issues known to exist at the time of the Toad for DB2 release.
|
Feature |
Known Issue |
Defect ID |
| General | Customized options selected in the Configuration wizard are not applied if you are running as a Restricted user. | CR#216699 |
| (DB2 for z/OS) Toad has issues when handling LOBs. These issues can occur, for example, when you attempt to migrate auxiliary tablespaces, preserve LOB data in advanced alters, or generate DDL for base table dependencies. | ST#53,640 | |
|
As a security measure in Windows Vista, when a standard user belonging to an Administrators group launches a
process and the Vista User Access Control security feature is
enabled, the process launches with only standard user privileges.
However, under these restricted privileges, Toad can have problems cataloging DB2
systems (including transferring a DB2 catalog at Toad setup) and running
utilities through CLP, thus affecting advanced alters and other Toad
functionality.
Additionally, this user does not have write access to the Toad default storage folder (the Toad installation folder) where files, such a the license key file and export profiles generated in the Client Configuration wizard, are stored when no explicit path is specified. Instead, Vista automatically copies files to C:\Users\db2admin\AppData\Local\Virtual Store\Program Files\Quest Software\Toad for DB2 version. The Toad user can have the following issues:
Workaround: |
N/A | |
Toad
DB2 4.0 installs a db2cli.ini file, which is set to have connections
connect to the catalog node.
If you need to change this node specification for any reason, use the
following steps to edit the file:
|
ST#53,860 | |
| Installation/ Upgrade |
If a Vista standard user belonging to an Administrators group attempts to
uninstall Toad when the Vista User Access Control security feature is
enabled, the uninstall might hang. Workaround: Turn off the User Access Control security feature and then uninstall. |
ST#52,914 |
| 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 | |
| Network and LAN installations are currently not supported. | N/A | |
| Advanced ALTER | ||
| (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. | ST#44,753 | |
| Connection Manager | ||
|
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. |
CR#166752 Case#408845 | |
|
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:
|
ST#42,813 CR#227752 | |
| Data Reports | Currently, you cannot create a Label Report in the Toad Data Report wizard. |
ST#42,133 CR#215945 |
| Database Explorer/Object Explorer | ||
| Currently, you cannot grant or revoke privileges table columns. |
ST#41,786 CR#184359 | |
|
Currently, no option exists that allows the user to remove notes on
objects in the Database Explorer. Workaround: Open the note, delete its contents, and click OK. The note and its indicator are removed. |
ST#52,941 | |
|
Performance problems might occur when browsing a large number of
database objects. Workaround: |
CR#220761 CR#220757 | |
| Debugger | Currently, the debugger does not support Unicode schema names. |
ST#41,770 CR#184638 |
| Editor | ||
The following object types are not found when using the View Object at
Cursor feature:
|
ST#41,627 CR#164917 | |
| When you edit a script in Toad, you must delimit SQL identifiers that begin with @ to differentiate these identifiers from named parameters. For more information, refer to the following IBM documentation: |
CR#224375 Case#552946 | |
| Export Data (Toad core feature) | Binary data types cannot be exported in this release. |
ST#41,665 CR#170430 Case#419715 |
|
When exporting large result sets (approximately 500K), you might run out
of memory before the operation completes. Workaround: Create a view for the query and export that view. |
ST#41,935 CR#203483 Case#483802 | |
| Help in Toad | The help does not state the DB2 restriction that you cannot drop packages containing triggers | N/A |
| Query Builder | ||
| Indicators for notes created on relationships in the Query Builder and in ER Diagrammer are not showing. | ST#52,943 | |
| Schema Compare | ||
| (DB2 for LUW only) If the source schema contains a table alias with the same name as the target schema, synchronizing the schemas results in the target schema name being replaced with the actual table name from the source table. | CR#140343 | |
| (DB2 for z/OS only) A comparison of materialized query tables generates an "undefined name" error. |
ST#42,913 CR#228511 | |
| Synchronization script does not create tablespaces on target. |
ST#41,983 CR#210132 Case#491910 | |
| Version Control | ||
|
The Update Schema function for version control often requires that
objects be dropped and recreated. If tables are referenced by foreign
key constraints, the following error occurs when executing the script: "Could not drop object N because it is referenced by a FOREIGN KEY constraint." |
ST#42,093 CR#214601 | |
| Currently Version Control handles only DB2-standard schema names and file and folder names that are compatible with the underlying Version Control repository. |
ST#42,184 CR#217475 | |
| You currently cannot check object list definitions into version control. |
ST#42,188 CR#217524 | |
| (CVS only) Each version control configuration should point to a unique Root Folder location on the Source Repository to avoid conflicting file usage. | CR#228422 | |
|
(CVS only) You
might receive an "Unknown Error..." message when using the sspi protocol
to connect to a CVSNT server. Possible
Workaround: |
CR#226256 | |
|
(CVS only) You cannot successfully configure CVS using the SSH protocol. Workaround:
|
CR#228718 |
The following is a list of third party issues known to exist at the time of the Toad for DB2 release.
|
Feature |
Known Issue |
Change Request |
| General | You cannot insert a double-byte character into a database with a single-byte codepage. IBM PMR30857,756,000 states that this configuration is not supported. |
CR#220327 Case#537948 |
| (DB2 for LUW only) Certain Toad functions use the DB2 snapshot monitor to capture information about containers used in a database. To capture this information in a multi-partition database, the snapshot monitor requires that all database partitions be active. Therefore, to ensure that Toad obtains container information across all partitions, execute the DB2 command ACTIVATE DATABASE real_database_name on the server before connecting Toad to the database. This command keeps all partitions on the database active. For more information about ACTIVATE DATABASE, refer to the IBM DB2 for Linux, Unix, and Windows documentation. | N/A | |
|
Installation/ Upgrade |
You cannot install DB2 for LUW 8 on the same system that already has Toad for
DB2 4.0 installed. This problem exists because of a current DB2 limitation in
which DB2 for LUW 8 cannot be installed on a system on which DB2 for LUW
9 resides. (Toad for DB2 includes a customized version of DB2 for LUW 9.) Workaround: |
CR#187913 |
|
An SQL0805N error occurs when performing a DML statement on a database. Workaround: |
CR#220160 | |
| Database Explorer/ Object Explorer | (DB2 for z/OS only) There is a known z/OS issue when attempting to ALTER partitioning index values for PRIQTY and SECQTY. If these values are changed in Toad, the subsequent ALTER statement is generated without ENDING AT values for the partition keys. The generated syntax is correct; however a database error will occur. IBM has issued z/OS APAR PK69271 to address the issue. | ST#49,829 |
|
(DB2 for z/OS only) Attempting to drop a distinct type or sequence with a delimited
blank name results in following error due to server side abends: "IBM][CLI Driver] CLI0108E Communication link failure. SQLSTATE=40003" This is a known IBM DB2 issue and IBM has opened APAR PK3269 to track this issue. |
N/A | |
| (DB2 for z/OS only) In some cases, a user can revoke INSERT privileges on a table for the owner and cause a cascading revoke of privileges for any user (including the revoker) who was granted privileges by the table owner. This is a known IBM DB2 issue and IBM has opened APAR PK30558 to track this issue. | N/A | |
| Schemas containing empty names or special characters are not supported in this release and will display as QUEST_SCHEMA_PLACE_HOLDER when used. |
CR#133127 CR#133139 |
|
| A Microsoft .NET Framework issue causes an exception error when you attempt to browse the Data tab for a table containing a decimal value with a precision greater than 28 or 29. This issue is described in http://msdn2.microsoft.com/en-us/library/xtba3z33(vs.71).aspx. | CR#186529 | |
|
(DB2 for z/OS only) The following DB2 error is generated when you try to refresh an MQ table: "ERROR [58031] [IBM] SQL1034C The database is damaged..." This error is identified in APAR PQ97328. The APAR states that, if the statement text in the CREATE TABLE statement for a materialized table is more than 4K, the statement text stored in the SYSVIEW.VIEWS catalog table entries for the table (after the first three sequence number entries) contains unusable data. The APAR has been fixed with PTF UK00557. However, any materialized tables created before this fix need to be dropped and recreated and REFRESH rerun. |
N/A | |
| Timestamp data causes exceptions when you click the Data tab or attempt to query the table. This issue is related to the IBM DB2 APAR IY87346. | CR#220839 | |
| Data Grid | Attempting to update a table column value that is not generated causes an error when another column in the table is defined as GENERATED ALWAYS. This issue is related to the DB2 9.5 APAR JR30189, which IBM expects to fix in a future 9.5 fixpak. | ST#51,035 |
|
(DB2 for z/OS only) Tables that contain decimal data larger than 28 or 29 decimals
results in an error stating:
"Value was either too large or too small for a Decimal." This is due to a limitation in the .NET Framework in which the maximum decimal that the Framework can handle is 10^31 with 0 decimal.
Workaround:
Note: When using this workaround, if the number of characters is less than 32, leading zeros display. |
CR#186529, CR#186535 |
|
|
You cannot add data to tables that include columns that have the GENERATED
ALWAYS AS option enabled. The IBM Command Builder generates the INSERT statement
and includes the generated always column, which results in the following error:
"A value cannot be specified for column "GEN" which is defined as GENERATED ALWAYS. SQLSTATE=428C9" Workaround: |
CR#142504 | |
| Debugger | When compiling with debug, it is recommended that you disable AutoCommit (Tools | Options | Database | General) to allow a rollback if there is a problem when dropping and creating the procedure. Once you successfully create the procedure, commit the changes before starting the debugging session. | N/A |
| When debugging, you must enter a value for every start parameter, regardless of whether they are input or output values or an error message incorrectly informs you that the procedure must be compiled with debug information. | CR#143234 | |
|
(DB2 for LUW only) 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 [57011] [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: |
CR#188846 | |
| (DB2 for z/OS only) A message stating that a procedure is not compiled with the Debug code, when in fact it is, is being generated. This issue is due to an error in the z/OS implementation of Create_Session. | CR#207662 | |
| 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. |
Case#517909 Case#529227 CR#213765 |
|
| Editor |
Attempting to create an object in the SQL Editor when the schema selected from
the drop-down list in the Editor toolbar is different than the schema you logged
into, results in an error. Toad issues a SET CURRENT SCHEMA statement the
first time you execute a script/statement. Workaround:
|
CR#183855 |
| Dropping a nickname does not drop its primary key. This issue (PMR 30432,756,000) was fixed in DB2 9.1 Fixpak 3. |
ST#42,503 CR#223155 |
|
| Export Data (Toad core feature) |
In order to export to an Office 2003 or 2007 Excel instance, the Office 2003 Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from
one of the following locations: |
CR#138239 |
| Schema Compare | (DB2 for LUW only) You cannot synchronize schemas if the Code Pages on the compared schemas do not match. | CR#141383 |
| Space Management | (DB2 for LUW only) APAR IY90197 states: RUNNING SNAPSHOT TABLE FUNCTIONS CAN CORRUPT MEMORY INSIDE THE DB2FMP (C) PROCESS DUE TO STACK OVERFLOW. This issue was fixed in DB2 8.1 Fixpak 14. | N/A |
Please review upgrade information in the Toad for DB2 Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.
Verify that your system meets the minimum requirements described in the following sections:
Requirement for Capturing Container Information in a DB2 for LUW Multi-Partition Database
Recommended Indexes to Improve Toad Performance in DB2 for z/OS
Toad for DB2 client installation requires the following.
Note: 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.
| Platform | 1 GHz minimum |
| Memory | 512 MB of RAM minimum, 1 GB recommended Note: The memory required may vary based on the following:
|
| Hard Disk Space | 185 MB of disk space required to run Toad If installing the Toad SQL Tuning for DB2 z/OS component, allocate an additional 45 MB. If installing the Quest SQL Optimizer for DB2 LUW, refer to the Release Notes for that product for disk space requirements. |
| Operating System | Any of the following:
|
| Additional Software |
.NET Framework Microsoft .NET Framework 2.0 or later Note: Consider the following:
Browser Note: Toad installs a DB2 9 client as part of the installation process. The DB2 9 client can co-exist with an existing DB2 8 client; however, it is incompatible with a DB2 7 client. If a DB2 7 client is already installed on the system, the Toad installation stops and cannot complete. You must upgrade to the DB2 8 client and restart the Toad installation to avoid losing functionality in some DB2 native tools. PDF Viewer |
| Other Requirements | SVGA monitor with a minimum resolution of 800x600, 1024x768 recommended |
Each DB2 database server requires the following:
| Database Versions |
IBM® DB2 for z/OS 8.1 or later Note: At this time, Toad supports DB2 for z/OS running in Full Function mode, but does not support DB2 running in Compatibility mode. IBM DB2 for Linux, UNIX, and Windows (LUW) 8.1.5 or later Note: To run RUNSTATS and the native REORG utility on tablespaces and indexes, Toad supports version 8.2.2 or later. |
| Database Operating System Platforms | z/OS (V1R6 Base Services [5694-A01] or later)
|
The following are user requirements for installing and running Toad:
Only Administrators and Power Users can install Toad.
Note: The following exceptions exist for Power Users:
If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and menu items with any user--a Power User, Restricted User, Vista standard user--on the computer.
If a Power User installs Toad, a Restricted User cannot do the following:
The following describes the requirements and restrictions for users who launch and run Toad:
http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSAuthorizations.doc
- Select Control Panel from the Windows Start menu.
- Double-click Administrative Tools.
- Double-click Microsoft .NET Framework 2.0 Configuration.
- Select My Computer, and then select the Runtime Security Policy node.
- Select Evaluate Assembly from the list of tasks in the right panel and browse to the location of Toad.exe in the File field.
- Click Next and set the permission to Unrestricted.
Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server Service Pack 2 using the Metaframe Access Suite 4.0 and Citrix Presentation Server Clients 10.2. For information about installing Toad in a Citrix environment, refer to Install Toad on Citrix Systems in the Toad for DB2 Installation Guide.
To connect to a Lightweight Directory Application Protocol (LDAP) server, you must enable LDAP support and specify the host name and port number of the LDAP server for the DB2 client installed with Toad.
Note: Keep the following mind:
To configure Toad to use LDAP
db2set DB2_ENABLE_LDAP=YES
db2set DB2LDAPHOST=hostname[:port]
The port number defaults to 389 (default LDAP port) if you leave the port number blank.
Databases on the LDAP server should now be available from the Database Alias drop-down list in the Connections window. To complete the Toad connection setup, you must create a Toad profile for each database. See Create Toad Connection Profiles in the Toad for DB2 Installation Guide.
Certain Toad functions use the DB2 snapshot monitor to capture information about containers used in DB2 for LUW databases. To capture this information for a multi-partition database, the snapshot monitor requires that all database partitions be active. Therefore, to ensure that Toad obtains container information across all partitions, execute the DB2 command ACTIVATE DATABASE real_database_name on the server before connecting Toad to the database. This command keeps all partitions on the database active. For more information about ACTIVATE DATABASE, refer to the IBM DB2 for Linux, Unix, and Windows documentation.
The following are the requirements for using Toad to compile and debug stored SQL procedures in DB2 for z/OS.
To use the Toad debugger on stored SQL procedures, the following Toad client requirement must be met:
Each DB2 subsystem on which you want to compile and debug stored SQL procedures must meet these requirements:
To bind and rebind packages and plans and to invoke utilities during advanced ALTERs on a DB2 for z/OS subsystem, Toad for DB2 requires the following:
If you neither product is installed on a subsystem, run edit and run the DDL that creates these objects. Click the following link to open the file containing this DDL:
http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadzOSTemplateDDL.txt
Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.
User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects in Toad. The following link contains the DDL for indexes that can optimize Toad performance on your DB2 for z/OS subsystem. Keep in mind that the creation of these indexes is a recommendation only. The indexes can have different results in different environments, depending on the number of DB2 objects and the amount of data involved. To create these indexes, edit and run the DDL contained in the following file:
http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSIndexes.txt
Additionally, if the schema drop-down lists in the Object Migration wizard populate slowly, consider creating an index on the SCHEMA and CREATOR columns in the catalog table for each object type. Here is a list of some of the object-type tables:
SYSIBM.SYSSYNONYMS
SYSIBM.SYSSEQUENCES
SYSIBM.SYSROUTINES
SYSIBM.SYSTABLES
SYSIBM.SYSDATATYPES
SYSIBM.SYSINDEXES
SYSIBM.SYSTRIGGERS
SYSIBM.INDEXES
The following are requirements for using Toad's Object Migration wizard to migrate DB2 objects and their dependencies.
When migrating a table that has referential-integrity relationships to other tables, select Include objects referenced by those originally selected and Include objects that are dependent upon those originally selected on the Customize Migration page in the wizard. These options generate the statements necessary in the script to migrate the related tables. If you do not select these options, edit the migration script to include these statements.
The following requirements and restrictions exist for source and targets:
Note: When you are migrating objects between different versions, the Migrate catalog statistics on the Customize Migration page in the wizard is disabled.
Toad for DB2 supports the following version control providers for the versions and platforms listed. Testing is not complete for versions and platforms not listed:
| Supported Provider | Server Version Tested | Client Version Tested |
| Visual SourceSafe (VSS) | VSS 6.0d | VSS 6.0d |
| Concurrent Versions System (CVS) | CVS 1.11.22 on Solaris CVSNT 2.5.03 on Windows |
CVNT 2.5.03 |
| Subversion | Subversion 1.4.2 | Subversion 1.4.2 |
| Team Foundation Server (TFS) | TFS 2005 | Visual Studio 2005 Team Foundation Server MSSCCI Provider |
Ensure that you install the following on the same computer on which you installed Toad.
Note: Toad connects to your version control system based on login information included in your configuration. Your version control client does not need to run for Toad to connect.
| Provider | Prerequisite |
| VSS | VSS client |
| CVS | CVS client |
| Subversion | Subversion binary package Note: When configuring version control in Toad, specify the binary path in the BinaryPath field on the Command Based Version Control Properties page in Toad. Do not include the executable file name in the path. |
| TFS | Visual Studio Team Foundation Server MSSCCI
Provider client Notes:
|
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 is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.
This release has the following known capabilities or limitations:
The Toad SQL Tuning for DB2 z/OS feature supports single-byte character sets. Double-byte or multi-byte character sets are not supported. All product components should be configured to use the same or compatible character encodings and be installed to use the same locale and regional options.
The Knowledge Xpert feature is available with English language content only.
The Toad for DB2 release package contains the following products:
For important information about installing Toad for DB2, refer to the Toad for DB2 Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.
Caution:
|
For instructions on installing the Quest IBM DB2 z/OS component, refer to the Quest IBM DB2 z/OS Component Installation Guide. This guide is available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our Web site for regional and international office information.
(Commercial and Trial Support only)
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.
(Freeware Support)
You can join the Toad for DB2 discussion group by sending an email to: toad_db2-subscribe@yahoogroups.com
© 2008 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
Refer to our web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix, AppAssure, Benchmark Factory, Big Brother, ChangeAuditor, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
Toad for DB2 contains some third-party components (listed below). Copies of their licenses may be found on our web site at http://www.quest.com/legal/third-party-licenses.aspx.
CONTAINS Runtime Modules of IBM DB2 Runtime Client Merge Modules Version 9; Copyright IBM Corporation 2006 All Rights Reserved
| Component | License or Acknowledgement |
|
EDraw Office View 5.3 |
Copyright © 2008, EDrawSoft |
|
IBM DB2 Client Merge Modules Version 9 |
CONTAINS Runtime Modules of IBM DB2 Runtime Client Merge Modules Version 9; Copyright IBM Corporation 2006 All Rights Reserved |
|
SharpZipLib 0.84 |
The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.