The following databases/platforms are deprecated in the current release:
Windows server 2012
Windows server 2012 r2
Windows 8.1
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:
|
|
Hard Disk Space |
800 MB to install Toad Note: The disk space required may vary based on the edition of Toad selected for installation. |
|
Operating System |
Windows Server® 2016 Windows Server® 2019 Windows Server® 2022 Windows® 10 Windows® 11 |
| .NET Framework |
Microsoft® .NET Framework 4.7.2 |
| 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 9.7.6 through 11.5.9. 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.9. |
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, 10.5.0.5, 11.1, 11.5, 11.5.9 IBM DB2 LUW 12.1 – tolerant
IBM DB2 for z/OS 11, 12, 13 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 10 and Windows Server 2012 require the following Fix Pack in order to ensure registration of DLLs in Global Assembly Cache:
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. |
| 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 |
Only Windows 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—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:
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:
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:
The following is a list of issues addressed and enhancements implemented in this release of Toad for IBM DB2:
Resolved issues in 8.0
| Feature | Resolved Issue | Defect ID |
|---|---|---|
| Profiling option | The error System.InvalidCastException: Specified cast is not valid occurs when using the profiling option with a SELECT query. |
TDB-4488 |
| SQL script | The error SQL0556N An attempt to revoke a privilege from EJS was denied because EJS does not hold this privilege occurs when users execute the Revoke All Privileges SQL script to revoke all permissions for a specific user in an LUW database. |
TDB-4154 |
| Extract DDL | When performing an Extract DDL operation for the Z/OS database with the Include Privileges option specified, users cannot view the grants for roles returned in the DDL script. This issue also occurs when users select the "Generate SQL" or "Create Script" options. | TDB-4146 |
| DDL for triggers | Users are unable to generate the DDL for triggers using the right-click option, the Script tab in the Properties view, or the Compare Object feature. | TDB-4142/TDB-3994 |
| Multiple features |
Users are facing the following issues after connecting to the DB2 database:
|
TDB-4131 |
| Stored procedure | Toad for DB2 fails to display the properties of a stored procedure when users press the F4 key in the Editor where the stored procedure name is written. | TDB-4119 |
| Review comparison report | Toad for DB2 cannot generate scripts based on the filters applied when executing queries on the Review Comparison Report page. | TDB-4118/TDB-4141 |
| Application tab | The Application tab is not visible in Toad for DB2 version 7.4. | TDB-4112 |
| Restrictive option | Toad for DB2 is generating a script with the restrictive option for a database that is configured as non-restrictive. | TDB-4108 |
| Manage By | Toad for DB2 is displaying incorrect information for Manage By field in Tablespace view details window. | TDB-4030 |
| Create Database scripts | The Create Database scripts for an LUW database, which fetch the storage groups for the creation or an already created database, are not retrieving the assigned database path. | TDB-4012 |
| EditSchemaPrivileges | When connected to LUW version 11.5, the script generated for EditSchemaPrivileges incorrectly includes load-related scripts, resulting in errors during execution. Additionally, when attempting to create a user and assign a schema with all available privileges, the script fails to generate properly. | TDB-4010 |
| Database Explorer | When users try to connect to a new DB2 LUW database connection, the Database Explorer does not open automatically in Toad for DB2 version 7.4. | TDB-4008 |
| Expression-based index | When users create an expression-based index and compares the same object using Compare Object , the expression-based index does not appear in the script. As a result, users are unable to perform object comparisons with accurate results and copying the index to the target object. | TDB-3995 |
| Collate Using | The Collate Using option in the Script tab of the database is not visible in the Toad for DB2 7.2 application. | TDB-3985 |
| Execute Explain Plan | Toad for DB2 is displaying the System.InvalidCastException error when users execute the Execute Explain Plan SQL script to generate the Explain Plan for a set of tables, indexes, or functions. |
TDB-3982/TDB-3983 |
| Alter Database | Application does not display any fields/options on the Alter Database screen under the Storage Path option. | TDB-3965 |
| CREATETAB grant | Toad for DB2 displays a duplicate entry of the CREATETAB grant in the Role tab when generating the Grant script for the Role functionality. | TDB-3963 |
| Data grid | When click on the Save As button in data grid a popup window freezes. | TDB-3961 |
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 |
| 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:
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:
|
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 |
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
