
Beta Version 4.0.0.688
Beta Release Notes
June 24 2008
| Third Party Known Issues | ||||
| System Requirements |
Toad for DB2 is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to DB2 expertise.
Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.
All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.
Areas to focus on in this beta drop:
We have introduced the beta of the new optional Quest SQL Optimizer for DB2
LUW 3.0 Beta that is integrated with Toad.
If you have this new component installed you can launch it from a Toad DB2 SQL
Editor session to perform advanced statement tuning.


Note that the Quest SQL Optimizer for DB2 LUW 3.0 Beta is available for use during this beta and will available in the Toad for DB2 LUW Xpert edition upon Toad DB2 4.0 General Availability. To download the installation for this component see the Quest SQL Optimizer for DB2 LUW page.
![]()
Under Construction
Some features that we are updating are still being
developed and tested. See Known Issues for more
information.
Thank you for your feedback!
Migration Wizard
The Migration Wizard remains under development.
Migration Wizard Known issues:
Toad does not include some referenced/dependent objects (CR51027).
Toad throws an exception in Migration if the user defines a schema
transformation rule, then attempts to define any other transformation rule. A
work around would be to define your schema transformation last (CR51222).
If you find any other issues please report those to the beta board. Thank you for your patience.
From Previous drops:
We have introduced the beta of the new optional Toad SQL Tuning for DB2 z/OS
component that is integrated with Toad.
If you have this new component installed you can launch it from a Toad DB2 SQL
Editor session to perform advanced statement tuning.


Note that the Toad SQL Tuning for DB2 z/OS component is available for use during this beta and will available in the Toad for DB2 z/OS Xpert edition upon Toad DB2 4.0 General Availability. To download the installation for this component see the Toad SQL Tuning for DB2 z/OS page.
DB2 on Linux, UNIX and Windows and DB2 on z/OS
Run script from cursor
We have introduced a new SQL Editor Toolbar button "Execute From Cursor"
.
This button will execute the statements in the script from the cursor
position through the end of the script.
This buttons is helpful when you need to restart a script from a certain
location. We have decided to not show this button by default to reduce the
clutter of our Toolbars. You may add this button as shown below:

Migration Wizard Changes
To improve the flow of the wizard, in this drop we moved the options to migrate referenced objects and dependent objects from the Filter page onto the Customize Migration page. We also reorganized the Customize Migration page and have grouped options into more meaningful sections.

Performance Enhancements
In this drop we have made performance improvements in the following areas:
- Database browser
- We made changes to how we fetch and format data that
appears on both the left-hand side and the right-hand side of the browser
- Alter scripts
- We made changes in the SQL we execute and in our processing
to reduce the time it takes to generate scripts for when altering objects
(for native alter statements as well as for Advanced Alters - which require a
drop and re-create of objects)
- Migration Wizard
- We made changes in the Migration wizard in the SQL we
execute and in our processing to reduce the time it takes to generate dependency
lists and migration scripts
- Schema Compare
- We made changes in the Schema Compare feature in the SQL we
execute and in our processing to reduce the time it takes to identify
differences and generate sync scripts
We welcome feedback on these features and are anxious to hear about the performance of these features at your site.
For DB2 on z/OS subsystems:
Note that we are still in the process of testing these changes and reviewing our
list of recommended indexes to ensure they are leveraged with our recent
changes. For the time being, please continue to use the list of
recommended DB2 z/OS indexes below.
DB2 on z/OS Command Snippets
We now have added DB2 z/OS command snippets to allow you to easily generate and execute those commands within an editor.

The execution of DB2 z/OS commands require the z/OS Components to be installed -
please refer to that section in the release notes for additional information
here.
DB2 on Linux, UNIX and Windows
Space Calculator Feature
The Space Calculator feature lets you test hypothetical object additions, deletions, or object-size changes to determine their impact on space usage in a DB2 for LUW tablespace. Space Calculator also provides options to run maintenance utilities on objects or to generate scripts that put into effect your space-usage scenarios.
Access Space Calculator from the Database Explorer or Object Explorer or from an object list.
To access Space Calculator from the Database Explorer or Object Explorer
In the Database Explorer or Object Explorer, select the Tablespaces, Tables, or Indexes tab.
Select the objects that you want to involve in making hypothetical space adjustments.
Right-click and select Space Management | Calculate Space.
To access the report from an object list
In the Database Explorer or Object Explorer, select the Object Lists tab.
Select the object list.
Within the object list, select either the tablespaces, the tables, or the indexes you want to involve in making hypothetical adjustments.
Right-click and select Tablespace (or Table or Index) | Space Management | Calculate Space.
The Space Calculator window opens, showing a list of the tablespaces you selected or the tablespaces to which the objects you selected belong.

The Space Calculator window initially shows space-related information (gathered from the system catalog) for each tablespace you selected, for each container that makes up a given tablespace, and for each table or index in the tablespace. As you hypothetically adjust space requirements at the container or object level, Space Calculator keeps track of how your changes affect the tablespace.

You can group by any column by dragging the column name to the area above the list as shown below.

You can hypothetically adjust space values by entering the new values in the
grid or by clicking the
button:

When you click the
button
you can enter space information and then click 'Apply':

The graphs are updated to reflect your hypothetical space changes:

You can use the buttons at the bottom of the lower left area to remove hypothetical objects, show additional columns, reset the selected objects or reload object definitions from the catalog:

Additionally, right-click menus enable you to perform
maintenance procedures

Support for DB2 V9.5 Array Type
You can now create, create like, alter and drop DB2 LUW V9.5 Array types. You can invoke these actions and others from the 'Distinct Type' tab on the database browser:

To specify an 'Array' type, select the 'Array' value in the 'Type' drop-down list in the object editor dialog. Specify the array length in the properties section of this dialog:


DB2 on Linux, UNIX and Windows and z/OS Performance fixes
For this drop we changed how we format the results from catalog queries when populating object lists in the Database Browser. You should see that the objects listed in the Database Browser (like Tables, Tablespaces, Indexes, etc.) are displayed faster now compared to previous 4.0 beta drops.
DB2 on Linux, UNIX and Windows
Analyze Table Partitions Feature
The Table Partition Analysis tool helps you determine how best to redistribute the data among the current data partitions in a table. Using this tool, you set up data distribution scenarios. Table Partition Analysis then calculates the number of table rows that DB2 would store in each partition for the current scenario and shows a graphical depiction of this data distribution. Once you determine the best scenario for redistributing the data, you can have Table Partition Analysis generate the script that alters the data partitions using the scenario values and redistributes the table data accordingly.
To invoke this new feature right click on a data partitioned table and select Space Management...Analyze Table Partitions:

Upon entry to this feature you can click on the 'Refresh Graph' button to display a graphical representation of the table's data distribution:

You may edit the partition ranges and then click on the 'Refresh Graph' button to see the new data distribution. You can then click on the 'Show Script' button to generate an 'Alter' script to implement your changes:

Space Usage Feature
For LUW tablespaces there now is a 'Space Usage' tab on the right hand side in the database browser.
Use this tab to easily obtain and view space information for the tablespace, its containers, and the tables and indexes in the space.



From Previous drops:
DB2 on Linux, UNIX and Windows
New multiple object Table and Tablespace editors
Now you can conveniently alter some common LUW Table and Tablespace properties using one editor. As of this Beta release when you multi-select these objects and choose 'Alter' a new multiple object editor will be launched.



New option to rebuild Indexes, Triggers and Views
Now you can easily recreate selected LUW Indexes, Triggers, and Views with a single right-click 'Rebuild' action.



Common DB2 Changes (for both LUW and z/OS)
Previewed extended object alter scripts are now sent to the SQL Editor for execution
When performing an alter that requires a drop and recreate of the DB2 object the resulting script is no longer able to be executed from the object editor when the 'Preview script' option is in effect. With this option set the script may only be sent to the SQL Editor for execution. The SQL Editor provides greater flexibility and ease of execution.


DB2 on Linux, UNIX and Windows
Stored Procedure enhancements
Now you can easily Create, Create Like and Alter LUW Stored Procedures. Those actions are available via a right-click menu and invoke object editors to make creating and altering Stored Procedures an easy task.


Edit Catalog Statistics
Now you can easily update catalog statistics for Tables and indexes. A new right-click menu item "Edit Catalog Statistics" has been added for LUW Tables.

This new features brings up an editor that allows you to edit table, column
and index statistics.
You can easily save and reload statistics in the editor. This feature
allows you to easily simulate production statistics in a test environment.

New Space Exceptions feature
A new 'Space Exception' Report feature is available from the Tools Menu or via right-click menu Tables - Send To - Exception Report.


Objects from the 'Object Explorer' can also be dragged and dropped onto the
'Space Exception' tab.
The Space Exceptions feature allows you to easily identify objects that need to be reorganized or objects that do not have current statistics in the catalog. You can use the controls at the top of the Space Exceptions tab to easily view and check objects and fix objects with REORG or statistics issues. Correcting these issues will lead to better database performance.

When you click the above 'Reorg' button, the following screen displays and allows you to easily generate scripts.

The criteria used in identifying exceptions and warnings can be viewed and modified using the Tools - Options - Database - DB2 - LUW - Space Exceptions.

New Space Estimator feature
We are introducing a new 'Space Estimator' feature. When you are creating a tablespace, you can use the 'Space Estimator' tab and enter information about the tables or indexes that you plan on defining in the tablespace. The estimated space usage is calculated and displayed. If you are creating a database managed tablespace and already have specified the containers, when you click on the 'Apply' button, the containers are sized to accommodate the anticipated space usage.

When the 'Apply' button is clicked, the Containers tab is shown with container sizes computed.

You can also estimate size using existing table definitions. Just click the '...' button.

The following window will display and allow you to select existing tables to be used in the space usage computation.

New Set Integrity support
Toad has added the ability to quickly generate 'Set Integrity' statements for Tables. Now you can select one or more tables, right-click and select Utilities - Set Integrity.



New Utilities tab
Toad has a new 'Utilities' tab where information about currently executing commands/utilities are displayed.
You can right-click on a utility and select 'Set Utility Impact' to easily modify the utility's priority.



Applications tab enhancements
We now include Dynamic SQL and SQL statement information on the Applications tab.

DB2 on z/OS
DB2 Command support
You can now execute DB2 on z/OS commands within the SQL Editor. (This requires that the Quest z/OS Components are installed for the DB2 z/OS subsystem).

Advanced Alters - Stop/Start tablespace
Advanced alter scripts now generate -STOP and -START tablespace commands (when necessary).
Common DB2 Changes (for both LUW and z/OS)
Constraints
Toad now shows constraints as objects in the Database Explorer and Object Explorer so you can now easily view properties and columns, view dependencies, or maintain constraints.

Objects details on right hand side
Toad has enhanced the Database Explorer right hand side view to show information on objects. When you click on a node group in the tree, a list that can be sorted and arranged is displayed on right hand side view. You can right click on those objects in the list and invoke actions on those

Compare Options save and re-load
Toad now allows you to save and re-load Schema compare options. The options can be modified, saved and re-loaded from the Tools - Options - Schema Compare - panel.

Migration Wizard Changes
The migration wizard now has individual check boxes that can be selected to migrate objects that are referenced by the selected objects as well as dependent objects. (Stay tuned for additional migration wizard enhancements).

Visual Changes
We have renamed several features and regrouped features under different menus to improve the product's organization and to simplify use.
The 'Object Palette' has been renamed to 'Object Explorer'.

The 'Database Browser' has been renamed to 'Database Explorer'.

We have moved the Migration and Compare features
from the Advanced Menu to now be under the Tools Compare Menu:

For this drop we are trying to reduce the number of toolbar buttons. We changed the run script button (F5) to the below highlighted button:

Group Execute
Group execute is now a left docked tab within the SQL Editor.

![]()
Other Features Under construction
Other features are under construction and have not completed testing at the time of this drop. As those features become solid, we will be highlighting and explaining them in subsequent beta drops.
The following is a list of issues addressed and enhancements implemented in this beta release of Toad for DB2.
|
Feature |
Resolved Issue |
Change Request |
| DDL Generation | ||
| Beta: Generate Table DDL script including ALTER TABLE statements for check constraints on 'GENERATE ALWAYS' columns. | CR044727 | |
| DDL Generation does not include Index Creation DDL |
CR0227632 |
|
| Constraints | Create Constraint: Exception occurs when 'Create Constraint' is selected | CR047236 |
| Table Alter | When the last column in a table was removed Toad indicated 'no changes detected' | CR051153 |
| Migration Wizard | Beta: 591 - Migration Wizard issue - Once the 'include objects that are dependent..' check box is checked - if it is unchecked, the Migration Wizard still believes it is checked. | CR049824 |
| Database browser filter | Exception encountered on 4.0.0.335 when on the table tab, changing schema filter in database browser to an asterisk (*). Users will be presented with a System.NullReferenceException and Toad may close. For now - avoid specifying * in the schema. | CR049597 |
| New Dependencies tab | When an object has a dependent constraint, at times an exception may appear when viewing the new Dependencies tab | NA |
| Table Alter LUW | Support: Add or remove MDC (multidimensional clustering) | CR047073 |
| Connection Version Check | Enh: Update DB2 version check to verify a minimum LUW version of 8.1.5 when Toad is connecting to db | CR047388 |
| Advanced Alter z/OS | Data loss during advanced alter of a table when the tablespace is placed in checking pending status | CR0222564 |
| Package LUW | DB2 truncation error when selecting package and clicking on USES tab in LUW only | CR0228752 |
| Advanced Alter | Foreign key references are not being re-created during advanced table alter | CR0228594 |
| Packages | Packages with the same name and same schema with different versions are now identified correctly | CR0225069 |
| Statistics Profiles LUW | Statistics profiles are now being preserved during advanced alters and are being migrated | CR0226714 |
| Comments in scripts | Scripts are now generated with -- comments that allow execution outside of Toad | CR0228395 |
| Structured Types | You can now define and alter structured types that contain methods | CR0212683 |
| Schema Report | Exception occured when attempting to generate a Schema Report on both LUW and Z/OS. | CR48115 |
| Explain errors | Errors caused by bad or missing explain tables have been addressed | CR0226717 |
The following is a list of issues known to exist at the time of the Toad for DB2 release.
|
Feature |
Known Issue |
Change Request |
| Migration Wizard | Toad throws an exception in Migration if the user defines a schema transformation rule, then attempts to define any other transformation rule. A work around would be to define your schema transformation last. | CR#51222 |
| Migration Wizard | Toad does not include some referenced/dependent objects. | CR#51027 |
| General | Customized options selected in the Configuration wizard are not applied if you are running as a Restricted user. | CR#216699 |
| Installation/ Upgrade |
If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing to avoid losing functionality in some DB2 native tools. |
CR#192879 Case#462823 |
| Connection | Manually configuring a connection using the Client Configuration Wizard fails on a Windows 2003 64-bit machine. | CR#202308 |
|
Attempting to launch Toad results in a
System.Security.Policy.PolicyException error. Workaround: |
CR#166752 Case#408845 | |
| Data Diff Viewer | Comparing a script results grid with an XSD file does not work. | CR#219662 |
| Data Reports | Currently, you cannot crate a Label Report in the Toad Data Report wizard. | CR#215945 |
| Database Browser/Obj Palette | ||
| Currently, you cannot grant privileges to a tables' columns for users. | CR#184359 | |
|
Any action that results in an advanced alteration on a table
that contains constraints results in the tablespace being placed in a
check pending state. This occurs because Toad loads the table data
before re-creating the constraints. Workaround: |
CR#222564 | |
|
Performance problems might occur when browsing a large number of
database objects. Workaround: |
CR#220761 | |
| Debugger | Currently, the debugger does not support Unicode schema names. | CR#184638 |
| Editor |
The following object types are not found when using the View Object at
Cursor feature:
|
CR#164917 |
| Export Data | Binary data types cannot be exported in this release. | CR#170430 |
|
When exporting large result sets (approximately 500K), you might run out
of memory before the operation completes. Workaround: Create a view for the query and export that view. |
CR#203483 | |
|
Exporting more than 65,536 rows to an Excel 2007 instance causes an
error.
|
CR#211832 | |
| Help | (LUW only) Object Details and Object Editor windows in the Database Browser/Object Palette have limited documentation in this release. This documentation will be expanded in a future release. | N/A |
| Schema Compare | (LUW only) If the source schema contains a table alias with the same name as the target schema, synchronizing the schemas results in the target schema name being replaced with the actual table name from the source table. | CR#140343 |
| Version Control | Toad is providing a more in-depth integration with popular VCS vendors. Currently, Toad integrated version control with Visual SourceSafe. If you are using CVS or SCC as the provider from the previous release of Toad, you currently cannot use those providers in Toad. Also, you might not want to migrate settings to the current release. | N/A |
|
The Update Schema function for version control often requires that
objects be dropped and recreated. If tables are referenced by foreign
key constraints, the following error occurs when executing the script: "Could not drop object N because it is referenced by a FOREIGN KEY constraint." |
CR#214601 | |
| Currently Version Control handles only DB2-standard schema names and file and folder names that are compatible with the underlying Version Control repository. | CR#217475 | |
| You currently cannot check object list definitions into version control. | CR#217524 |
The following is a list of third party issues known to exist at the time of the Toad for DB2 release.
|
Feature |
Known Issue |
Change Request |
| General | You cannot insert a double-byte character into a database with a single-byte codepage. IBM PMR30857,756,000 states that this configuration is not supported. |
CR#220327 Case#537948 |
| Installation |
You cannot install DB2 for LUW 8 on the same system that already has Toad for
DB2 4.0 installed. This problem exists because of a current DB2 limitation in
which DB2 for LUW 8 cannot be installed on a system on which DB2 for LUW
9 resides. (Toad for DB2 includes a customized version of DB2 for LUW 9.) Workaround: |
CR#187913 |
|
An SQL0805N error occurs when performing a DML statement on a database. Workaround: |
CR#220160 | |
| Database Browser/ Obj Palette |
(z/OS only) Attempting to drop a distinct type or sequence with a delimited
blank name results in following error due to server side abends: "IBM][CLI Driver] CLI0108E Communication link failure. SQLSTATE=40003" This is a known IBM DB2 issue and IBM has opened APAR PK3269 to track this issue. |
N/A |
| (z/OS only) In some cases, a user can revoke INSERT privileges on a table for the owner and cause a cascading revoke of privileges for any user (including the revoker) who was granted privileges by the table owner. This is a known IBM DB2 issue and IBM has opened APAR PK30558 to track this issue. | N/A | |
| Schemas containing empty names or special characters are not supported in this release and will display as QUEST_SCHEMA_PLACE_HOLDER when used. |
CR#133127 CR#133139 |
|
| A Microsoft .NET Framework issue causes an exception error when you attempt to browse the Data tab for a table containing a decimal value with a precision greater than 28 or 29. This issue is described in http://msdn2.microsoft.com/en-us/library/xtba3z33(vs.71).aspx. | CR#186529 | |
|
(z/OS only) The following DB2 error is generated when you try to refresh an MQ table: "ERROR [58031] [IBM] SQL1034C The database is damaged..." This error is identified in APAR PQ97328. The APAR states that, if the statement text in the CREATE TABLE statement for a materialized table is more than 4K, the statement text stored in the SYSVIEW.VIEWS catalog table entries for the table (after the first three sequence number entries) contains garbage. The APAR has been fixed with PTF UK00557. However, any materialized tables created before this fix need to be dropped and recreated and REFRESH rerun. |
N/A | |
| Timestamp data causes exceptions when you click the Data tab or attempt to query the table. This issue is related to the IBM DB2 APAR IY87346. | CR#220839 | |
| Data Grid |
(z/OS only) Tables that contain decimal data larger than 28 or 29 decimals
results in an error stating:
"Value was either too large or too small for a Decimal." This is due to a limitation in the .NET Framework in which the maximum decimal that the Framework can handle is 10^31 with 0 decimal.
Workaround:
Note: When using this workaround, if the number of characters is less than 32, leading zeros display. |
CR#186529 CR#186535 |
|
You cannot add data to tables that include columns that have the GENERATED
ALWAYS AS option enabled. The IBM Command Builder generates the INSERT statement
and includes the generated always column, which results in the following error:
"A value cannot be specified for column "GEN" which is defined as GENERATED ALWAYS. SQLSTATE=428C9" Workaround: |
CR#142504 | |
| Debugger | When compiling with debug, it is recommended that you disable AutoCommit (Tools | Options | Database | General) to allow a rollback if there is a problem when dropping and creating the procedure. Once you successfully create the procedure, commit the changes before starting the debugging session. | N/A |
| When debugging, you must enter a value for every start parameter, regardless of whether they are input or output values or an error message incorrectly informs you that the procedure must be compiled with debug information. | CR#143234 | |
|
(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: |
CR#188846 | |
| (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. | CR#207662 | |
| The "Unable to initialize debug session" error that is generated when you attempt to debug procedures in DB2 for LUW is a DB2-related issue. A future release of a DB2 unified debugger should help reduce the occurrence of this issue. |
Case#517909 Case#529227 CR#213765 |
|
| Editor |
Attempting to create an object in the SQL Editor when the schema selected from
the drop-down list in the Editor toolbar is different than the schema you logged
into, results in an error. Toad issues a SET CURRENT SCHEMA statement the
first time you execute a script/statement. Workaround:
|
CR#183855 |
| Export Wizard |
In order to export to an Office 2003 or 2007 Excel instance, the Office 2003 Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from
one of the following locations: |
CR#138239 |
| Help |
After installing Microsoft Security Update 896358, selecting a topic in the help
file when using the Web Browser (Internal Help) results in the topic displaying
in the navigation pane.
Workaround: |
CR#129554 |
|
After installing Microsoft Security Update KB922616, attempting to view the Help
file from the Web Browser (Internal Help) results in the following error: "COM object that has been separated from its underlying RCW cannot be used" Workaround: http://www.microsoft.com/technet/security/Bulletin/MS06-046.mspx |
N/A | |
| Log Reader | Sometimes DB2 writes an UPDATE command to the log after a CREATE TABLE command is executed. An exception error occurs when the Log Reader attempts to parse the record for the UPDATE command because the record contains unexpected or unparsed data. | CR#201537 |
| Schema Compare | (LUW only) You cannot synchronize schemas if the Code Pages on the compared schemas do not match. | CR#141383 |
| Version Control | Quest recommends using the native VSS implementation in Toad rather than VSS via SCC integration. When using VSS via SCC, if the file does not have the attributes that SCC expects, issues with the file being updated properly might occur. | CR#138078 |
Please review upgrade information in the Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.
Verify that your system meets the minimum requirements described in the following sections:
Toad for DB2 client installation requires the following.
Note: If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing to avoid losing functionality is some DB2 native tools.
| Platform | 600 MHz minimum |
| Memory | 512 MB of RAM minimum, 768 MB recommended Note: The memory required may vary based on the following:
|
| Hard Disk Space | 171 MB of disk space required to run Toad Note: The disk space required can vary based on the edition of Toad installed. |
| Operating System | Microsoft® Windows® 2000, XP Professional
(32-bit only), 2003 (32-bit only) Windows Vista (tested on 32-bit Ultimate edition with XP Graphics) |
| Additional Software | .NET Framework Microsoft .NET Framework 2.0 or later Note: In order to run Toad, the .NET security policy must be set to unrestricted. For more information, see User Privilege Requirements. Browser PDF Viewer |
| Other Requirements | SVGA monitor with a minimum resolution of 800x600, 1024x768 recommended |
Each DB2 database server requires the following:
| Database Versions |
IBM DB2 UDB for z/OS 8.1 or later Note: At this time, Toad supports DB2 for z/OS running in Full Function mode, but does not support DB2 running in Compatibility mode. IBM® DB2 UDB for Linux, UNIX, and Windows (LUW) 8.1.5 or later, 9.0 Note: To run RUNSTATS and the native REORG utility on tablespaces and indexes, Toad supports version 8.2.2 or later. |
| Database Operating System Platforms | z/OS (V1R6 Base Services [5694-A01] or later) Linux, UNIX, and Windows:
|
The following user privileges are required for installing and running Toad:
Note: Power users cannot install Toad on a Windows Vista Enterprise machine. This Windows limitation is due to the fact that the Power User mode is no longer used in Vista and therefore cannot install applications.
Associate file extensions.
From the Windows Start menu, select Settings | Control Panel.
Double-click Administrative Tools.
Double-click Microsoft .NET Framework 2.0 Configuration.
Click + to expand My Computer, and then select the Runtime Security Policy node. A list of tasks for the node display in the right panel.
Click Evaluate Assembly from the lists of tasks in the right panel. An Evaluate an Assemble window displays.
Browse to the location of Toad.exe in the File field.
Click Next to view permissions for Toad.exe.
Set the permission to Unrestricted.
READ permissions on the log files belonging to the database and on the directory where these files are stored
Database administrator privileges to read the database's log.
Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server Service Pack 2 using the Metaframe Access Suite 3.0 and Citrix Presentation Server Clients 10.0. For information about installing Toad in a Citrix environment, refer to Install Toad on a Citrix Machine in the Toad for DB2 Getting Started Guide.
To connect to a Lightweight Directory Application Protocol (LDAP) server, you must enable LDAP support and specify the host name and port number of the LDAP server for the DB2 client installed with Toad.
Note: You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the machine is already configured to support LDAP.
To configure Toad to use LDAP
db2set DB2_ENABLE_LDAP=YES
db2set DB2LDAPHOST=hostname[:port]
The port number defaults to 389 (default LDAP port) if you leave the port number blank.
Databases on the LDAP server should be available from the Database Alias drop-down list.
Note: At this point, Toad for DB2 supports only the access of DB2 LDAP catalog entries. Toad does not support the management of these entries (such as adding or removing them) Debugger Requirements
The following are the requirements for using Toad to compile and debug stored SQL procedures in DB2 for z/OS.
To use the Toad debugger on stored SQL procedures, the following Toad client requirement must be met:
Each DB2 subsystem on which you want to compile and debug stored SQL procedures must meet these requirements:
To bind and rebind packages and plans and to invoke utilities and commands within scripts like those scripts generated by advanced ALTERs or Migrations on a DB2 for z/OS subsystem, Toad for DB2 requires the following:
If neither product is installed on a subsystem, run edit and run the DDL that creates these objects. Click the following link to open the file containing this DDL:
Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.
User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects in Toad. To ensure the best possible performance from Toad, create the following indexes in each subsystem to which you are connecting in Toad:
CREATE INDEX TOADIX01
ON "SYSIBM"."SYSCOLUMNS"
("TBCREATOR" ASC,
"TBNAME" ASC,
"TYPESCHEMA" ASC,
"TYPENAME" ASC,
"COLTYPE" ASC
)
USING STOGROUP "SYSDEFLT"
PRIQTY 3600
SECQTY 3600
ERASE YES
FREEPAGE 0
PCTFREE 10
GBPCACHE CHANGED
DEFINE YES
BUFFERPOOL BP0
CLOSE NO
DEFER NO
COPY NO
PIECESIZE 2097152 K;
On the SYSTABLES table, as defined in the following DDL. Edit the DDL as needed for your site.
CREATE INDEX TOADIX02
ON "SYSIBM"."SYSTABLES"
("NAME" ASC,
"CREATOR" ASC,
"DBNAME" ASC,
"TSNAME" ASC
)
USING STOGROUP "SYSDEFLT"
PRIQTY 7200
SECQTY 7200
ERASE YES
FREEPAGE 0
PCTFREE 10
GBPCACHE CHANGED
DEFINE YES
BUFFERPOOL BP0
CLOSE NO
DEFER NO
COPY NO
PIECESIZE 2097152 K;
Adhere to these requirements when you use the Toad's Schema Migration wizard to migrate DB2 objects and their dependencies.
You must handle target tablespaces in one of two ways:
or
Notes:
When migrating a table that has referential-integrity relationships to other tables, select the Include dependencies option on the Select Objects for Migration page in the wizard. This option generates the statements necessary in the script to migrate the related tables. If you do not select this option, you must edit the migration script to include these statements.
The following requirements and restrictions exist for source and targets:
Note: When you are migrating objects between different versions, the Include statistics by default on the Select Objects for Migration page in the wizard is disabled.
Toad for DB2 supports the following version control providers for the versions and platforms listed. Testing is not complete for versions and platforms not listed:
| Supported Provider | Server Version Tested | Client Version Tested |
| Visual SourceSafe (VSS) | VSS 6.0d | VSS 6.0d |
| Concurrent Versions System (CVS) | CVS 1.11.22 on Solaris CVSNT 2.5.03 on Windows |
CVNT 2.5.03 |
| Subversion | Subversion 1.4.2 | Subversion 1.4.2 |
Ensure that you install the following on the same computer on which you installed Toad:
| Provider | Prerequisite |
| Visual SourceSafe (VSS) | VSS client |
| Concurrent Versions System (CVS) | CVS client |
| Subversion | Subversion binary package Note: When configuring version control in Toad, specify the binary path for the BinaryPath value on the Command Based Version Control Properties page in the Version Control wizard. |
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. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.
This release has the following known capabilities or limitations:
The Knowledge Xpert feature is available with English language content only.
The Toad for DB2 release package contains the following products:
For important information about installing Toad for DB2, refer to the Toad for DB2 Getting Started Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.
Caution:
|
For instructions on installing the Quest IBM DB2 z/OS component, refer to the Quest IBM DB2 z/OS Component Installation Guide. This guide is available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA | |
| Web |
Refer to our Web site for regional and international office information.
(Commercial and Trial Support only)
Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a commercial version and have a valid maintenance
contract.
Quest Support provides around the clock coverage with SupportLink,
our web self-service. Visit SupportLink at http://support.quest.com/.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, and policy and procedures.
The guide
is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.
You can join the Toad for DB2 beta discussion group by sending an email to: toaddb2beta-subscribe@yahoogroups.com
Participate in the Beta Yahoo! Board
This document 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.
© 2008 Quest Software, Inc. ALL RIGHTS RESERVED.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
If you have any questions regarding your potential use of this material, contact:
| Quest
Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 Email: legal@quest.com |
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.