Toad® for IBM DB2

Version 4.7.2 (Click here for previous versions)

Release Notes

August 11, 2011


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 4.7.2 is maintenance release containing primary fixes and enhancements to the previous 4.7.1 release.


Previous Features and Updates in Toad for DB2 4.7 and 4.7.1


Click to review updates and new features in the following areas:

Note: The features described in the following sections apply to the commercial version of Toad and might not be available in the freeware version.

Support for DB2 for LUW 9.7 Features

Toad provides the following support for DB2 for 9.7 features:

Prerequisites and Installation

General Toad Environment



You can now view RSS and Twitter feeds, including Toad Community postings from within Toad using the new Collaboration window. You can access this window from View | Collaboration. Once the window opens, click any entry to open the related content.

When you open the Collaboration window, it polls all RSS and Twitter feeds that you have defined in the Collaboration options page (Tools | Options | Environment | Collaboration). The first time you open the Collaboration window, you are prompted to configure RSS and Twitter options.

In the Collaboration window, click at the top of the window to compose a new entry. You can select the drop-down arrow beside the icon to select which feed you want to post to.

To tweet, use the entry field at the bottom of the window. If you click an item in the list, a reply tweet is entered in the field. If the post contains a link, that link is opened in the Web Browser as well. To post a tweet, press ENTER or click . If you click , you can toggle whether you want to include a screen shot of Toad with your post. (After posting, this option always reverts back to False.)

Database Administration

Click a category in the list to view the features and updates for this release:

Object Explorer

Object Search

For objects with columns, Object Search results now show column types and lengths.

Object Management - General

The Object Compare wizard now includes a Diff Viewer to help you identify changes across database objects.

Object Management - DB2 for LUW

Object Management - DB2 for z/OS

ER Diagram/Database Diagram

 Back to Start of Section

Space Management

Toad introduces support for DB2 for LUW compression analysis. To view compression information for tables (9.5 or greater) and 9.7 indexes, right-click the objects, and select Space Management | Compression Analysis.

The report shows current space savings for already compressed objects and estimated space savings for objects currently not compressed.

Right-click objects in the report to perform common maintenance actions.

Data Management

Click a category in the list to view the features and updates for this release:


Export Wizard

You can now execute an export template against a different connection than the one saved with it. For example, this allows you to use the same export template against your test, development, and production databases. To execute the template against a different connection, make sure that you are connected to the new database and that it has focus in the Connection Manager when you execute the template.

Import Wizard

You can now execute an import template against a different connection than the one saved with it. For example, this allows you to use the same import template against your test, development, and production databases. To execute the template against a different connection, make sure that you are connected to the new database and that it has focus in the Connection Manager when you execute the template.

Data Compare

You can now multi-select rows of objects in the Select Objects page and click Map Selected to map multiple objects at a time.

Data Reports

Query Development

Click a category in the list to view the features and updates for this release:


When executing a query in the Editor or Query Builder, you can now pin a result set tab so it is not overwritten by a subsequent query. This is helpful when there are a few lookups that you want to remain active.

Query Builder

You can now right-click an alias and send it to Query Builder.



The debug trace feature collects a complete trace of everything you do when debugging stored procedure so that you can play it back later. You can then replay the trace forwards and backwards to evaluate the execution. The replay does not affect the server; it is only a local replay.

You enable debug trace collection by selecting the Collect debug trace checkbox in the Debugger Start Parameters window that displays when starting a debug session. You can also open this window by clicking (...) on the Debugger toolbar.

Note: This flag is cleared after every execution.

You can also enable and disable trace collection while executing using a new toggle on the Debugger toolbar.

The debug trace collects the following:

The debug trace does not collect the following:

After creating a debug trace, you can browse, delete, and replay traces. You can manually open this window by selecting Debug | Windows | Debug Traces from the menu.

Each item in the list represents saved debug traces that were created for the current connection. If you hover over an item in the list, the full name of the piece of code and the value of any specified parameters when you executed it display. To replay a trace, double-click it in the list or click .

When replaying a trace, you can also step over backwards, step into backwards, and step out of backwards.

You can also generate a coverage report from the trace by clicking .


You can set debug trace options in Tools | Options | Debugger | General

The Collect trace option determines whether the trace should record every line executed while debugging or only the lines where you break or step on. By default all lines are collected.



Resolved Issues and Enhancements

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

Resolved Issues and Enhancements in Toad for DB2 4.7.2


Resolved Issue

Defect ID

Data Grid

The result set can return N-1 record if grid columns have a date based column type.

Object Details (DOV) (DB2 for z/OS) Threads list now can display 6-digits Tokens and CANCEL THREAD command is processed correctly. ST85870


Resolved Issues and Enhancements in Toad for DB2 4.7.1

The following is a list of issues addressed and enhancements implemented in the current release:


Resolved Issue

Defect ID

Space management
The LUW Database Space usage feature is now threaded so you may user other features within Toad while the space information is being obtained. ST70255
In the Indentify Exceptions feature an IndexoutofRange error may occur when connected to an LUW V8 database. ST79663
Data grid
In the data grid, now specific pop-up editors are available by default for DB2 time and timestamp columns.  You no longer need to specify any custom formats for those data types.  To use these new built in editors, ensure you have no Custom - Data Type formatting values specified in Tools | Options | Environment | Grid. ST78044
z/OS remote execution Remote Execution Wizard FTP session has no detailed messaging to assist with problem determination when issues occur. ST78473
When submitting a remote job,  the job submission fails with Runtime error occurred: 42884 (42884: [IBM][DB2] SQL0440N No authorized routine named "QUEST.QC300JFI" of type "" having compatible arguments was found. SQLSTATE=42884). ST78284
Object management
Enhancements have been made to improve performance when determining if objects contain data during extended alters, Object Compare, and Object Migration processes. ST78508
You can now perform a data only migration in the Object Migration feature when you invoke the Object Migration wizard with a z/OS Database or Tablespace by deselecting the DDL options. ST65807
Toad now has an option to always generate import/export commands in extended alter/compare/migrate scripts even when objects do not have data.  The option Always generate data manipulation commands/utilities can be set for extended alter at Tools | Options | Database | DB2 | Advanced Admin or in the Object Compare/Migration wizards. ST68470
In Schema Compare: Unable to print Report, exception baseRow doesn t belong to this XRTable occurred. ST79414
In Schema Compare: There are several issues with views and warning messages in script. ST79500
During certain circumstances, the Toad generated Sync Script is issuing a Drop and Create instead of an Alter . ST79251
In Object Migration/Compare Toad is not identifying all dependents when DB2_COMPATIBILITY_VECTOR=ORA. ST80014
The Explain plan was not returning results when DB2_COMPATIBILITY_VECTOR=ORA. ST79040
To avoid the "Plan not Available" message when attempting to see Access path as part of the SQL tab in Browser - Packages - you can bind with the EXPLAIN(YES) parameter. ST81212
The Extract DDL feature on a z/OS Index now generates key-expressions. ST74617
EXTRACT DDL will not generate DDL for partitioned tablespace when certain items are checked. ST78513
When creating/altering an LUW Table, if a column default of CURRENT USER is specified, validation now occurs to ensure the specified column attributes are valid. ST73043
When creating/altering a DB2 z/OS V9.1 Table, BINARY and VARBINARY are now valid column data types. ST77541
When altering a Table with a foreign key, the generated script did not take into account dependent/referenced objects. ST73141
When a Sequence is altered, executing the generated script may result in an out of range error. ST77772
The generated script created for an extended alter on a Table, may not preserve all permissions on the table.  Now - For non-system objects we don t include in script permissions granted by SYSIBM ; For system objects we script all permissions. ST79691
Toad would generate invalid script syntax for a stored procedure when there are no parameters defined for the procedure. ST79978
A parsing error could lead to incomplete stored procedure - body script generation. ST77997

Resolved Issues and Enhancements in Toad for DB2 4.7

The following is a list of issues addressed and enhancements implemented in Toad for DB2 4.7:


Resolved Issue

Defect ID

Startup issue is resolved by deploying customized settings that disable the opening of the Toad website at startup. ST72768
The Export data to an Excel file icon is no longer disabled for certain Toad DB2 for z/OS licenses. ST70575
Settings migrated from a previous Toad version reside in appropriate version-named directories. ST68623
Installation/Upgrade Updated Installation Guide describes the correct command syntax for deploying Toad to all users via a silent installation. ST72920
A new button on the Create New Connection window allows you to control whether to refresh the list of database and subsystem aliases. Otherwise, Toad caches the Toad DB2 catalog the first time you open this window in your Toad session and continues to read from cache each time you subsequently open the window. This button forces Toad to reread the DB2 catalog to list any new systems that might have been cataloged externally during the caching period. ST77264
Data Grid The INSERT statement resulting from the Copy Rows function now formats the integer values correctly (without quotations). ST75178
Database or Object Explorer
DB Parameters tab now properly displays the Automatic attribute for those database configuration parameters to which it applies. ST76082
Script tab in Object Details now displays FOR BIT DATA for those LONG VARCHAR columns defined with this attribute. ST76045
In Treelist view, you can now uncheck all objects in Tools | Options | Explorer | Objects. ST72978
You can now filter views by schema. ST72961
(DB2 for LUW) You can add State and Bufferpool columns to view a tablespace s status and the name of its associated bufferpool. ST72863
(DB2 for z/OS) The Extents column displays the correct value on the Datasets tab in Object Details for a tablespace. ST72251
On SAP databases, an exception no longer occurs when trying to view privileges assigned to users or assigned on objects. ST70271
System functions generated when distinct types are created now display in the Functions node under System Objects. ST69549
(DB2 for z/OS) The correct creator and owner information displays tables. (Owner information is available for DB2 for z/OS 9.1 or later tables.) ST68942
An exception no longer occurs when you try to open the Explain tab in the Results pane (after moving the pane down to the bottom of the Editor). ST73380
The following object types are not found when using the View Object at Cursor feature:
  • Triggers
  • Users
Import Wizard Date and time data now import correctly, even though the import preview shows the data in incorrect format. ST76313
Migration/Object Compare/Schema Compare
Schema Compare and Object Compare no longer incorrectly flag identical constraints as different. ST73253
The correct RUNSTATS syntax is now generated in Object Compare synchronization and Migration scripts. ST72859
During Object Compare synchronization, the Unload Dataset template provides the proper qualifier for the Unload Dataset name in the target script. ST70732
The Object Compare (not Schema Compare) feature correctly synchronizes a table in a simple tablespace on the target with table in a partitioned tablespace on the source. ST61109
Object management
(DB2 for z/OS) The LOAD phase of an extended alter on tables with decimal types completes successfully. ST75670
(DB2 for LUW) You can now successfully alter a non-partitioned table to make it partitioned. ST75181
(DB2 for LUW) The Drop Table window now includes a Restrict override option. When enabled, this option alters the table to remove the RESTRICT ON DROP attribute before Toad drops the table. ST75097
(DB2 for z/OS) The syntax for dataset template generation in a utility script now matches the syntax used in the template definition. ST74911
(DB2 for z/OS) The Create/Alter Tablespace window accepts the value -1 for the Primary quantity and Secondary quantities fields on the Storage page. ST74866
Extract DDL script creates dependent triggers in timestamp order. ST73907
(DB2 for LUW) During an extended alter, triggers are now created after the LOAD or IMPORT phase. ST73721
You can now perform Extract DDL on system objects. ST73431
(DB2 for LUW) When using temporary tables for extended alters, you can now alter pre-9.7 tables to change an INTEGER column to VARCHAR. ST73015
(DB2 for LUW) Extract DDL and Script tab use correct PAGESIZE syntax in CREATE DATABASE script. ST73004
(DB2 for LUW) Migration, Object Compare synchronization, extended alter, and Extract DDL scripts now place the CREATE UNIQUE INDEX syntax before the ALTER TABLE ADD PRIMARY KEY  syntax. ST72848
The Extract DDL script for a tablespace recreates primary keys for primary and dependent tables when Include drop statements is selected. ST72727
(DB2 for LUW) Toad now supports the NONRECOVERABLE option in the stand-alone Load utility editor. ST72599
Full object-editor template support is available for procedures and functions. ST72045
You can now drag an alias into Query Builder. ST71829
You can now successfully remove any column from a table that contains one or more XML columns. ST70877
Toad now supports changing an XML column to a VARCHAR type in DB2 for LUW 9.5.1 or later. ST70795
On SAP databases, REORG and RUNSTATS execution no longer generate SQL0873 encoding errors. ST70362
(DB2 for z/OS) The script for migrating tables with referential integrity now properly applies the target schema to tables referenced in constraints. ST68675
(DB2 for z/OS) Dataset template variables are now resolving properly during dataset generation. ST68302
Toad now performs a regular ALTER (not an extended alter) when you drop a column default. ST67094
(DB2 for LUW) Toad now supports stand-alone BACKUP, RESTORE, and ROLL FORWARD utilities. ST53988
Query Builder This release addressed the following issues:
  • When you save Query Builder (.tsm) files, the connection password is no longer saved in the file.
  • When you load an existing Query Builder (.tsm) file, Toad no longer uses the connection password to create the connection. If you want to remove the password from the existing file, re-save the file using this Toad release.
Space Management (DB2 for LUW) Space Calculator maintains correct values as move between tablespace entries in a multiple-tablespace list. ST74787
Graphs in Analyze Table Partitions reflect correct row counts in partitions. ST73952
SQL Analysis (DB2 for LUW) Issue with launching SQL Analysis from Toad in a French Windows XP environment is resolved. ST71303


Known Issues

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


Known Issue

Defect ID

General Attempting to launch Toad results in a System.Security.Policy.PolicyException error.

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
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:

  • When the user attempts to launch Toad again, Toad cannot find the license key file.
  • The user might not know where to find the export profiles since they are stored in an unexpected location.

When launching Toad as standard user belonging to an Administrators group, right-click the Toad icon on the Vista desktop, and select Run as administrator.

If a Vista standard user belonging to an Administrators group has launched Toad with the Vista User Access Control security feature enabled, the user cannot open a Spotlight on DB2 for z/OS session within Toad due to insufficient privileges.

When launching Toad as standard user belonging to an Administrators group, right-click the Toad icon on the Vista desktop, and select Run as administrator.



The Toad for DB2 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
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.

Turn off the User Access Control security feature and then uninstall.

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 Toad to avoid losing functionality in some DB2 native tools. CR192879
Data Reports Currently, you cannot create a Label Report in the Toad Data Report wizard. ST42133
Database or Object Explorer Certain DateTime custom formats (such as dd.MM.yyyy HH:mm:ss:ffffff) defined in Tools | Options | Environment | Grid can cause filters based on date or time to generate the message: "Invalid value for the date." ST71682
Performance problems might occur when browsing a large number of database objects.

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.

Debugger 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 9.7 Fixpak 2.

If the DB2 server version is earlier than DB2 for LUW 9.7 Fixpak 2, copy DB2DBGM.JAR from the Toad client installation to the following location on the server:

  • DB2 instance home path/SQLLIB/JAR (Unix or AIX computer)
  • DB2 instance home path\SQLLIB\JAR (Windows computer)


  • If the DB2 server version is DB2 for LUW 9.7 Fixpak 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.
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.

Set a breakpoint after the call to the inner procedure.

Editor 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:

Export Wizard/Quick Export Toad hangs when you use the Export wizard to export data to an Excel instance. This issue occurs when Toad is installed in a Windows 7 environment.

Use the Quick Export method instead. (Right-click the data grid and select Quick Export.)

Binary data types cannot be exported in this release. ST41665
Migration/Object Compare/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. CR140343
Schema Compare synchronization does not create tablespaces on target to synchronize tablespace differences.

To create tablespaces during synchronization, use Object Compare instead.

(DB2 for z/OS only) A comparison of materialized query tables generates an "undefined name" error. ST42913
(DB2 for LUW) The Object Compare synchronization script is not generating the required DROP statements for target functions and procedures that need to be recreated to synchronize them with those on the source. ST53435
(DB2 for z/OS) Toad supports the migration and synchronization of LOB object DDL, but does not support the migration or preservation of LOB data. ST53640
(DB2 for z/OS) During synchronization, Schema Compare places a newly created index-controlled partitioned table in an implicit tablespace, instead of the intended partitioned tablespace. A DB2 error is generated during the creation of the partitioned index.

Use the new Object Compare feature to generate the synchronization script.

(DB2 for z/OS) When synchronizing partitioned indexes, Schema Compare fails to create the partitioned tablespaces in which to place the partitioned tables that the indexes control. ST63613
(DB2 for z/OS) Schema Compare synchronization is creating auxiliary tables in temporary tablespaces, instead of creating them in the proper existing (empty) tablespaces. ST64130
When you are both migrating and preserving target data, Schema Compare and Object Compare generate scripts that list columns for the re-created tables in source-table order, which can be different from the order in which the target data is unloaded. ST64749
Object Management
Extract DDL is not generating the correct script for an index based on a key expression. ST74617
Toad supports scripting, creation, and alteration of nicknames that are based on DRDA-type wrappers only. N/A
(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. ST44753
Project Management When you open Project Manager for the first time, the message "Error loading previous project file..." might occur.

Save the project.

Quest IBM DB2 z/OS Component The current version of the Quest IBM DB2 z/OS component is 4.5.2. (No changes were made to this component for the Toad for DB2 4.7 release.) However, the Quest IBM DB2 z/OS Component Installation Guide erroneously refers to the current component version as 4.7. N/A
SQL Analysis for LUW SQL Analysis does not provide support for Unicode, multi-language, or Microsoft cluster environments. N/A
DB2 truncates dynamic SQL statement text in a DB2 event monitor when deadlock monitoring is enabled in SQL Analysis. The truncated statement text displays in SQL Analysis with three consecutive periods (. . .) at the end.

Clear the Collect Deadlocks option on the Create Collection window in SQL Analysis to disable deadlock monitoring.

Version Control Currently Version Control handles only DB2-standard schema names and file and folder names that are compatible with the underlying Version Control repository. ST42184
You currently cannot check object list definitions into version control. ST42188


Third-Party Known Issues

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


Known Issue

Defect ID

Toad is a .NET application that installs a DB2 for LUW 9.7 client. Due to design changes that IBM introduced in DB2 for LUW 9.7 FixPak 2, .NET applications no longer use db2cli.ini. However, this file contained information you might still want to use when running Toad.

Customize a db2dsdriver.cfg file to define parameters used in the old db2cli.ini file. Perform these steps:

  1. Create an ASCII file named db2dsdriver.cfg in the following directory:

C:\Documents and Settings\All Users\Application Data\IBM\DB2\ToadC47\TOADC47\cfg

  1. Refer to the following IBM document for information about updating this file: doc/doc/c0054555.html

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. CR220327
Connections to Toad are lost, generating SQL0902 errors from the .NET driver. IBM has opened PMR 47384,756,000 to investigate this issue. ST56141
DB2 Management service does not start automatically when Toad for DB2 64-bit is installed. Without this service running, Toad cannot read the DB2 catalog. IBM has opened PMR 63932,756,000 to address this issue.

Reboot the computer, or manually start the DB2 Management service after the Toad installation.

You cannot install DB2 for LUW 8 on the same system that already has Toad for DB2 3.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.)
If you need to install DB2 for LUW 8, uninstall Toad, install DB2 for LUW 8, and then reinstall Toad. For more information, refer to the Release Notes for IBM DB2 9 for Linux, Unix, and Windows.
An SQL0805N error occurs when performing a DML statement on a database.

Refer to the following IBM documentation for an explanation and a solution:

Database Explorer/ Object Explorer Schemas containing empty names are not supported. CR133127
Data Grid (DB2 for LUW) 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. IBM has opened PMR 48511,756,000 to investigate this issue. ST51035
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"

Use the Editor to insert data into tables that include the "Generated always as" option set.

(DB2 for z/OS) 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 error 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. To view details about this issue, see


Perform the following:

  1. Click the Filter Data icon in the data grid.
  2. Select the SQL tab.
  3. Select the Enable custom SQL checkbox.
  4. Enter a query that casts the decimal column as a character data type with 32 characters similar to the following:


Note: When using this workaround, if the number of characters is less than 32, leading zeros display.

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. CR220839
Debugger When compiling with debug, 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
The Debugger is not advancing to the next line under certain circumstances. ST70691
(DB2 for 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 [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.

To avoid the heap memory issue, increase the application heap size on the server.

(DB2 for z/OS) 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. CR207662
(DB2 for LUW) 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. CR213765
Editor (DB2 for LUW) Dropping a nickname does not drop its primary key. This issue (PMR 30432,756,000) was fixed in DB2 9.1 Fixpak 3. ST42503
On SAP databases, RUNSTATS execution generates SQL0873 encoding errors. ST70267
Attempting to create an object in the 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.

You can use either of the following methods as a workaround:

  • Select the schema that you are logged into and fully qualify the schema name for the objects.
  • Issue a SET CURRENT SQLID statement to set the schema on which you want to create objects.
Export Wizard/Quick Export If you use the Export wizard to export result sets to an Excel instance, the Excel spreadsheet shows dates in the wrong format. This issue occurs only when using the Microsoft Office German edition.

Use either method as a workaround:

  • Export the data to an Excel file instead of an instance.
  • Export the data to an Excel instance, and then re-apply the correct format.
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.

For better results, try exporting the data to a CSV file.

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:

2003 PIAs

2007 PIAs

Extract DDL On SAP databases, attempting to extract DDL for a database generates SQL0873N encoding errors. These errors also occur when extracting DDL on objects and their dependencies, which include the database. ST70269
Migration/Object Compare/Schema Compare (DB2 for LUW) You cannot synchronize schemas if the Code Pages on the compared schemas do not match. CR141383
Object Management (DB2 for z/OS) DATE values that define partition-key limits for tables are stored with no single quotations around them in the catalog. Thus, Extract DDL and the Script tab generate scripts that contain incorrectly formatted values for these tables. IBM PMR 64932,756,000 addresses this issue. ST76167
You cannot create a DB2 8 database from a DB2 9 client. Therefore, you cannot use Toad s DB2 LUW Create Database wizard to create a DB2 8 database. N/A
(DB2 for z/OS) 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.

(DB2 for z/OS) 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
(DB2 for z/OS) 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.

(DB2 for LUW) Running queries or performing database administrative tasks in Toad on DB2 databases running on an AIX 5.2 machine can cause the DB2 instance to crash. IBM has addressed this issue with APAR IY79365. ST57962
(DB2 for LUW) db2bp.exe can fail with a Windows error during advanced alters, migrations, Object Compare synchronization, and regular object management. IBM has issued APAR JR33088 to address this issue. ST59491
SQL Analysis for DB2 LUW Databases on DB2 for LUW 8.1 (with FixPaks 1 through 4 applied) generate deadlock events that show a zero lock-wait start time. IBM has addressed this issue with APAR JR18739 in DB2 8.1 FixPak 5. N/A


Upgrade and Compatibility

Upgrade Toad for DB2

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.

Upgrade the Quest IBM DB2 z/OS Component

An upgrade to the Quest IBM DB2 z/OS component was available with the previous version, Toad for DB2 4.5.2. To ensure you have the latest z/OS component upgrade on a DB2 subsystem, do one of the following:

Determine Current Quest IBM DB2 z/OS Component Version

To determine the Quest z/OS component version currently installed on a DB2 subsystem

  1. Open a Toad Editor on the DB2 subsystem connection.
  2. Execute the following query:


Part 1: Update the LOADLIB

To update the LOADLIB

  1. Allocate a sequential file on the mainframe using the following attributes:




  1. Use FTP or an IND$FILE transfer to copy loadlib.xmi (in the Plugins\DB2\zOS folder, located where the Toad for DB2 4.7 client is installed) to the sequential file you set up in step 1. Transfer the file in binary mode.
  2. At a TSO command prompt, type the following, where is the file you allocated in step 1:


  1. At message INMR906A, type the following:


The variable ’’ is either the name of the new PDS/E or the name of the old LOADLIB you are replacing, depending on whether you created a new PDS/E or are using the existing LOADLIB.

  1. If you chose to receive the xmi dataset into a new PDS/E, do the following:
  1. Update the WLM-started tasks and QPDSNAT procedures to reflect the new load library name.

  1. APF-authorize the new LOADLIB.

Part 2: Define the New Functions

To define the new functions

  1. Locate the U4045DDL member in the Plugins\DB2\zOS folder where the Toad for DB2 4.7 client is installed.

  2. Open this file in the Toad Editor.

  3. Change the %COLLID% and %MULTTCB% variables in the script to match those currently used in your system.

  4. Execute the script to define the two new functions.

  5. Grant these functions the same EXECUTE privileges granted to other QUEST functions.


System Requirements

Verify that your system meets the requirements described in the following sections:


Client Requirements

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 Toad for DB2 to avoid losing functionality in some DB2 native tools.


1 GHz minimum

Hard Disk Space 212 MB of disk space required to run Toad.

Allocate the following additional space as needed:

  • If installing the Toad SQL Tuning for DB2 z/OS component, allocate an additional 45 MB.
  • If installing Toad SQL Analysis for DB2 LUW, allocate an additional 47 MB.
  • If installing the Quest SQL Optimizer for DB2 LUW, refer to the Release Notes for that product for disk space requirements.
Memory 512 MB of RAM minimum, 1 GB recommended

Note: The memory required may vary based on the following:

  • Applications that are running on your system when using Toad
  • Size and complexity of the database
  • Amount of database activity
  • Number of concurrent users accessing the database
Supported Operating Systems Any of the following:
  • Windows Server 2003 (32-bit)
  • Windows XP Professional (32-bit)
  • Windows Vista (32-bit)
  • Windows Server 2008 (32-bit)
  • Windows 7 (32-bit or 64-bit)

Note: The Toad SQL Analysis for DB2 LUW client is not supported on Windows Vista, Windows Server 2008, or Windows 7.

.NET Framework .NET Framework

Microsoft .NET Framework 3.5 (Service Pack 1)


  • The .NET Framework Client Profile is not supported.
  • To run Toad, the .NET security policy must be set to unrestricted. See User Privilege Requirements for more information.
Additional Requirements Web Browser

Microsoft Internet Explorer 6.0 or later

Existing DB2 Client Support

Toad installs a DB2 for LUW 9.7 client as part of the installation process. The DB2 9.7 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. To avoid losing functionality in some DB2 native tools, first upgrade to the DB2 8 client; then restart the Toad installation.

Requirements for Windows 7 32-Bit and 64-Bit Environments

Toad provides a 32-bit and a 64-bit Toad DB2 client installer. The 32-bit client installs in any Toad-supported Windows environment. The 64-bit client installs in a Windows 7 64-bit environment only. Additionally, a 32-bit and a 64-bit IBM DB2 client cannot exist on the same computer. Based on this restriction, install the appropriate 32-bit or 64-bit Toad DB2 client if another DB2 client already resides on your 64-bit computer.

Monitor Resolution

SVGA monitor with a minimum resolution of 800x600, 1024x768 recommended


Server Requirements

Toad supports any of these DB2 and operating system versions.

Supported Operating Systems DB2 for z/OS
  • z/OS (V1R6 Base Services [5694-A01] or later)

DB2 for LUW

  • IBM AIX 5.1, 5.2, 5.3, 6.1
  • HP-UX 11i 1.5, 2 (32-bit or 64-bit)
  • Red Hat Enterprise Linux AS release 3 (or later) (32- and 64-bit)
  • Solaris 7, 8, 9, 10 (32-bit or 64-bit)
  • SuSE 7 (or later)
  • Windows 2000, 2003, 2008, XP, Vista, Windows 7
Supported Databases DB2 for LUW
  • IBM DB2 for LUW 8.1.5 or later, 9.1, 9.5 and 9.7

DB2 for z/OS

  • IBM DB2 for z/OS 8 or 9


  • To run RUNSTATS and the native REORG utility on tablespaces and indexes in DB2 for LUW, Toad supports version DB2 for LUW 8.2.2 or later.
  • At this time, Toad SQL Analysis for DB2 LUW does not support DB2 for LUW 9.7.
  • Toad supports DB2 8 for z/OS running in Full Function mode, but does not support DB2 8 running in Compatibility mode.
Supported Operating Systems for Toad for DB2 Agent Toad requires that the Toad for DB2 Agent 5.1 reside on each DB2 for LUW server on which you intend to execute scripts server-side (using the Toad LUW Remote Script Execution component) or to collect SQL using Toad SQL Analysis for DB2 LUW.

The agent supports servers running in any of these operation systems:

  • Microsoft Windows 2000, Windows 2003 (32-bit), Windows XP (32-bit)
  • Sun Solaris 7 or later
  • IBM AIX 4.3 or later
  • SuSE Linux Enterprise Server 8 or 9 for zLinux
  • SuSE Linux Enterprise Server 8 or 9 United Linux for Intel x86
  • SuSE Linux (2.6 Kernel) on AMD64 (x86_64)
  • RedHat Enterprise Linux AS 3.0 or 4.0 zLinux (31-bit)
  • RedHat Enterprise Linux AS 2.1, 3.0, or 4.0 for Intel x86
  • RedHat Enterprise AS 4.0 (2.6 Kernel) on AMD64 (x86)


  • In 64-bit zLinux environments, the Toad for DB2 Agent supports only DB2 for LUW 9.1 or later.
  • To collect SQL in a RedHat or a SuSE Linux 2.6 environment on an x86-64 (AMD64) server, Toad SQL Analysis requires a minimum of DB2 for LUW 8.1 with FixPak 10 applied.
  • Sun Solaris 7 servers must have Sun Solaris 7 patch 106327 applied.
  • RedHat 3.0 servers must have compatibility library compat-libstdc++-7.3-2.96.122.i386.rpm installed. This package is available on RedHat Advanced Server 3.0 installation media.

See the Toad for DB2 LUW Installation Guide for agent requirements and installation instructions.

Hard Disk Space for Toad for DB2 Agent
  • For the Toad LUW Remote Script Execution agent component, 34.9 MB
  • For Toad SQL Analysis services, 35 MB


Virtualization Support

Limited testing has been performed for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the Metaframe Access Suite 5.0 and Citrix Presentation Server Clients 10.2. See "Install Toad on Citrix Systems" in the Toad for DB2 Installation Guide.


User Privilege Requirements

The following are user requirements for installing and running Toad:

User Requirements to Install 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:

User Requirements and Restrictions for Running Toad

The following describes the requirements and restrictions for users who launch and run Toad:

  1. Select Control Panel from the Windows Start menu.
  2. Double-click Administrative Tools.
  3. Double-click Microsoft .NET Framework version Configuration.
  4. Select My Computer, and then select the Runtime Security Policy node.
  5. Select Evaluate Assembly from the list of tasks in the right panel.
  6. In the File field, locate and select Toad.exe.
  7. Click Next, and set the permission to Unrestricted.


LDAP Requirements

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

  1. Open the Command Window for the DB2 client installed with Toad by selecting Start | All Programs | IBM DB2 | <ToadCom, ToadEval, or ToadFree> | Command Line Tools | Command Window.
  2. Type the following command to enable LDAP support:


  1. Type the following command to specify the TCP/IP host name and port number of the LDAP server:

db2set DB2LDAPHOST=hostname[:port]

The port number defaults to 389 (default LDAP port) if you leave the port number blank.

  1. Exit the Command Window.
  2. Launch Toad and open the Connections window.

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 for DB2 in the Toad for DB2 Installation Guide.


Requirement for Capturing Container Information in DB2 for LUW Multi-Partition Databases

Certain Toad functions require that the DFT_MON_BUFPOOL database manager configuration parameter be set to ON to capture information on containers used in DB2 for LUW databases. Additionally, to capture container information across all partitions in a multi-partition database, the snapshot monitor requires that all database partitions be active. To activate all database partitions (and keep them active), execute the DB2 command ACTIVATE DATABASE real_database_name on the server before connecting Toad to the database. See your IBM DB2 for Linux, Unix, and Windows documentation for more information about this command.


Compile and Debug Requirements for Stored SQL Procedures

See the Toad for DB2 Installation Guide for the list of requirements.


Requirements for Full Access to Toad DB2 for z/OS Functionality

To have access to the full range of Toad functionality for managing DB2 for z/OS subsystems, make sure that you have completed the following:

If you currently have the Quest Central for DB2 z/OS component or a pre-4.5.2 Quest IBM DB2 z/OS component installed on your DB2 subsystem, perform an upgrade. Use the instructions found in Upgrade and Compatibility.

If the neither the Quest Central for DB2 z/OS component nor a previous Quest IBM DB2 z/OS component currently exists on your DB2 subsystem, perform a new installation of Quest IBM DB2 z/OS Component available with this release of Toad for DB2. Use the instructions found in the Quest IBM DB2 z/OS Installation Guide (available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation).

Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.


Recommended Indexes to Improve Toad Performance in DB2 for z/OS

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:


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:



Requirements for Object Migration

The following are specifications for using Toad s Object Migration wizard to migrate DB2 objects and their dependencies:


Configuration Requirements for SQL Analysis

SQL Analysis requires the following configuration on the database servers on which you intend to run SQL collections:


Global Operations

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, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations:

Getting Started

Contents of the Release Package

The Toad for DB2 release package contains the following products:

Installation Instructions

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.

  • Do not attempt to manually import catalog entries from the IBM CLP window provided with Toad. If you have any DB2 ODBC entries, db2cfimp will overwrite your existing ODBC system DSN entries and can cause previously configured DB2 ODBC connections to stop working.
  • 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 Toad for DB2 to avoid losing functionality in some DB2 native tools.

Installation Instructions for Additional Components

To install other Toad for DB2 components, refer to the following documentation:

Component Installation Instructions Documentation Location
Quest IBM DB2 z/OS component Quest IBM DB2 z/OS Component Installation Guide From the Start menu, select Program Files | Quest Software | Toad for DB2 | Documentation
Toad for DB2 agent Toad for DB2 LUW Agent Installation Guide From the Start menu, select Program Files | Quest Software | Toad for DB2 | Documentation
Quest SQL Optimizer for DB2 LUW Quest SQL Optimizer for IBM DB2 LUW Installation Guide Download from Quest SupportLink ( or from the Quest product site (
Toad SQL Tuning for DB2 z/OS Toad for DB2 Installation Guide Available on Toad installation DVD
Download from Quest SupportLink ( or from the Quest product site (
Toad SQL Analysis for DB2 LUW


For More Information

Contacting Quest Software

Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656

Refer to our Web site for regional and international office information.

Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to SupportLink, our self-service portal. Visit SupportLink at

From SupportLink, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, policies and procedures. The guide is available at:

Toad Community

Get the latest product information, find helpful resources, and join a discussion with the team and other community members. Join the community at


© 2011 Quest Software, Inc.


This guide contains proprietary information protected by copyright. The software described in this guide 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.

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.

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters


5 Polaris Way

Aliso Viejo, CA 92656


Refer to our web site for regional and international office information.


Quest, Quest Software, the Quest Software logo, Benchmark Factory, Toad, T.O.A.D., Toad World, and vToad are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please see Other trademarks and registered trademarks used in this guide are property of their respective owners.