
Toad™ for IBM® DB2®
Version 3.0.1
Release Notes
September 2007
| 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.
Review the following:
Tab Renaming—Rename tabs in document windows by pressing F2 or by right-clicking the tab and selecting Rename Document.
Connection Organizing—Use drag-and-drop in the Connection Manager to reorganize connections and connection groups.
Connection Renaming—Rename connections and connection groups in the Connection Manager by pressing F2 or by right-clicking an item and selecting Rename.
Service Management—In
the Connection Manager, start, stop, or pause a database service in Windows by right-clicking a connection:

Redesigned Connection Toolbar—Perform
connection-related actions formerly accessed from the standard Toad
toolbar. These actions include Open Connections (used for creating and
saving new connections), Commit, and Rollback. The toolbar also contains
a drop-down list of available connections, allowing you to switch easily
between connections.

You can right-click the current connection in the drop-down list to access functionality associated with the connection, including options to disconnect from the connection, disconnect from all connections, view connection properties, or open documents associated with the connection.
Redesigned Connections Window—Perform these functions and tasks easily from the Connections window (formerly the New Connections window):
Click Save to save connection information for later use without having to connect.
Edit connection properties in the right pane (including the default DB2 schema or authorization ID and certain DB2 registry settings for the connection), and then save or undo your edits.
Create a new connection.
Import connections to Toad or export your Toad connections to a
file.

Side-by-Side Grid View—Now display the Card view side-by-side with the Grid view on Data tab.
Edit and Read-Only Toggle—Right-click the green (or red) button in the lower left of the Data grid to toggle between edit (Grid has custom editing) mode and read-only (Grid is read-only...) mode.
Row Copy Support—Copy multiple cells of
data. Press Ctrl and click each cell to select the cells to copy; then
right-click and select Copy Rows.

Row Flagging—Flag rows on the Data tab in the Database Browser by clicking within the margin of the row. Review the following guidelines for using this feature:
This option does not apply to data queried from the Editor.
The table you are browsing must have a primary key.
The flag is tied to values of the primary
key. Therefore, if the value changes, the row is no longer flagged. Also, if you
alter the table and change the primary key, all flagged rows are
removed.

Line Numbers for Data—Add a line number to the margin in the data grid to locate or reference a row quickly when working with colleagues. This feature is enabled in Tools | Options | Environment | Grid.
Merge Results—Display results in a single, stacked data grid if a query returns multiple results. This feature is enabled in Tools | Options | Database | Script Result.
You can now start the Toad Data Report wizard from the Tools menu (select Tools | Data Report Designer) and from within the Reports Manager (right-click a folder and select Create Data Report).
Primary Key and Not Null Indicators—Easily
identify key columns and columns that do not allow null values. A key
icon next to a column name indicates a primary key; and an asterisk next
to the column name indicates a Not Null column. The Not Null indicator
is also available for query result sets in the Editor. (The primary key
indicator is not available in the Editor.)

Enhanced SQL Generate Feature—Use the
Generate SQL option to send a generated SQL script for a table or
view to the Editor or
a clipboard or to save it to a file:

Connection Changing—Change the connection
associated with the current window by right-clicking the tab, selecting
Change Connection, and selecting an available connection:
![]()
Tab Renaming—Rename
tabs in documents windows by pressing F2 or by right-clicking the tab
and selecting Rename Document:

Line Commenting—Easily comment or
uncomment lines of code by selecting the code text, right-clicking, and selecting
Comment Lines or Uncomment
Lines. You can also use the keyboard shortcuts Ctrl+Minus (to comment
lines) and Ctrl+Shift+Minus (to uncomment lines).

Query Execution Enhancements—Display query results using these new enhancements:
A collapsed results pane automatically expands when you execute a script (F5) or an SQL statement (F9) or when you verify SQL.
Multiple result sets are now merged
automatically by default, instead of displaying in separate tabs. A
navigation panel displays to the left of the result sets, enabling you
to navigate quickly to each set. The number of columns and rows (shown
as columns number X rows number) also displays in the
navigation panel.

To specify the default format for displaying
results sets (as either merged sets or individual tabs), use Tools |
Options | Database | Script Result. You can also modify the maximum
number of result sets to display for a query. (The default is 100.)

Intellisense—Add an asterisk as the first entry in the auto-completion list for columns. If you specify the asterisk, all columns for the table are added to the list. This feature is enabled in Tools | Options | Editor | Toad Insight.
Add Notes—Right-click
a pane, table, or relationship to add notes:

Manual Relationships—Create manual relationships.
Diagram Schema—Quickly diagram all tables in a schema.
Query Builder Integration—Send a diagram to the Query Builder.
Tree View—Now use a standard tree view to quickly navigate between pages in the Options window.
Modeling Options—Go to the Database | Diagramming and Query Builder pages to modify options formerly on the Modeling page.
New DB2 Options—On the Database | DB2 page, specify object-editor options for handling advanced alterations, creating object-editor templates, and removing comments in SQL before execution.
Updated Keyboard Options—Use the enhanced Environment | Keyboard page to assign keyboard shortcuts more easily:
You can now edit the Default keyboard scheme.
You can click Default beside the Shortcut currently used by field to revert back to the default shortcuts for the selected keyboard command.
You no longer have to click Assign for keyboard shortcuts to be saved. They are now applied when you move the cursor focus to another command.
Network Share Option—Specify a location where you can share reports from the Report Manager or files and directories from the Project Manager with your colleagues.
New Toolbar—Use the toolbar to
start the project creation process quickly:

Use the toolbar to navigate to other projects
easily:

To-Do Items—Keep up with project or daily
tasks using the new To-Do Items feature. To create a To-Do list,
right-click a resource node in the Project Manager, and select New |
To Do Item:

Double-click the clipboard beside the To-Do item to assign a due date and to add any notes. With an assigned due date, the item's text changes to red when it is past due. Also, the notes display as a tool tip when you hover the cursor over the item.


To access
this feature, in the Diagram pane, right-click the ID column for which you want to find
descriptive information, and select Find Lookup
Table. The Find Lookup Table window is displayed, showing a Tables pane
that lists all tables defined with a column with the selected column name.


DB2 for LUW Version 9 FixPak 1 Load Modules—Toad for DB2 Version 3.0 ships with the IBM DB2 for LUW Version 9 FixPak 1 modules.
Object Notes—Add notes to objects in the Database Browser, Object Palette, ER Diagram,
and Query Builder.

One-Click Export—Easily export data using
default settings from the Editor, Query Builder, and Database Browser.
![]()
Note: When using this feature with Database Browser, first select the Data tab before selecting any of the one-click export actions to avoid hanging Toad.
Object Lists—Group specific objects into
named object lists. You can run remedial utilities and object
migration in Toad against an object list, without having to select the
objects individually. When you run one of these functions against an
object list, you can be certain that the generated script does not
reference objects that could halt the execution. To run a utility or a
migration against an object list, right-click the object list name, and
select the option for the appropriate function.

Templates—Save and reuse specific object attributes as templates for creating other objects. You can create both regular templates, which you manually load in the object editors, and default templates, which are automatically loaded each time you open object editors. When you define a default template for an object type, Toad gives you the option to designate it as the default for the database (or subsystem) or for the user connection to that database (or subsystem).
The toolbar located on
each Create or Create Like window provides options to load an existing
template or to create a regular or default template from the current
object attributes.

Advanced Alteration—Perform database object alterations that cannot be performed by ALTER SQL statements. Toad for DB2 analyzes the changes you want to make to objects and generates scripts that contain either ALTER statements or, if advanced alteration is needed, statements that drop and recreate the objects.
DB2 for LUW Version 9 Support for Objects—Manage objects using Version 9 enhancements and updates now included in Toad object editors.
New Object Editors for DB2 for LUW—Manage DB2 for LUW buffer pools and database partition groups (including stripe sets) using Toad object editors.
New Object Editors for DB2 for z/OS—Manage DB2 for z/OS auxiliary tables and storage groups using Toad object editors.
Thread Activity (DB2 for z/OS)—View
details about current threads connected to your DB2 for z/OS database.

Database and Database Manager Configuration Parameter Management (DB2 for LUW)—Review and edit current database and database configuration parameters values.
Support for Transfer Ownership (DB2 for LUW)—Change
ownership of objects using the DB2 TRANSFER OWNERSHIP command.

Enhanced Table and Index Reorganization
Utility (DB2 for LUW)—Run this utility on one or more tables or indexes
at the table, index, or tablespace level. The newly designed Reorg
window lets you specify reorganization options for the individual tables or
indexes and for the REORG command in general. Additionally, the utility now
supports both REORG INDEXES ALL and REORG INDEX commands.

New RUNSTATS Utility (DB2 for LUW)—Execute
this utility on one or more tables at the table or tablespace level. The
Runstats-Tables window allows you to specify RUNSTATS options for
individual tables and for the command in general.

Compare differences in DDL or in files using the new Diff Viewer. Access the Diff Viewer using one of the following methods:
Select Tools | Diff Viewer. You can then select any two files to compare.
Right-click an object or data grid, and select Send To | Diff Viewer.
Note: You cannot make updates to files in the current database.
You can now open existing reports or spreadsheets without leaving Toad.
Note: When using this feature, have only one Excel file
open at a time. If more than one file is open, the Excel toolbar is disabled
for the additional files.

The Toad for DB2 Schema Migration wizard migrates objects from a source DB2 database or subsystem to a target database or subsystem. The migration process runs in the background so you can continue to work on other tasks. To start the wizard, select one or more objects to migrate, right-click, and select Migrate Object(s). You can also select Advanced | Migration.
Using Schema Migration wizard, you can do the following:



Note: Currently Schema Migration does not migrate object data.


The new Quest IBM DB2 z/OS component is available with this release of Toad for DB2. You install this component on each DB2 for z/OS subsystem that you want Toad to manage. In addition to the object-management functionality already provided with Toad, this component enables you to perform the following in Toad:
View the list of volumes available for defining a storage group in the subsystem.
View the information about the current threads connected to the subsystem.
Perform future product features
The new Reports Manager lets you quickly manage reports or use canned reports provided by Toad. To access this feature, select View | Reports Manager.

Toad now supports editing DB2 special register values at the connection level and at the Editor level.
When you set up a
Toad connection to a DB2 database or subsystem, you can define certain special
register values that are then in effect each time Toad connects to the database or
subsystem.

Additionally, you can override special register values for the duration
of a specific Editor session. To do so, click the Set Register Value
toolbar button in the Editor to display the Alter Special Registers window.
Then make changes to the listed special register values.
To be able to override special register values in the Editor, make sure that you use the following settings on the Tools | Options | Editor | General page:

If you select to log information to a file, this log file is stored in C:\Documents and Settings\username\Local Settings\Application Data\Quest Software\Toad for database version\ConnectionTrace.log. You can view the log file in the Editor by selecting Tools | SQL Trace | Show Logfile.
Note: Because SQL Trace logs information for each execution, it can slow performance on your computer.
Use the new Web Search feature to Google (or perform another type of web
search) without leaving Toad. From the toolbar in the main window, select
the search engine type (such as Google), enter the search criteria, and
click Search.

Customize you searches by adding your own search engines or web sites under
Tools | Options | Environment | Quick Search.

The following is a list of issues addressed and enhancements implemented in this release of Toad for DB2.
|
Feature |
Resolved Issue |
Change Request |
| General | ||
| Toad has resolved the character issue that occurs when Regional Options is set to Turkish on the client computer. |
CR#224551 Case#555563 |
|
| Editor | ||
| If a user attempts to close the Editor when a lock exists on an object because of an uncommitted transaction, the Editor notifies the user of this condition. |
CR#224712 Case#540318 | |
| Schema Compare | Schema Compare is automatically enabled for users with commercial or term licenses for the Standard, Professional, or Xpert editions of Toad for DB2 2.5 or earlier. |
CR#223702 Case#550259 |
|
Component |
Resolved Issue |
Change Request |
| General | Korean code page issues—repeating characters in the Editor and import and export issues—have been addressed or resolved. |
CR#201538 Case#484626 |
| Option to have Toad remove comments from SQL before execution has been implemented under Tools | Options | Database | DB2. |
CR#213765 Case#529227 | |
| Connection information is now being properly added to the support bundle. | CR#213808 | |
| Installation | Silent installation is now available. |
CR#200792 Case#481561 |
| Connection Manager | In the Client Configuration wizard, the Authentication field now has an Not Specified (NOSPEC) option. |
CR#201753 Case#481133 |
| The Operating System drop-down list on the Add a Host page in the Client Configuration wizard now uses a single Windows option to represent all Windows types. |
CR#204638 Case#491829 | |
| Previously, if you upgraded IBM DB2 for LUW version 9 from FixPak 0 to FixPak 1, specifying the Work with Existing option, Toad for DB2 might issue an exception error when you tried to establish a database connection. To resolve the issue, Toad for DB2 version 3.0 now ships with the IBM DB2 for LUW version 9 FixPak 1 modules. | CR#204844 | |
| Database Browser/ Obj Palette | ||
| You can now remove columns when altering a table. |
CR#156271 Case#391667 | |
| Performance time in generating table scripts has improved significantly. |
CR#191534 Case#460284 | |
| The expand bar between the Parent Table Information and the This Table sections is working properly. |
CR#192553 Case#462812 | |
| You can now generate DDL for dependencies (for example, triggers, views, grants, indexes, procedures, and so on) from the Script tab if you select Generate script for dependent objects. |
CR#195671 Case#468471 | |
| The USER and GROUP keywords are now properly generated in the GRANT statement of the table DDL. |
CR#196653 Case#472046 | |
| Newly created indexes are now showing in up on the Indexes tab on the right-hand side of the browser. |
CR#197858 Case#474681 | |
| Issues with separators in trigger scripts has been resolved. |
CR#201407 Case#480305 | |
| DDL script now shows ALLOW REVERSE SCANS on indexes. |
CR#201389 Case#484643 | |
| Table editor now supports both COMPRESS and VALUE COMPRESSION. |
CR#202702 Case#490028 | |
| CLOB columns now display their size with the correct byte designation. |
CR#204490 Case#494668 | |
| You can now generate the DDL for the selected objects and its dependencies from the Script tab if you select Generate script for dependent objects. |
CR#204491 Case#494685 | |
| Adding a container to a tablespace no longer generates the error "SQL0104N An unexpected token '-' was found following 'ADD TO STRIPE SET.'" |
CR#204658 Case#493644 | |
| DDL script now shows WITH DEFAULT clause. |
CR#206226 Case#498970 | |
| The error generated when processing a view script no longer occurs. |
CR#209844 Case#507431 | |
| The user can now use the lower-left green button to toggle between edit and read-only mode on the Data tab. |
CR#209106 Case#511935 | |
| The error "Object reference not set to an instance of an object" generated when browsing the Used By tab for tables could not be reproduced. |
CR#214721 Case#522183 | |
| The errors generated when clicking between different tables in the browser cannot be reproduced. |
CR#214723 Case#522187 | |
| Generating the script for a view on the Script tab no longer produces a script-processing error. |
CR#218072 Case#531345 | |
| You can now filter by the number of rows when setting schema filters. | CR#187906 | |
| Trigger DDL no longer displays as a single row on the Triggers tab for a table. | CR#201408 | |
| Double-clicking on a trigger on the Trigger tab for a table now takes you to that trigger in the browser. | CR#201410 | |
| Debugger | 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. |
CR#213765 Case#517909 Case#529227 |
| Editor | Toad has normal limitations on the performing row counts. |
CR#199771 Case#479827 |
| If user changes the schema in the drop down, both SET CURRENT SCHEMA and SET CURRENT SQLID statements will be executed. |
CR#205955 Case#497777 | |
| The data grid no longer locks down after data is changed and the query rerun. |
CR#210700 Case#502892 | |
| You can now use the same parameter name more than once for multiple tables in a query. | CR#163853 | |
| The inability to generate a DDL script when the code pages on the server and client do not match is no longer an issue. | CR#136103 | |
| Explain Plan | The explain plan now supports Korean characters. | CR#184449 |
| Export Data | When exporting a large amount of data, the user is now prompted to re-execute the currently running query to avoid reading the complete dataset into memory. |
CR#201720 Case#484690 |
| Log Reader for DB2 | ||
| The code page issue has been resolved. Connecting to a database no longer generates the error "Object reference not set to an instance of an object" and shuts down Toad. |
CR#219371 Case#534404 |
|
| Search conditions in the Log Reader Advanced Search feature are processed with OR logic, not AND logic. | CR#194746 | |
| A message now displays on the Redo tab on the DML/DDL page if UPDATE command is not supported. | CR#202373 | |
| Log Reader now generates the correct Undo script to insert BLOB, CLOB, DATALINK, or LONG VARCHAR values in a table. | CR#202602 | |
| An exception error is no longer generated when the user attempts to select a transaction on the Transactions page after canceling a rerun of the Read Log File wizard. | CR#202699 | |
| Migration | Issue with migrating Oracle stored procedures to DB2 is resolved. |
CR#172843 Case#422459 |
| Object Search | You can search Unicode databases. | CR#166781 |
| Schema Compare | Schema Compare now shows differences in the DB2-generated name for the same procedure on the source and target, but will not generate an ALTER script. |
CR#218070 Case#529304 |
| SQL Modeler (now Query Builder) | SQL generated in the SQL Modeler could not be executed in the Modeler. This has been fixed. |
CR#183510 Case#441482 |
| SQL Optimizer |
(LUW only) The SQL Optimizer toolbar icon is enabled only when you have
Quest SQL Optimizer for DB2 installed. You can download SQL Optimizer
from the following location as part of the Toad for DB2 Xpert Edition
trial: http://www.quest.com/toad-for-db2/Software_downloads.aspx Once installed, click the SQL Optimizer toolbar icon in Toad to launch the SQL Optimizer. |
CR#153015 |
| SQL Recall | You can now see the entire SQL query when you move the mouse cursor over the SQL Text entry in the SQL Recall window. | CR#177941 |
| Version Control | Previously, some error messages are currently available with English language content only. This issue has been resolved by an overall design change. | CR#140084 |
The following is a list of issues known to exist at the time of the Toad for DB2 release.
|
Feature |
Known Issue |
Change Request |
| 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 | |
| An advanced alteration on a unique index generates an incorrect DROP syntax for dropping foreign key restraints. | CR#219910 | |
|
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 | Toad cannot execute an SQL script in the Editor if syntax highlighting is disabled (Tools | Options | Editor | Highlighting Styles). | CR#167980 |
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 |
| Log Reader for DB2 | If the user has selected the incorrect processor architecture, the wrong error message is displayed as the Log Reader reads files | CR#181504 |
| Log Reader does not support a proxy when using FTP to access log files. | CR#199332 | |
| The Log Reader temporary files on the local drive are not deleted under the these circumstances: Toad is shut down via Task Manager while Log Reader is loading log information, or the FTP connection is aborted while Log Reader is loading log information. | CR#199340 | |
| The Log Reader Undo/Redo SQL wizard currently does not provide a comment in the script to explain when the Log Reader is unable to redo or undo a specific command. | CR#199336 | |
| Log Reader cannot parse commands involving DATALINK columns. | CR#199338 | |
| Log reader creates temporary files in Log_Reader_installation_path/Tmp directory on the local disk. Normally, these files are deleted. However, these files can remain on the local disk if, while the Log Reader was loading files, either the FTP process was aborted or Toad was closed down through the Task Manager. | CR#199340 | |
| Results from running the Advanced Search function show an invalid data type value for distinct type, structured type, and DATALINK columns. | CR#202208 | |
| The Undo script for stored procedures contains incorrect syntax. | CR#202327 | |
| Object names using different encoding schemes are not displaying properly in the Advanced Search window. | CR#202667 | |
| The Log Reader can parse the log files for only the database to which it is currently connected. | N/A | |
| For a multi-partitioned database, the Log Reader can parse the log files for only the database partition to which you are currently connected. | 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 |
| Toad Security | The DBA edition of Toad for DB2 overrides all Toad Security settings. However, this override feature is currently not working. | CR#221808 |
| 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 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: |
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 following minimum 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 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 or x64), 2003 Windows Vista (tested on 32-bit Ultimate edition with XP Graphics) |
| Additional Software | .NET Framework 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: Toad supports DB2 for z/OS running in Full Function mode, but does not support DB2 running in Compatibility mode at this time. IBM® DB2 UDB for Linux, UNIX, and Windows (LUW) 8.1.5 or later, 9.0 |
| 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:
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.
(Freeware Support)
You can