Toad® for IBM DB2

Beta Version 4.7.0.558

Beta Release Notes

September 2, 2010


Contents

Welcome to
Toad for DB2

New in this Release

Resolved Issues and Enhancements

Known Issues

Third-Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information


Welcome to Toad for DB2

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

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

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


New in This Release

The latest Toad for DB2 4.7 Beta drop includes fixes and new enhancements.  Additional new atures, enhancements and fixes will be introduced throughout the Beta cycle.

 

Features and Updates in Toad for DB2 4.7

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

 

 


Prerequisites and Installation

Toad ships and installs IBM DB2 for LUW Client 9.7 as the DB2 client. The new default location for the DB2 client is C:\Program Files\Toad for DB2 4.7\SQLLIB.

 

 


General Toad Environment

 

 

 

 

 

 

 

 


Database Administration

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

 

Object Management - General

 

 

Object Management - DB2 for LUW

Toad continues to introduce support port for important DB2 for LUW 9.7 features.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Database Level Backup:

 

 

Tablespace level backup:

 

 

 

 

 

 

 

 

 

 

The results of resetting charts removes all data points in all charts as shown below.

 

 

 

 

 

Object Management - DB2 for z/OS

Toad continues to introduce new features and support for important DB2 for z/OS v9.1 features. 

 

In the Recovery dialog you can easily view and select your recovery dataset.

 

Now when defining templates on a DB2 v9.1 subsystem the new Template 'switching' values can be specified as shown below.

 

The 'New template' value is the name of a defined template whose definition will be used if the Limit/Limit unit values are exceeded during utility execution.  Toad will generate the appropriate Template statements in scripts to support this new v9.1 feature.

 

 

 

 

 

 

 

 


Space Management

 


Data Management

 

Custom options that control those formats:

 

 


Query Development

Query Builder

Editor

 

 

 

 

 

You can now expand schemas to see other items that are associated with them from code completion. You can view these items by clicking the + sign or by pressing CTRL+RIGHT.

You can use the new toolbar at the bottom of the code completion list to change the following code completion options (in order): Apply filter to editor, Include system objects, Merge secondary items.

 

 


Under Construction   

The following features are under construction in this beta drop and should be avoided:

 

 

Resolved Issues and Enhancements

Resolved Issues and Enhancements in Toad for DB2 4.7 Beta

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

Feature

Resolved Issue

Defect/Enhancement ID

Drop
Table Editor
Toad was generating an extended alter when a Table Column's default value was removed. Toad now generates a native table alter - alter column drop default. CR67094 4.7.0.353
Object Migration/Compare
When an Object Migration/Compare wizard completes it generates two scripts. One script to be run against the source (for example to extract data) and the second script to execute on the target (for example to create target objects and load data).  The Wizards used to set context to the target script upon completion.  Now context will be set to the source script as that script is required to be executed first. CR72087 4.7.0.353
z/OS Tablespace Alter z/OS Tablespace Editor: Request to allow a user to alter a segmented tablespace to a partitioned or universal tablespace. Toad now supports such alters.
 
CR68049 4.7.0.353
Data Grid  Request to have separate formats for Date, Time and Timestamp columns in the grid. CR62009 4.7.0.353 
Object Search  Request to display column datatypes and lengths in the Object Search Results CR67389 4.7.0.353  
DB2 LUW Database Monitor Tab  Request to be able to reset the charts - to remove all points and start over CR73037 4.7.0.353   
DB2 LUW Tablespaces List Request to have the Bufferpool name displayed in the list of Tablespaces CR72863 4.7.0.353
Object Compare Request to have a visual difference viewer in the Object Compare wizard CR67395
CR71376
4.7.0.353
DDL Generation In the 4.7  Beta - Alias DDL is being omitted from scripts generated for Extract DDL, Extended Alters, Compares and Migrations. CR74019 4.7.0.395
z/OS Tablespace Extended Alter The generated script for an extended alter for a z/OS partitioned table does not include the necessary drop statements. CR74082 4.7.0.395
Object Compare When comparing objects across different database versions, some new attributes, only available in the later version of DB2 could cause differences to be flagged.  Work will continue throughout the beta cycle to correct those issues. N/A 4.7.0.395
Dependencies Toad now displays the creator of synonyms in the dependency tree. CR67870 4.7.0.429
Explain Plan Toad has updated the DDL for explain plan tables changes for DB2 LUW v9.7 and DB2 z/OS v9.1. CR69949
CR69955
4.7.0.429
Privileges Toad now includes support (Grant/Revoke) for the DB2 z/OS DEBUGSESSION privilege. CR70892 4.7.0.429
Table Properties OBID is now displayed on z/OS Table properties. CR69294 4.7.0.429
Function/Procedure Templates Toad improved the Template feature for Function and Procedure database objects.  Now all properties of those objects are templatable. CR72045 4.7.0.450
Extract DDL - Table Extract DDL of Table with LOB produces a script with incorrect syntax CR76039 4.7.0.558
Stored Procedures Parsing Several parsing issues may arise when parsing the body of Stored Procedures. These include miss-parsing of TRUNCATE TABLE statements and miss-parsing of Labels within procedure bodies. CR76165 4.7.0.558

 


Known Issues

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

Feature

Known Issue

Defect ID

Database Level Compare We have disabled the Compare/Migration feature at the DB2 LUW Database level and plan to re-introduce that with improved performance in a subsequent future release. N/A
General 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.

CR166752
Case 408845
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.

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

N/A
The Toad db2cli.ini file defines that Toad connects to the catalog node on multi-partitioned DB2 for LUW databases. To change the node to which Toad connects, use the following steps to edit the file:
  1. Locate db2cli.ini in \Documents and Settings\All Users\Application Data\IBM\DB2\ToadC46.
  2. Open the file and do one of the following.
     

    Edit the following line with the correct node specification:

    [COMMON]
    ConnectNode = SQL_CONN_CATALOG_NODE
     

    or

    Comment out the line by placing a semi-colon at the beginning of the line:

    [COMMON]
    ;ConnectNode = SQL_CONN_CATALOG_NODE

53860
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.

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

60819
Installation/

Upgrade/Uninstall

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.

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

52914
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
Case 462823
Connections If you migrate settings from a previous version, the following options in Tools | Options Database | DB2 might point to paths from the previous version instead of the newly installed version:
  • Root folder option under Database Object Editor Templates on the General page
  • Recovery script directory option on the Advanced Administration page
  • Utility File Directory option on the LUW | General Utilities page

If you later delete the previous version's Toad for DB2 directory where these directories reside, you receive a "path not found" error when you attempt to connect to a database. (You can click OK and continue working.)

Workaround:
Select Tools | Options | Database | DB2, and locate each page listed in the previous list. For the given option on the page, navigate to and select the parallel path located in the Toad for DB2 4.6 directory. The following lists the default path for each option:

For Windows 2003 or XP

  • Root folder option: C:\Documents and Settings\username\Application Data\Quest Software\Toad for DB2 4.6\Templates\DOE
  • Recovery script directory option: C:\Documents and Settings\username\Application Data\Quest Software\Toad for DB2 4.6\Recovery Scripts
  • Utility File Directory option: C:\Documents and Settings\username\Application Data\Quest Software\Toad for DB2 4.6\Data\Utility Files

For Windows Vista or 7

  • Root folder option: C:\Users\username\AppData\Roaming\Quest Software\Toad for DB2 4.6\Templates\DOE
  • Recovery script directory option: C:\Users\username\AppData\Roaming\Quest Software\Toad for DB2 4.6\Recovery Scripts
  • Utility File Directory option: C:\Users\username\AppData\Roaming\Quest Software\Toad for DB2 4.6\Data\Utility Files
68623
Data Reports Currently, you cannot create a Label Report in the Toad Data Report wizard. 42133
CR215945
Database or Object Explorer
Performance problems might occur when browsing a large number of database objects.

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

CR220761
CR220757
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.

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

Notes:

  • 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.
N/A
Currently, the debugger does not support Unicode schema names. 41770
CR184638
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.

Workaround:
Set a breakpoint after the call to the inner procedure.

69377
Editor
The following object types are not found when using the View Object at Cursor feature:
  • Triggers
  • Users
41627
CR164917
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:

http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.dndp.doc/htm/frlrfIBMDataDB2DB2CommandClassCommandTextTopic.htm

CR224375
Case 552946
Export Wizard/One Click Export Binary data types cannot be exported in this release. 41665
CR170430

Case 419715

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.

Workaround:
To create tablespaces during synchronization, use Object Compare instead.

41983
CR210132
Case 491910
(DB2 for z/OS only) A comparison of materialized query tables generates an "undefined name" error. 42913
CR228511
(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. 53435
(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. 53640
(DB2 for z/OS) During synchronization, Schema Compare fails to create the partitioned tablespace in which to place an index-controlled partitioned table.

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

61109
(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.

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

61112
(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. 63613
(DB2 for z/OS) Schema Compare synchronization is creating auxiliary tables in temporary tablespaces, instead of creating them in the proper existing (empty) tablespaces. 64130
When 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. 64749
During Object Compare synchronization, the Unload Dataset template incorrectly inserts the source subsystem ID in the Unload Dataset name in the target script. 70732
Object Management
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. 44753
Project Management When you open Project Manager for the first time, the message "Error loading previous project file..." might occur.

Workaround:
Save the project.

70794
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.6 release or the 4.7 beta.) However, the Quest IBM DB2 z/OS Component Installation Guide erroneously refers to the current component version as 4.6. N/A
LUW Index DDL There is a bug in the 4.7 beta where Toad will generate an invalid "IN" clause in index DDL. CR74076
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.

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

N/A
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. 42184
CR217475
You currently cannot check object list definitions into version control. 42188
CR217524

 


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.

Feature

Known Issue

Defect ID

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. CR220327
Case 537948
Connections to Toad are lost, generating SQL0902 errors from the .NET driver. IBM has opened PMR 47384,756,000 to investigate this issue. 56141
Case 669950
Installation/
Upgrade
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.)
Workaround:
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.
CR187913
An SQL0805N error occurs when performing a DML statement on a database.

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

http://www-1.ibm.com/support/docview.wss?rs=71&context=SSEPGG&dc=DB520&q1=DML&uid=swg21208123&loc=en_US&cs=utf-8&lang=en

CR220160
Database Explorer/ Object Explorer Schemas containing empty names are not supported. CR133127
CR133139
On SAP databases, an exception occurs when trying to access the Grants tab for a given object or to access an object tab for a given user or group to view assigned privileges. 70271, 70270
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. 51035
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:
Use the Editor to insert data into tables that include the "Generated always as" option set.

CR142504
(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 http://msdn2.microsoft.com/en-us/library/xtba3z33(vs.71).aspx.

 

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

SELECT COLUMN, CAST ("DECIMALCOLUMN" AS CHAR (32)) AS DECIMAL FROM DB2ADMIN.TESTDECIMAL

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

CR186529,
CR186535
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. 70691
(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.

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

CR188846
(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
Case 517909,
        529227
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. 42503
CR223155
On SAP databases, RUNSTATS execution generates SQL0873 encoding errors. 70267
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.

Workaround:
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.
CR183855
Export Wizard/One Click 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.

Workaround:
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.
68732
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.

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

70817
Case 785690
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
http://www.microsoft.com/downloads/details.aspx?FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&DisplayLang=en

2007 PIAs
http://www.microsoft.com/downloads/details.aspx?FamilyID=59DAEBAA-BED4-4282-A28CB864D8BFA513&displaylang=en

CR138239
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. 70269
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
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.

N/A
(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.

N/A
(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. 57962
(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. 59491
Space Management (DB2 for LUW) 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
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
Stand-alone Utilities (DB2 for LUW) On SAP databases, SQL0873N encoding errors occur when running Reorg Tables, Reorg Indexes, or Runstats. 70362

 


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.

 

This Toad for DB2 beta is a separate product that will not upgrade any commercial Toad for DB2 products that you may have installed on your machine.

This beta can be installed on a machine that has other versions of Toad DB2 installed.  You should install this beta into a separate, new directory.

 

For Toad DB2 on z/OS users, this beta will work with the Quest IBM DB2 z/OS Components that you may have installed with Toad for DB2 v4.6, so there is no reason to install those z/OS Components again, if they already exist. 

 


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.

Platform

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)

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)

Notes:

  • 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.

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- and 64-bit)
  • Red Hat Enterprise Linux AS release 3 and 4 (32- and 64-bit)
  • Solaris 7, 8, 9, 10 (32- and 64-bit)
  • SuSE 7, 8, 9
  • Windows 2000, 2003, 2008, XP, Vista, Windows 7
Supported Databases DB2 for LUW
  • IBM DB2 for LUW 8.1.5 or later
  • IBM DB2 for LUW 9.1 or later

DB2 for z/OS

  • IBM DB2 for z/OS 8 and 9

Notes:

  • 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_24)
  • 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)

Notes:

  • 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 CDs.

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

 


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.

 


Citrix Requirements

Toad has been tested 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.

 


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:

db2set DB2_ENABLE_LDAP=YES

  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:

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

 


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, Far-East Asia, Japan.

However, 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.

Caution:
  • 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 (http://support.quest.com/) or from the Quest product site (http://www.quest.com)
Toad SQL Tuning for DB2 z/OS Toad for DB2 Installation Guide Available on Toad installation DVD
or
Download from Quest SupportLink (http://support.quest.com/) or from the Quest product site (http://www.quest.com)
Toad SQL Analysis for DB2 LUW

 


For More Information

Contacting Quest Software

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

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 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, policies and procedures. The guide is available at: http://support.quest.com.

 

This guide is available in English only.

 

 


© 2010 Quest Software, Inc.
ALL RIGHTS RESERVED.

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
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

www.quest.com

Email: legal@quest.com

Refer to our web site (www.quest.com) for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Toad, T.O.A.D., and Toad World 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 http://www.quest.com/legal/trademark-information.aspx . Other trademarks and registered trademarks are property of their respective owners.