Chat now with support
Chat with Support

Toad for DB2 7.4 - Release Notes

Toad for IBM DB2 7.4

Toad for IBM DB2 7.4

Release Notes

Friday, February 11, 2022

Contents

About Toad for IBM DB2

With Toad, developers and database administrators can use a familiar, proven tool to manage databases. Toad empowers developers and administrators, of varying skill levels, to rapidly create and execute queries, automate database object management, and develop SQL more efficiently.

Toad also provides utilities to compare, extract and search for objects, manage projects, import/export data and administer the database, while increasing your productivity and delivering access to an active user community.

System Requirements

Client Requirements

Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements:

Requirement Details

Platform

2 GHz processor (recommended minimum)

Memory

8 GB of RAM minimum, 16 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

Hard Disk Space

800 MB to install Toad

162 MB to run Toad

Note: The disk space required may vary based on the edition of Toad selected for installation.

Operating System

Windows Server® 2012

Windows Server® 2012 R2

Windows Server® 2016

Windows Server® 2019

Windows® 8.1 (32-bit or 64-bit)

Windows® 10

Deprecated Version of Windows

Toad for DB2 customer support will not be available for the following operating systems as Microsoft has stopped providing support for these platforms.

  • Microsoft Windows 8 (64-bit)
  • Microsoft Windows Server 2008 R2 (64-bit)
.NET Framework

Microsoft® .NET Framework 4.7.1

Database Client

When connecting to a DB2 database/subsystem, ensure that you have a DB2 Client or IBM Data Server Driver installed. Toad supports DB2 Client versions 10.5 through 11.5.

Toad has been tested with the following versions of the DB2 Client: 10.5.0, 10.5.2, 10.5.3, 11.1.0, and 11.5.

Additional Requirements

Web Browser

Microsoft® Internet Explorer® 11 or later

Screen

Recommended maximum DPI settings for Toad are 125%. It is possible to use Toad up to 200% but some dialog windows will not be completely usable anymore.

Maximum tested resolution for Toad is 1920 x 1080 px.

Server Requirements

Before installing Toad, ensure that your server meets the following minimum hardware and software requirements:

Requirement Details

Database Server

IBM DB2 for LUW 10.5.x, 11.1.x, 11.5.x

IBM DB2 for z/OS 11, 12

Note: Toad may support IBM DB2 Express and SWE in addition to listed above servers but note that no testing was performed on it.

Note: Windows 8.1, 10 and Windows Server 2012 require the following Fix Pack in order to ensure registration of DLLs in Global Assembly Cache:

IBM DB2 LUW 10.5 Fix Pack 4
IBM DB2 LUW 11.1 Fix Pack 6
IBM DB2 LUW 11.5 Fix Pack 0

Note: To use Access 2016 64-bit to connect to an Access database in Toad, the Microsoft Access Database Engine is required and might not be included in the Access installation. The engine must match the architecture (bitness) of Toad.

Deprecated Version of Database Server
  • IBM DB2 LUW 10.1 Fix Pack 4
  • IBM DB2 LUW 9.7 Fix Pack 1

Virtualization Support

Requirement Details
Application Virtualization

When deploying Toad in a virtualization environment, for best results ensure the system accurately reflects the applicable client hardware and software requirements listed in this document.

Toad has been developed using Microsoft guidelines (see Remote Desktop Services programming guidelines) and can be deployed and operated in virtualization environments such as Citrix XenApp, Microsoft App-V, and VirtualBox.

Install Toad on Citrix® Systems

User Requirements

User Requirements to Install Toad

Only Windows Administrators and Power Users can install Toad.

Note: The following exceptions exist for Power Users:

  • A Power User can install Toad as long as this user belongs to the DB2ADMNS or DBUSERS group.

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—on the computer.

If a Power User installs Toad, a Restricted User cannot do the following:

  • Associate file extensions.
  • View the Toad shortcut icon on the desktop or the Toad menu options in the Windows Start menu. As a workaround, Restricted Users can create a shortcut to Toad from the install directory and place the shortcut on their desktop.

User Requirements and Restrictions for Running Toad

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

  • A Windows Power User or Restricted User must belong to the DB2ADMNS or DB2USERS group. To add the user to one of these groups, select Start | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Groups | DB2ADMNS or DB2USERS.
  • A Windows Power User or Restricted User does not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, these users can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries to Toad.
  • To take full advantage of Toad for DB2 LUW functionality, the user ID specified in the Toad connection profile for each DB2 for LUW database connection requires the authorizations listed in the following document:

    ToadDB2LUWAuthorizations.xls

  • As a minimum requirement to manage a DB2 for z/OS subsystem in Toad, the user ID defined in the Toad connection profile for the subsystem must either have SYSADM privileges or SELECT privileges on the DB2 catalog tables. For a complete list of authorizations (and corresponding GRANT statements) a user requires to take full advantage of Toad for DB2 z/OS functionality, refer to the following document: ToadDB2zOSAuthorizations.doc
  • To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security features.
  • For information about defining a RACF, Unix, or Linux group as a Toad Security role, see the About Setting Up Toad Security topic in the Toad online help. This topic explains how to add the Toad Security icons to your toolbar and how to define Toad Security roles that apply to your current connection. (The ability to define RACF, Unix, and Linux groups as Toad Security roles works with DB2 for LUW 9 or later databases and DB2 for z/OS 8 or later subsystems.)

Resolved Issues and Enhancements

Resolved Issues

The following is a list of issues addressed in this release of Toad for IBM DB2:

Resolved Issues in 7.4

 

Feature Resolved Issues Defect ID
Alter Database Script Application is not generating the script correctly for the Alter Database operation under the SQL Script tab. TDB-3981
Project Rename Project rename functionality under the Project Manager option is not working for a newly created project. TDB-3978
Publish Project Toad for DB2 displays an error while publishing a newly created project. TDB-3977

Known Issues

The following is a list of issues known to exist at the time of this release.

Feature Description Support Case/Defect ID
General The Explain Plan screen is not displaying the results, when an SQL Query is executed in the Editor tab. TDB-4003
General Toad for DB2 displays an error when users try to create a new Like table from the Object Explorer pane. TDB-4001
General Application is not generating the script correctly for the Alter Database operation under the SQL Script tab. TDB-4000
General Toad for DB2 is not displaying any matching files when searched using the Find and Replace option. TDB-3999
General Toad for DB2 displays an error when users try to create a new table from the Object Explorer pane. TDB-3997
General Toad for DB2 displays an error when users try to import data using the Excel Instance option. TDB-3980
SQL Script Generation Toad for DB2 is not generating the script correctly while creating database constraints to retrieve data. TDB-3979
General Toad for DB2 displays an error even after entering the valid server details to test the connection using the FTP connection functionality. Also, system displays an inappropriate error message. TDB-3976
Toad Intelligence Central Application displays an error while registering a new user in Toad Intelligence Central. TDB-3975
General Toad for DB2 is not generating the application log while performing any operation. TDB-3973
Script for Alter Table Upon making any modifications in the existing columns of a table, application generates the updated SQL script in the comment form due to which users are not able to alter the tables. TDB-3971
General Application displays an error while opening the Spotlight application as an integrated Quest tool. TDB-3969
General Toad is not displaying the execution cancellation alert message every time users cancel/stop the execution. TDB-3968
Export Connection Since the Save button used while exporting connections is disabled, users are not able to export connections using the Connection Manager option. TDB-3967
General Toad displays an error while exporting a MS Excel linked query of an output. TDB-3966
Alter Database Window Application does not display any fields/options on the Alter Database screen under the Storage Path option. TDB-3965
Object Details When a DB2 object is created, DB2 implicitly creates authority for the user who created that object. In the system catalog tables those are shown as SYSIBM as the Grantor. When migration\compare\extended alter scripts are generated Toad does not generate GRANT statements in those scripts for authorizations granted by SYSIBM because those are granted implicit authorizations that have been created by DB2. TDB-870
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 10.1 fix pack 2.

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

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

Notes:

If the DB2 server version is DB2 for 10.1 fix pack 2, use the JAR file supplied with your DB2 version. If replacing the JAR file as described in the workaround, make sure you back up the original JAR file on the server before replacing it with the one from the Toad client installation.

N/A
Export Wizard/ One Click Export Avoid using Excel for exporting if your data has numeric values that require a high precision because Excel's precision is limited to 15 digits. If you export numbers with more precision, the values are rounded. If you export boundary numbers (max, min), rounded numbers will exceed the data type limit. N/A
Installation Network and LAN installations are currently not supported. N/A
 

Toad uses hardcoded values instead of some variables such as %USERNAME% in several path names and therefore App-V environment is not supported.

For installation adhere to Windows Installer Best Practices, see here.

TDB-1009/ 2297051-1
Space Management

If running Toad for IBM DB2 6.0 or earlier in a pureScale environment and the QUEST.SH_SNAPSHOT procedure had been installed, the procedure will have to be redefined. Please, follow these steps:

  1. Drop procedure QUEST.SH_SNAPSHOT
  2. Right click a tablespace
  3. Select Space Management | View Space History
  4. Click Yes when prompted to run the install script for the procedure
  5. Execute the script
N/A
SQL Editor Toad does not handle DBMS_OUTPUT in the SQL Editor. ST90710
z/OS Utilities When using Utilities as the data preservation method and the length of a column tied to columns from other tables via RI is reduced. When executing the alter script the load fails with a DSNU334I INPUT FIELD INVALID error pointing to the altered column. The load cards show the old length for the altered column which appears to be the problem. ST44753

 

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating