Toad (r) Copyright (c) 1995-2006 Quest Software All Rights Reserved

Toad 9.0 ReleaseNotes

LAST REVISED: 16-OCT-06

Table of Contents

Introduction

These Release Notes are intended to provide an overview of new functionality and to list many of the fixes that have been implemented in this release of Toad. The Release Notes are also intended to help you upgrade to the new version. For a short summary of new features, also see the "New in Toad" topic in the Toad help file. For an introduction to Toad, please see TOAD Getting Started Guide located in the 'docs' folder.

Toad for Oracle 9.0 continues our commitment to providing new features while improving and streamlining existing features and windows. The 9.0 development cycle focused on stability, usability, and consistency. Some examples include the redesign of the menus to be more intuitive, combining the editors into one window that uses shared commands. In addition the new editor has much greater flexibility for parsing syntax highlighting, including the ability for you to design your own languages. A detailed Reports Manager has been added to provide pre-designed reports and queries through FastReports. In addition, the SQL Modeler has been renamed the Query Builder, and will now reverse-engineer any query it could have created; explain plans have been made easier to read; and RAC support has been improved throughout Toad.

In the Toad Professional Edition, the Code Xpert is now available from the right-click menu around Toad. In addition, it is available in a standalone window from the menus.

In the Quest DBA module, a DBMS_REDEFINITION Wizard has been added to make it easy to redefine and rebuild your tables online. This feature uses Oracle's DBMS_REDEFINITION package. From the Top Session Finder, find any selected session in the Session Browser with just a click. Also, ADDM/AWR functionality has been greatly expanded. Run several automatic reports, create snapshots and baselines easily from Toad.

In the Quest eBiz Module, the reporting functionality has been merged with Toad Reports Manager to make reports easier to find and manage.

Top

Important Installation and Upgrade Information

ITEMDETAILS
DesktopsDue to the Editor merge and the addition of new functionality in Toad 9.0, we can no longer preserve old desktop layouts from previous versions of Toad. All previously saved desktop layouts for the main Toad desktop and the Procedure/SQL Editor desktops will be overwritten to the new default layouts. Once Toad is upgraded, users are advised to add customizations back if they wish.
Editor OptionsToad now uses a new Editor component, therefore not all pre-9.0 Editor options could be preserved on upgrade. The new "Auto Replace" and "Code Templates" options will recognize your pre-9.0 configurations and will not be lost when upgrading. As for the rest of the old "Editor options" (linked from Toad's main options screen in previous versions), they are now merged in with the other Toad options. The options in question will now revert back to the default settings as if you were re-installing Toad. For example, any custom Editor key mappings that were set for previous Toad versions will not be remembered when you upgrade. The key mappings will be set to match the defaults for Toad 8.6
Editor ToolbarsDue to the Editor merge and the addition of new functionality in Toad 9.0, we can no longer preserve old SQL Editor and Procedure Editor toolbar layouts if upgrading from previous versions of Toad. Since the 2 Editors have been combined into a single Editor, there was no way for us to determine which toolbar to preserve. In addition, new toolbar items available in the single Editor would not be seen for upgrading users.
Editors MergeIn Toad version 9.0, the SQL Editor, Procedure Editor, and Text Editor have been merged into a single Editor. The new Editor features context sensitive execution (F9 key or green arrow button). The new execution routine can identify the statement at your caret and perform the correct execution action when a single Editor tab contains heterogeneous statements. PL/SQL can also be compiled directly from the Editor's navigator panel via the Right-click menu. Script Execution is still available in the new editor as well as 3 debuggers (PL/SQL, JDWP, and Script). Only 1 debugger may be used at a time, use the "debug" main menu to switch between debuggers. "Execute Statement at cursor" is still available via Shift+F9, Ctrl+Enter, and the button may be added back to the toolbar using customizable toolbars. The new Editor now has 5 different "Tab Styles" that are used depending on what you are doing in the Editor. For example, if "XML" tab is selected, the tab will be in XML editor mode using the HTML parser and an XML tree will appear. Tab styles are also associated with a Desktop layout and file extensions.
Object LoadingThe Toad 8.6 option to include owner when extracting source from database has been changed. There are 3 choices now in Options > Editor > Open/Save > Object Loading options group. Always include, never include, and include when the owner of the object to load is not that of the connected schema. In 8.6, if USER1 loads an object owned by USER2 and the include schema option was unchecked then compiling would still compile that object in the USER2 schema. For 9.0 if the schema name is not present then compiling will always occur in the connected schema. The new options set is not mapped to the old "Include owner when extracting source from database" option and defaults to always include owner.
OptionsDue to the Editor merge and the introduction of a new Editor component, there has been some significant options re-work throughout Toad. For example, options previously found in the stand-alone "Editor Options" are now included with the rest of the Toad options. All of the old SQL Editor and Procedure Editor options have been moved and reorganized to be more intuitive with the single Editor. The best way to find the option you are looking for it to use the Options window's search function.
Script Execution and DBMS OutputThe script execution is an almost identical replacement for SQL*Plus so all script output will go to the script output tab in Toad 9.0. As with SQL*Plus, to see DBMS Output while running a script, a 'SET SERVEROUTPUT ON' command will have to appear at the beginning of your scripts. For frequent use of the server output command, we suggest adding this to your login.sql file.
Toad Main MenuThe Toad menus have been completely restructured for Toad 9.0. The new Session menu contains session-specific items such as creating and ending connections and anything else that can modify specific connections. The Database menu has been greatly expanded and generally contains all of the Oracle functionality, arranged by function. The new Utilities menu contains non-connection/Oracle windows for the most part, such as Network Utilities, Archive, and FTP. In the Files menu, you will now find items that operate on files only. The View menu toggles the visibility state of dockable windows along with a few other items that fit nicely in that category. The Search menu contains all search-related functionality from searching text to Oracle object search. The Edit and Grid menus have been left untouched. The "SQL Editor" menu has been renamed to "Editor" menu and the debug menu has not changed with the exception of removing items whose only function was to toggle the visibility of Editor sub-tabs.
eBiz ReportsAs of Toad 9.0, eBiz Reports, which used to reside in the "eBiz" menu have been moved to Database > Reports > Reports Manager
Master/Detail BrowserAs of Toad 8.6, this window no longer remembers previously selected relationships or filter conditions. This behavior has been replaced with the Open/Save Relationship functionality.
SQL Editor Script OptionsThe Toad script options have been removed as of Toad 8.5. Toad now respects the SQL*Plus standard login.sql and glogin.sql. The Script options section in SQL Editor options will display this path when login.sql and/or glogin.sql are found. You can also open these files for editing from Toad's options window.
Server Login WindowAs of Toad 8.5, The 'SQL*Net compatible Net8' and 'Force SQL*Net (ignore Net8)' options have been removed. These options are no longer necessary since the bugs that they were used as workarounds for have been fixed.
Threaded QueriesAs of Toad 8.5, the SQL Editor options "Process statements in threads / allow queries to be cancelled", "Process Update, Insert, and Delete statements in background (threaded)" and "Process PL/SQL statements and DDL in background (threaded)" have been replaced with the new General option "Execute in threads (creates a new session for every active query). This new option provides true threaded query support. A "Query Viewer" window and new SQL Editor subtab have been added to supplement this new functionality. As of Toad 9.0, When using TQ, the "Commit" and "Rollback" buttons on Toad's main toolbar now only act on the current threaded session, instead of acting on all open threads for the current connection.
ToolbarsToad's pre-packaged toolbar templates have been depreciated as of Toad 8.5. The toolbars will no longer be updated with this and all subsequent Toad releases. However, the toolbars will still appear in your custom toolbar list as read-write. The depreciated toolbar may still be used but will be missing new features.
Microsoft Windows SupportAs of version 7.6, Toad no longer supports Windows 98. Toad supports Windows 2003, NT 4.0, Windows 2000, Windows XP, and Windows 2003. We recommend the latest patches for each operating system.
Newline format for character dataThe option to "Convert CRLF to LF" has been changed to "Newline format for character data" with choices "Unix" and "Windows" as of TOAD 7.6. If "Unix" is selected, then the behavior is the same as it was with "Convert CRLF to LF" checked: Toad converts carriage return-linefeed pairs in altered text data to linefeeds. If "Windows" is selected, however, then Toad will convert linefeeds in altered text data to carriage return-linefeed pairs.
Schema Definition FilesSchemaDefFileConverter.exe" was discontinued as of version 7.6. Schema definition files (.def files) created from Generate Schema Script in previous versions of Toad (pre 7.6) will no longer newer versions of Toad. Only Schema Definition Files extracted from a live schema using Toad 8.5 will work in Generate Schema Script.
Team CodingIf you plan to use Team Coding, we strongly recommend that you check Options > Editor > Execute/Compile > Toggle modified flag after compiling source loaded from database. The option defaults to checked in TOAD 7.5, but it is remembered from your previous installs, where it defaulted to unchecked. If the option is unchecked, then switching tabs or windows will disable check-in until you compile again.
Team Coding Upgrade from 7.5Views are now recognized in Toad's Team Coding module. If you are upgrading from TOAD 7.5, you will need to run the Server Side Objects wizard to update your Team Coding objects. When you upgrade your Team Coding objects from TOAD 7.5 to Toad 8.5, Team Coding will work with TOAD 8.5 and continue to work with TOAD 7.5 as long as CVS is not used as your version control provider. CVS is not supported in older versions.
TOAD Security Upgrade from TOAD 7.3The items you restricted through TOAD Security in versions 7.3, 7.4, 7.5, 7.6, or 8.0 will still be restricted in Toad 8.5, and there is nothing additional you will need to do. The following items can now be restricted in Toad 8.5:
Parser and Syntax Highlighting in EditorDue to the Editor merge and the addition of new functionality in Toad 9.0, we can no longer preserve custom syntax highlighting, or any other parser customizations made to Toad's pre-9.0 parser files.
Top

Windows Removed from Toad

Options

Options > General > "Prompt to close windows when closing connections". The behavior now is that all windows associated with a closing connection will close on a connection end. Connection-specific windows are useless and cause errors if they remain open after a connection is closed.

Options

Options > Procedure Editor > General: "Search for dependent objects after compile" option has been removed. This option can no longer be supported with multiple object support in the new editor.

Options

Options > Parser Scripts section has been removed. You can find similar options here: Options > Editor > Behavior > Languages

Options > Editors

Options > Editors Options > General > 2 "TNSNames Files" options removed: "Reload last used files" and "Backup Files during saves". The window now behaves as if both of these items were checked.

Options > Editors

Options > Editors > SQL/Procedure: "Variable Prefixes" section has been removed. This option was for sending text between the SE and PE and nothing else. With one editor that option is no longer needed.

Reports

Toad Reports have been removed. All of the reports previously available from this window have been recreated in Toad's new "Report Manager" (View menu). 3 previously available reports were not recreated because of redundancy. These reports include "Stand Alone Stored Arguments", "Arguments of stand alone stored programs", and "Stored objects with source"

eBiz Module

eBiz > Reports menu item has been removed. The same reports can now be found in the Reports Manager for eBiz module users (View > Reports Manager)

Top

Enhancements

Enhancements for Base Toad

Action Console

Analyze All Objects

Command Line

Compare Data

Compare Schemas

Copy Data to Another Schema

Data Grids

Data Subset Wizard

Editor

Estimate Index Size

Estimate Table Size

Explain Plan

External Tools

FTP

Find in Files

Flat File Export

Grid > Report

Health Check

Import Table Data

Master/Detail Browser

Options

Options > Editors

Options > Files

Options > Schema Browser

Options > Toolbars/Menus

Procedure Editor

Project Manager

Query Builder

Query Viewer

Reports Manager

Role Script

SB > Contexts

SB > Data Tab

SB > Filters

SB > Indexes

SB > Invalid Objects

SB > Packages

SB > Snapshots

SB > Tables

SB > Tables > Columns

SB > Tables > Constraints

SB > Tables > Data

SB > Tables > Referential

SB > Tables > Triggers

SB > Tablespaces > Objects

SB > Triggers

SGA Trace

SQL*Loader Wizard

Save As

Save As > XLS

Schema Browser

Schema Browser (SB)

Script Execution

Script Manager

Server Login

Session Browser

Set Parameters

Single Record View

Table Editor

Team Coding

Toad

Toad Advisor

Toolbars

Toolbars/Menus

User Editor

User Script

View Tablespace

Top

Enhancements in the Debugger

CodeXpert

Debugger

Watches

Top

DBA Module Enhancements

ADDM/AWR

DBMS Redefinition Wizard

Database Monitor

Database Probe

Export Wizard

Generate Schema Script

Health Check

Import Wizard

Oracle Parameters

Redo Log Manager

SB > Views

Tablespace Editor

Top Session Finder

UNIX Monitor

Top

Other Changes to Note

End Connection

Options

Options > Editors

Query Viewer

Schema Browser

Schema Browser (SB)

TNSNames Editor

Threaded Queries

Top

Bug Fixes

Alter Sequence

Alter Table window

Alter User

Auto Trace tab

Base

Bind Variables

Bind and Sub Variables in SE (Indiv. statement)

Bind and Substitution Variables (Indiv. statement)

Breakpoints

Code Snippets

CodeXpert

CodeXpert in PE and SE

Columns Tab

Common Create and Alter Components

Compare Files

Compare Schemas

Compare Schemas GUI

Compile

Create Database Link window

Create Menu

Create Queue Table

Create Script for Table

Create Snapshot

Create Synonym

Create Table Like

Create Table window

Create User

Create and Alter Table

Create or Alter View

DB Links

DB Menu: Commit

DB Menu: Export Source Code

DB Menu: Import Source Files

DB Menu: Import Table Data Wizard

DBA Menu

DBMS Output Debug Window

DBMS Output in SQL Editor

Data Duplicates

Data Grid

Data Grid: Blob Edit window

Data Grid: Find Value in Column

Data Grid: Single Record View

Data Tab in Schema Browser

Data tab in SQL Editor

Database Health Check

Database Health Check (DBA)

Database Menu: Create

Database Probe

Date/Time Window

Debugger

Describe

Describe (F4)

Edit Menu

Edit Menu: Replace

Editor

Editor Options

Editor Window: Column dropdown

Editor: Auto Trace Tab

Editor: Data Grid Tab

Editor: Execute

Editor: Explain Plan Tab

Editor: Load Object from Database

Editor: PL/SQL Debugger (Pro)

Editor: Script Engine

Editors Options

Excel Style Filter

Execute Generated Query

FTP

FTP Files

Favorites

File Menu

File Splitting

Filter Tables

Filter Views

Generate Schema Script

Import Table Data Wizard

Load Procedure from Database

Log Miner (DBA)

Make Code/Strip Code

Master/Detail Browser

Menus/Toolbars

Multiple Object Privileges

Network Window: Telnet

New Connection

ODAC integration

Object Search

Options

Oracle Options

Oracle Parser

PE Debugger: Ref Cursors

PE: Load Procedure from Database

PE: Navigator Panel

PL/SQL Profiling

Parameters Window (Debugger)

Partitions Tab on RHS

Print Grid (Old)

Proc Editor Debugger

Procedure Editor

Project Manager

Query Viewer

Query Viewer Tab

Queue Tables

Roles

SB Tables: Copy Data To Another Schema

SB Tables: Filter Tables

SB Tables: Generate Statement

SB Tables: RHS Columns Tab

SB Tables: RHS Data Tab

SB Tables: RHS Partitions Tab

SB: Constraints

SB: DB Links

SB: Functions

SB: Packages

SB: Procedures

SB: Queue Tables

SB: Roles

SB: Snapshots

SB: Synonyms

SB: Tables

SB: Types

SB: Users

SB: Views

SGA Trace/Optimization

SM: Print Model

SM: Save or Open Model

SM: Subqueries

SQL Command Recall

SQL Edit window

SQL Editor

SQL Editor - OLD

SQL Editor Desktop

SQL Editor Statement Execution

SQL Editor Toolbar

SQL Modeler

SQL*Loader Wizard

Save As

Schema Browser

Schema Browser Navigation

Schema Browser Tree View

Script Engine

Script Output tab

Server Login Window

Server Login: Connection Colors

Server Stats

Session Browser

Single Object Compare

Single Record View

Snapshot Log Script

Snapshot Script

Snapshots

Statement Execution

TKProf Interface

TNSNames Editor

TOAD

Tables

Tables Referential Tab

Tree View

Triggers

Triggers Tab on Tables RHS

Unix Monitor

User Script

Users

View Tablespace Multi-tabbed Window

Views

Watches

Windows Options

XML Editor for XMLType

eBiz Monitor

eBiz Reports

Known Issues

Top
WINDOWDESCRIPTIONWORKAROUND
CodeXpertSaving PL/SQL results to database may fail or save invalid data to database for invalid PL/SQL objects.To ensure PL/SQL results get saved to database correctly, verify the validity of all objects before CodeXpert is run.
CodeXpertSaving results to DB: When dealing with nested procedures, CodeXpert can only insert run data from procs one level deep.
DBMS OutputDBMS Output doesn't display in the DBMS Output sub tab or the DBMS Output window while debugging or executing pl/sql with debug.If DBMS Output is enabled in the Editor sub-tab or DBMS Output window, DBMS Output will not show while debugging or executing pl/sql in debug mode unless the following option is checked: View > Options > Debugger > "Enable DBMS Output before debug session"
Data Export"Create Insert for Selected Rows" and "Data Export" from the schema browser are giving the error "No exportable columns found" when "Return object names in lower case from selection windows and drag drop" is checked under Options > Editors.1. Uncheck that option
or
2. Right-click on the data grid and choose "Save As". Choose "Insert Statements". If you have selected multiple rows and want to only export those, then check "Selected rows only". If you want to put only certain columns in the Insert statements, then you will need to use the right-click "Select columns" function to choose the columns for the grid before going to "Save As"
or
3. If you just want to get INSERT statements for a lot of tables, go to Database > Export > Table Data
Data GridsData does not always display correctly when using an older Oracle Client on a newer Oracle Database.We strongly recommend using Oracle Clients equal to or greater than the Oracle Databases you are on to ensure data integrity.
Data GridsGrid scrolls horizontally back to focused cell when scrolling verticallySelect a cell in the visible part of the grid before scrolling vertically.
Data GridsPasting multiple rows of text into a cell will only register the first row of the data.Paste multiple rows of text into the text editor (popup editor) instead of into the grid cell.
Data GridsREF columns now show as "(REFERENCE)" in the grid instead of showing the object ID, but you can still double-click them to pop up a display of the object type that they point to.
Data GridsSome users have received the error "invalid rowid" when adding a row to a data gridThe error appears to be linked to the use of Oracle 7 client calls. You are using Oracle 7 client calls if either of the following is true:
1. "SQL*Net compatible Net8" is checked on your Server Login window
2. You are using an Oracle 7 client (Note that "Force SQL*Net" will force TOAD to select the Oracle client on your machine.)
We strongly recommend upgrading your Oracle client to at least the same version as the Oracle server that you are connecting to. We also recommend unchecking "SQL*Net compatible Net8" -- the only known advantage of using that setting with TOAD 7.5 is that for Oracle 8.0.x clients, it is the only way to get the error position in the SQL Editor
Data GridsYou may receive an "ORA-00902 invalid datatype" error when editing object, nested table, or varray data if you have redefined the data type for that data during the current session.If you redefine an object type, nested table, or varray and then need to edit data in a table based on that type, end your current connection and begin a new one.
Database ProbeDatabase Probe does not work with Oracle version 8.1.5.Upgrade to supported Oracle version 8.1.7
DebuggerThe debugger is not designed to work with word-wrapped lines, since the editor will then have a different set of line numbers than what is stored in Oracle.Toad provides a warning message about this if you open the procedure editor while word-wrapping is enabled. To disable word-wrap, go to Edit > Editor Options and uncheck "word wrap lines" under "General".
Editor"Capitalization Effects" applied from the language parser are not saved to file with the case applied by capitalization effects function.Type the code in the case desired, do not rely on the lexer to change the case of your code. Configure Toad's formatter (View menu > Formatting options) to change case as desired and format code before saving.
EditorIn an Oracle Apps environment, the default syntax highlighting options (options > Editors > General) can make the SQL Editor open very slowly.Go to Options > Editors > General and uncheck all of the options to highlight object names.
EditorOn an Oracle 8.0 client, if "Display large numbers in scientific notation" is unchecked, and the query contains a non-alphanumeric other than "*", the error "OCI-22061: invalid format text [TM9]" is returned.Either:
1. Check Options > Data Grid - Data > Display large numbers in scientific notation, or
2. Upgrade the Oracle client to at least Oracle 8.1.6
EditorThe procedure editor will jump to the wrong line number for PL/SQL Errors and debugging stepping if the name of the object is not on the same line as the CREATE OR REPLACEIf you add "PELineOffsetOverride=1" under the "[SETTINGS]" section in your Toad.ini, it should fix the offset problems, as long as the CREATE OR REPLACE is on the first line of the editor.
Formatter PlusAs long as the FmtPlus.dll exists in the TOAD directory, Toad will read its formatting options from there, even if there are other installations of Formatter Plus on the machineThis behavior is meant to ensure that the version of the FmtPlus.dll that Toad is loading will be high enough. If you have Formatter Plus version 1.4.0.6 (FmtPlus.dll version 4.8.0.23) or higher in another place on the machine and you would like Toad to use the options there, uninstall Formatter Plus from the Toad directory and manually delete the FmtPlus.dll from the Toad directory.
LogMinerYou may get the following error when moving from the first screen of the LogMiner to the second screen of the LogMiner:

17:46:25 Info: ORA-06532: Subscript outside of limit
ORA-06512: at "SYS.DBMS_LOGMNR_D", line 793
ORA-06512: at line 2

This results from an Oracle bug in 8.1.7.0.0 and 8.1.7.1.0.
Upgrade to Oracle version 8.1.7.2.0 or higher, or see Oracle Metalink Note:124671.1 for details of how to fix the package.
Multi-file Formatting ResultsAfter running a "Profile Code", "Check Syntax", or "Format Code" against files in the Project Manager, a results tab appears in the output window. Clicking on an occurrence node in the results tab will load the file in the appropriate Toad window. If you are loading a full package into the Procedure Editor in the manor and select "yes" to the Spec/Body file split prompt, your file will be split into 2 Procedure Editor tabs. At this point, selecting an occurrence node in the output window will only highlight the appropriate line in the Procedure Editor if the line is in the "Spec" tab. Clicking on an occurrence in the Body of the Package will always highlight the last line in the Spec tab.When loading a package into the procedure edit in this manor, select "no" to the Package spec/body split prompt.
Query Builder Reverse EngineeringThe Query Builder now supports, for the first time ever, the reverse engineering of queries. SQL Reverse Engineering represents a considerable technological advancement for the Builder. Although it was heavily tested throughout its development lifecycle, due to the vast array of possible queries there may be some queries it can create but cannot reverse. We encourage users to inform Quest if they discover such queries. The main limitations of reverse engineering are that it only supports single-level subqueries in the SELECT and WHERE nodes, and no subqueries in the FROM clause, and some calculated fields that include arithmetic operators might not be reversed correctly.
SB > ProcsSometimes on Oracle 8.1.7 or higher, after pressing "Compile invalid objects", you may get:
ORA-20000: You have insufficient privileges for an object in this schema.
ORA-06512: at "SYS.DBMS_UTILITY", line 282
ORA-06512: at line 1

This could mean that you really don't have the privileges to compile the object. But it also happens when the schema contains a package body that does not have an associated spec.
Look in the schema that you are trying to compile to see whether there are any orphan package bodies. If it is your own schema, then do:
select * from user_objects o1 where object_type = ''PACKAGE BODY'' and not exists (select ''x'' from user_objects o2 where o2.object_name = o1.object_name and o2.object_type = ''PACKAGE'') Then drop any orphan package bodies that are found.
SB > Tables > Data-Changing the order of the columns in the "View/edit query" popup does not change the order of the columns in the grid.
-Renaming a column in the "View/edit query" popup moves the renamed column one position to the left. The renamed column will not be editable.
Use drag-and-drop in the grid to change the column order.
SQL MonitorIn order to monitor services, you must run the SQL Monitor from one of your local drives. If you try to monitor a service while SQL Monitor is running on a mapped or network drive, you will get the message "Error installing monitor for the service process." This happens because services run under the "Local System" account, which can only see local drives.Install SQL Monitor on a local drive and run it from there.
SQL MonitorThe "Explain plan" options page describes SQL Monitor explain plan's limitations and potential side effects. Mainly, since SQL Monitor has to execute statements, it becomes proactive and can interfere with the program's execution flow. And since it executes statements, the statements may get into the SGA, and there is a remote possibility that they may affect the execution plan of the monitored application's statements. The only 100% guaranteed way of getting the execution plan that was actually used by Oracle for the statement is to turn on server-side tracing and get the plan from there. SQL Monitor is not guaranteed to display the plan that Oracle used, although it should be correct in most cases.
Save As > XLSExporting data grid cells of over 800 bytes (est.) could cause "OLE error 800A03EC" for Microsoft Office 2003 users when using the "XLS Instance" option.Save using the "XLS file" option instead
Script ManagerInstalled Script Manager files are not found in Citrix and Client/Server Environments.Toad installs packaged SQL Scripts with it's Script Manager. When Toad runs in a Citrix or Client/Server environment, the default paths to these script manager files will be pointing to the wrong place on the Server. These paths need to be changed to point to the client's files.

Every client user will have to manually change these paths 1 time. To change the paths, open File > Script Manager and Select the DBA category from the dropdown box. Click the move button and enter your new path, which will be "C:\Documents and Settings\User Name\Application Data\Quest Software\TOAD\ScriptMgr\DBA". Repeat for the "Schema Objects" category and move to "C:\Documents and Settings\User Name\Application Data\Quest Software\TOAD\ScriptMgr\Schema Objects".
Server LoginSelecting a new Oracle home in the ''Connect Using'' dropdown box does not guarantee that the correct home will be used. Switching between major Oracle client versions works correctly in Toad. Switching between patch or mid-release versions of Oracle will not always work. For example, switching from Oracle client 9.0.1.4 and Oracle 9.2.0.4 will not guarantee the correct Oracle home is used.To ensure the proper home is used while logging on, close TOAD use the Oracle Home Selector to select your home, and reload TOAD. Select the correct home in the ''Connect Using'' dropdown and login.
Session Browser"PLS-00553: character set name is not recognized" error encountered when opening Session BrowserWe received this when opening the Session Browser on a 9.0.1 database with a 7.3.4 client. We recommend always using a client version greater than or equal to the server version.
Session BrowserIn RAC databases, version 10.1.0.3 (and possibly other 10.1 versions), the query used to show the populate the "Current Statement" in the Session Browser fails with the following error:

Runtime error occurred: 12801 (ORA-12801: error signaled in parallel query server PZ99, instance
ORA-01008: not all variables bound)

This problem does not occur in Non-RAC environments.
Uncheck the "Use RAC Views" checkbox, and log into the appropriate instance of the database, if necessary.
Session BrowserSession Browser does not work with Oracle version 8.1.5Upgrade to supported Oracle version 8.1.7
Session BrowserThe Program name in the Session Browser may be blank or may be the full path to the executable instead of just the executable name. This depends on the Oracle client, not on Toad.
Snapshot ScriptIf you check "Indexes" on the Scripts tab for snapshots, then the primary key for the snapshot will be included in the script, even though the CREATE MATERIALIZED VIEW statement implicitly creates this primary key. We have not been able to determine a way to tell the difference between indexes explicitly created on the snapshot and indexes automatically created when the snapshot is created.If you are running the generated script to recreate the snapshot, then you can simply ignore the error that occurs when the script tries to re-create the primary key index for the snapshot.

If you do not normally create indexes on snapshots, then you can uncheck "Indexes" when generating the snapshot script.
Team CodingMost version control providers that integrate with Toad through the SCC API ignore the "Force revision" flag and the "Create a new revision for existing objects" option when exporting.
Team CodingTeam Coding and Clearcase: Dynamic Views are not supported via SCC interface. Snapshot Views must be used instead. (Rational case id v0830629, Rational Defect # CMBU00053934)
Team CodingTeam Coding and PVCS:

-Integration via the SCC API is available but not recommended for PVCS 6.6 and up.
-PVCS 6.6.1 is not supported. In testing, we were not able to get check in and check out to function properly. PVCS 6.6.0 and PVCS 6.7.0, however, worked correctly in testing.
-PVCS 6.8.0 is not supported because it has been found to cause a crash in Toad after about 5 to 15 minutes of use. We therefore recommend upgrading to PVCS 6.8.1, which does not have this problem.
-PVCS Version Manager 6.6 and above only supports "Tip Revisions" via the COM interface used by Toad. Attempting to retrieve a non-tip revision using the Version Control Browser will always return the latest revision. (Merant case id 1230782). This means that comparing revisions in the VCS Browser will fail because both versions will return the text of the latest version of the file.
-After connecting to a PVCS database, successive connections made during the same Toad session will always connect to the same PVCS database, even if a different database is specified in the "Logon to PVCS" dialog.
A work-around for this problem is to close and re-open TOAD before attempting to connect to a different PVCS database. If simultaneous connections to two different PVCS databases are required, this can be achieved by opening a second copy of TOAD.
Team CodingTeam Coding and SourceSafe:

-Integration via the SCC API is available but not recommended for SourceSafe 6.0
-SourceSafe 5.0 ignores the "Force revision" flag and ignores ''Create a new revision for existing objects'' option when exporting
Team CodingTeam Coding and StarTeam: If you cancel the login dialog for StarTeam, you will not be able to log in to StarTeam until you restart Toad.
Team CodingTeam Coding is disabled for mixed-case object names
Team CodingWhen you are using CVS as a version control provider, Toad may fail to retrieve the list of projects for you to select from, either in the VCS Browser or in Code Control Groups configuration. Toad determines which files and folders are in your CVS repository by reading the file named Entries. This normally resides in a folder named CVS under each of your working folders. If Toad cannot find this file in your top-level working folder, or if this file does not contain all the projects, then Toad cannot retrieve all the projects.

Please see the "Missing CVS\Entries File Error" topic in Help for details about how to create the Entries file.
Team CodingWhen you log into CVS from within Toad, Toad opens a command prompt window to send the password to the CVS server. Sometimes, the command prompt window opens in the background instead of the foreground, and this causes the login to fail. When this happens, the user needs to select "Log in to VCS Provider" from the Team Coding menu or toolbar to re-do the login. The second attempt invariably succeeds.
Toad HelpToad Help file no longer opens for Network installs. Microsoft security update 896358 disables ActiveX Components, which renders the Toad help file useless for network installs.Copy the Toad help file (Toad.chm) from the server to the client and change the following Toad.ini (located in main toad directory under the "User Files" folder) entry to point to the new location:

[SETTINGS]
HelpFileDir=C:\Program Files\Quest Software\Toad for Oracle 8.6 Client
UnicodeToad's data layer does not support UTF8 / Unicode data. Most non-ASCII characters will display as question marks in the data grid and should not produce any conversion errors except in TOAD Reports. TOAD Reports will produce errors and will not run on UTF8 / Unicode databases. It is therefore not advisable to edit non-ASCII Unicode data in Toad's data grids. Also, some users are still receiving "ORA-01026: multiple buffers of size > 4000 in the bind list" messages, which also seem to be related to Unicode data.
XML Editor"ORA-31001: Invalid resource handle or path name "%s" when trying to post XMLType data that points to a document type definition stored in the XML repository. Even though an insert statement with the same data may work, there appear to be problems with posting these items from the XML editor. We do not really have a workaround for this. But note that XMLType data that uses a registered XMLSchema for validation seems to post successfully. Also, XMLType data with an inline document type definition also seems to post successfully.
XML EditorAn extra newline gets added to the value for a mixed-content node when the XML is stored as XMLSchema. A mixed-content node is a node that has a value as well as subnodes.

For example, this:
<node1>value1<subnode1/></node1>

Returns exactly the same when it is in a CLOB or in an XMLType stored as CLOB:
<node1>value1<subnode1/></node1>

But, when it is in an XMLType stored as XMLSchema, it returns from Oracle to TOAD like this:
<node1>value1
  <subnode1/>
</node1>

As you can see, an extra newline appeared after value1. When TOAD posts altered data back to Oracle, that extra newline is posted along with the data (unless you manually eliminate it), and when TOAD then retrieves the data again, Oracle has added another newline:

<node1>value1

  <subnode1/>
</node1>
If you wish to use TOAD's XML editor with mixed-content nodes in an XMLType stored as XMLSchema, then any code you use for parsing will need to be insensitive to newlines at the end of values.
XML EditorThe XML Editor has been tested successfully with the following combinations:
-Oracle 9.2.0.4 database with 9.2.0.4 client
-Oracle 9.2.0.5 database with 9.2.0.5 client
-Oracle 10g database with Oracle 10g client
-Oracle 10gR2 database with Oracle 10gR2 client

Some errors in other configurations:
With an Oracle 9.0.1 client and any server, XMLType columns will show up as "(ADT)" and be unreadable.
With an Oracle 9.2.0.5 client and a 9.0.1 or 9.2.0.1 server, small XMLTypes seem to work, but trying to post an XML over 4000 bytes to a Unicode database yields "ORA-31011: XML parsing failed" even if the data is all English
With an Oracle 9.2.0.1 client and a 9.2.0.4 server, attempting to post data causes "two-task conversion" errors or "ORA-31011: XML parsing failed" errors.
With an Oracle 10g client and a 9.2.0.5 database, XMLType data shows in the editor as a long string of question marks.

These errors seem to be a result of errors occurring at the Oracle client level, which we cannot control.

Global Operation Statement

Top

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 supports any single-byte character set. Double-byte or multi-byte character sets are not supported. 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, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: Updating multi-byte or bidirectional character data, exporting multi-byte character data to excel. Visual display in some grids/views.


Release Statistics
Number of Bugs Fixed337
Number of Enhancements151
Number of Known Issues45