Component

Resolved Issue

Case ID/ Change Request

Database Browser/ Obj Palette

Tablespace containers can now have more than 999 pages.

CID401289

The Overhead value now displays correctly when altering a tablespace.

CID403161

You can now alter sequences.

CID403197

Executing DDL no longer creates new sessions when re-executed. Toad now leaves the existing session open.  

CID416549

When cancelling changes made to database authority privileges for users or groups, the change is automatically updated in the Authorities tab.

CR0142105

Data Grid

Refreshing the data grid two or more times in a row no longer results in Toad hanging when the rows exceed the size of the data tab.

CID399272

DATETIME data types now support milliseconds. To select a

data type display that uses milliseconds, select a pre-defined format or create a custom format in the DateTime Format options in Tools | Options | Environment | Grid.

CID377585
CID405045

DDL Script Wizard

Currently, you can include only 30 tables when generating a DDL script.

CR0138084

Currently, a script is not generated if the client and server do not have the same FixPak version or the same value for the Codepage.

CR0136103

Debugger

Values of out parameters now display in the output window during debugging sessions.

CID391325

If the DATETIME format in a parameter string does not match your Windows regional settings, an error message now prompts you to enter the correct format.

CID429425

When debugging a procedure, the return code now returns a correct value of zero.

CID442944

If you set a breakpoint on an unsupported type, the debugger no longer ignores the breakpoint.

CR0136596

Editor

You can now change the size of columns in the Script Output window

CID377937

Comments using "--" and "/* ... */" now execute properly.

CID378365

SQL Modeler

Attempting to delete a record from the Result Sets tab in the SQL Modeler no longer results in an exception error.

CR0143158

Single quotes are no longer added incorrectly to generated queries.

CID441482

Component

Known Issue

Case ID/
Change Request

Installation

If a DB2 v7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to v8 before installing to avoid losing functionality in some DB2 native tools.

CID462823

Connection

If a DB2 client already exists on the machine where Toad is installed, a dialog prompts you to import catalog entries from the client the first time you launch Toad for DB2. Do not attempt to import catalog entries using this dialog if you have any DB2 ODBC entries cataloged because db2cfimp will overwrite your existing ODBC system DSN entries. This results in an error stating, "SQL Error State:IM003, Native Error Code: A0, ODBC Error: Specified driver could not be loaded due to system error 126" and can cause previously configured DB2 ODBC connections to stop working.

As a workaround, you can re-import a backup copy of the catalog to the original DB2 client using the following steps:

1. Open a DB2 command window using your original DB2 client.
    

2. Export the original catalogs using the following command:
   “db2cfexp C:\temp\db2catexport backup”
    

3. In the same command window, re-import the catalog file you just exported using the following command: “db2cfimp C:\temp\db2catexport”

This will force the DSN driver names back to the original “IBM DB2 ODBC DRIVER”.

CID460464
CID459956
CID462319

Attempting to launch Toad results in a System.Security.Policy.PolicyException error. To resolve this issue, ensure that the system administrator has placed Toad in the correct code group with permissions set to execute code.

CID408845

If the status bar is hidden, attempting to connect to a database using Toad results in a "Parameter is not valid" error. As a workaround, right-click the toolbar area in the main Toad window and enable the Statusbar.

CR0189787

Database Browser/ Obj Palette

Currently, you cannot filter by the number of rows when setting schema filters.

 CR0187906

Currently, you cannot grant privileges to a tables' columns for users.

CR0184359

Debugger

Currently, the debugger does not support Unicode schema names.

CR0184638

Editor

Toad cannot execute an SQL script in the Editor if syntax highlighting is disabled (Tools | Options | Editor | Highlighting Styles).

CR0167980

The following object types are not found when using the View Object at Cursor feature:

• Triggers

• Procedures

• Functions

• Users

• Hosts

CR0164917

Clicking Clear All Filters in the Editor toolbar does not take effect. As a workaround, click Define Filters and clear the filter manually, or open the Database Browser/Object Palette, and click Clear All Filters.

CR0189718

Currently, the same parameter name cannot be used more than once for multiple tables in a query.

CR0163853

If the Code Pages on the server and client do not match, you cannot generate a DDL script.

CR0136103

Explain Plan

Currently, the explain plan does not support Korean characters

CR0184449

Help

The following new features and enhancements have limited documentation in this release. This documentation will be expanded in a future release.

• Charts

• LUW Object Details and Object Editor dialogs in the Database Browser/Object Palette

• SQL Modeler subquery updates

Import Wizard

On z/OS only, you cannot import data using this wizard.

CR0189536

Object Search

Currently, you cannot search Unicode databases.

CR0166781

Schema Compare
 

On LUW, 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.

 CR0140343

SQL Modeler

Saved model files from the 1.0 release are not supported in the 2.0 release.

CID455708

SQL Optimizer

On LUW, in order to evaluate the SQL Optimizer functionality, you must download and install a trial version of the SQL Optimizer separately from:  http://www.quest.com/quest_sql_optimizer_for_db2_udb/index.asp.

Once installed, click the SQL Optimizer toolbar icon in Toad to launch the SQL Optimizer.

CR0153015

Version Control

Some error messages are currently available with English language content only.

CR0140084

Component

Resolved Issue

Case ID/
Change Request

Database Browser/ Obj Palette

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

CR0183855

Schemas containing empty names or special characters are not supported in this release and will display as QUEST_SCHEMA_PLACE_HOLDER when used.

CR0133127

CR0133139

Data Grid

On z/OS, 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.

As a 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.

CR0186529

CR0186535

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

As a workaround, use the Editor to insert data into tables that include the "Generated always as" option set.

R0142504

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, please remember to commit the changes before starting the debugging session.

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.

CR0143234

Export Wizard

In order to export to an Office 2003 Excel instance, the Office 2003 Primary Interop Assemblies (PIAs) must be installed. You can install the PIAs from:  http://www.microsoft.com/downloads/details.aspx?FamilyID=3c9a983a-ac14-4125-8ba0-d36d67e0f4ad&DisplayLang=en

CR0138239

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. Quest recommends using External Help (Tools | Options | Environment | Interface) as a workaround. If you want to use Internal Help, you will need to disable some features in the security update. Refer to Microsoft Knowledge Base article: http://support.microsoft.com/kb/896905/ for steps to re-enable these features in ActiveX.

CR0129554

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." Quest recommends using External Help (Tools | Options | Environment | Interface) as a workaround. If you want to use Internal Help, you will need to disable some features in the security update. Refer to Microsoft Security Bulletin MS06-046: http://www.microsoft.com/technet/security/Bulletin/MS06-046.mspx

Schema Compare

On LUW, you cannot synchronize schemas if the Code Pages on the compared schemas do not match.

CR0141383

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, there may be issues with the file being updated properly.

CR0138078