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

Toad 8.5.3 Release Notes

LAST REVISED: 06-JULY-05

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 summary of new features, also see the "What's New" topic in the Toad help file. For an introduction to Toad, please see TOAD Getting Started Guide.pdf located in the 'docs' folder.

Toad for Oracle 8.5 extends the 10g support introduced in the previous release of Toad. New 10g support includes the 10g Instant Client (Toad 8.0 supports Instant Client from the Oracle installer but does not support the stand-alone Instant Client); Browser filter options to exclude recycle bin objects from lists; Global hash partitioned indexes; more datatype and SQL Statement support; and a drop table PURGE option. In addition, Toad DBA module exposes new Oracle 10g features by offering new utilities such as Data Pump (also available in Toad Professional), Segment Advisor, Undo Advisor, Index Monitoring (9i feature), and 10g Scheduling.

Other significant features now offered in Toad for Oracle Standard 8.5 include Terminal Server and Citrix support, Secure Shell support for all of Toad's monitoring and FTP capabilities, a redesigned SQL Editor, RAC support (included in both DBA and non-DBA windows), true threaded query support with the ability to view queries running in Toad, re-designed SQL Recall, and Integrated Windows Task Scheduler with the ability to schedule through many Toad windows.

Toad Professional and Xpert editions now offer more functionality in the CodeXpert Utility. CodeXpert now appears as a sub tab in both the SQL Editor and the Procedure Editor for Toad Professional users. CodeXpert analyzes PL/SQL and now SQL statements against an updated set of rules for best practices. In addition, Toad Xpert Edition users will have the ability to scan the SQL code for inefficient statements that are either problematic or complex, and which should be reviewed further in the SQL Tuning interface. Other Toad Professional enhancements include the Export File Browser (also included with DBA module), Just-in-time Debugging (also known as "External debugging") in the Procedure Editor, and Step-in Debugging has been added for debugging SQL scripts in Toad's redesigned SQL Editor.

Top

Patch Information

TOAD version 8.5.3 is provided as a patch with selected fixes to version 8.5. This patch version is not intended to address all reported issues. Rather, it addresses a subset of the issues, selected based on severity and complexity.

Top
Fixes in 8.5.1
WINDOW DESCRIPTION
Browser Filters User Status filters not working for < 10g DB.
Create DB Link Remove quotes from fields, but still allow manual entry.
Create Index Can't create Local Index on Hash partitioned table on non 10g DB.
Describe Can't describe package across DB link. Add support for lower case named DB Links.
File - End All Connections Access Violation when connected to 3 databases and have Procedure Editors open
Installer The default install directory has changed, detection code needed to locate previous Toad install.
Options F1 lookup disabled for SQL Editor > SQL Recall.
Procedure Editor Static methods don't show in navigator.
Procedure Editor Re-validate object owner on compile.
Procedure Editor Always include the schema name in the execution or debugging session generated anonymous block, independent of the "Procedure Editor - General - Include Owner when extracting source from database" option.
Procedure Editor Exception Eureka Log when saving to non-existent directory.
Procedure Editor Blank error message during debugging session.
Save As Detection code needed to check if file is opened.
Script Engine NO_DATA_FOUND PL/SQL Exception is not being raised.
Session Browser - Locks - Blocking Locks Field 'SQL_Test' not found error.
Single Record View Viewing single record view after running this query produces error: "select chr(13) || chr(10) from dual;".
SQL Command Recall Truncation after 5K and editor contents are being loading from grid, instead of file.
SQL Editor Ctrl/Alt + Up/Down to recall SQL history and overwriting editor contents can't be undone.
SQL Editor Caret position jumping to first character in statement.
SQL Editor Script Output Ctrl+A is non-functional in Script Output tab.
SQL Modeler AutoTrace tab is non-functional.
Threaded Queries DBMS Output is not displayed in the DBMS_OUTPUT window or the SQL Editor tab when Threaded Queries option enabled.
Threaded Queries Auto Commit on: No message to post outstanding transactions when a Commit is performed manually.
Threaded Queries Auto-commit is not committing after record deletions in data grid.
Toad Profiler Error: "PLS-00201: identifier 'TOAD.TOAD_PROFILER' must be declared" when Profiler installed in non-Toad schema.
Trigger Editor Comments being forced to UPPERCASE in some cases.
Top
Fixes in 8.5.3
WINDOW DESCRIPTION
ConnectUnable to connect to 64Bit Oracle instances, errors out with "Connections to Oracle 7 require Oracle 8.1.7 clients or older"
Connect10g instant client does not work if its is the only client installed
Procedure Editor/Schema BrowserWhen running Toad with multiple connections, Toad may execute a PL/SQL Object in the wrong connection. If using the debugger module, the PE lightening bolt will work, but right click "execute outside debugger" will not. If not using the debugger module, the lightening bolt in the PE will execute in wrong schema as well. Executing via the PM will also fail.
Procedure Editor/Schema BrowserWhen loading Triggers into the Procedure Editor, Toad will prefix the schema name twice if the schema name is in the DESCRIPTION column in dba_triggers.
Top

Important Installation and Upgrade Information

ITEMDETAILS
Microsoft Excel SupportExcel '97 is no longer supported as of TOAD 7.6. This desupport applies to importing/exporting data through TOAD.
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.
SQL Editor Script OptionsThe Toad script options have been removed. 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.
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.
Script Debugger/SQL Editor MergeThe SQL Editor has been merged with the Script Debugger. Script Debugging functionality will only be available for those users who have purchased the debugger license. The only available item on the Script Debugger for those without the Debugger license, will be the "Execute as Script" (lightning bolt) button.

Since the SQL Editor now combines SQL editing/execution with script execution/debugging, you will encounter several shortcut conflicts if you are upgrading. For instance, F8 was for "Step over" in the script debugger, and launched the SQL Recall Window from the SQL Editor. As a result, you will need to right click on the main Toad toolbar and choose "Menu Shortcuts". From there, you can adjust any conflicts as necessary to best fit your working environment, or reset defaults. If you are not upgrading, then you will not encounter shortcut conflicts.

The SQL Editor script engine used in previous version of Toad has been removed in favor of an updated script engine used in the old Script Debugger. Since the new script engine conforms to the SQL*Plus standard, you may need to modify some scripts that utilized non-standard aspects of the old Toad script engine.

Examples:

- SQL statements should be terminated with a semi-colon, anonymous blocks and create function or package calls should be terminated with a newline slash.

- the old Toad script engine had different variable scoping rules applying to substitution variables named like &1 and &2. Avoid numeric substitution variables unless you are referring to script arguments.

- "Set Maxrows" is an example of a non-standard, Toad-specific command used by the old script engine. This command will no longer work in the new script engine
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.
Set Table Alias in SQL ModelerSince the table selector window has been replaced with the Object Palette window (View > Object Palette) for Toad 8.0, the ability to add an alias from the table select window has been removed as well. You can still set a table alias by right-clicking on the table after it has been added to the table model area, and selecting 'Set Table Alias...'.
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:
Team CodingIf you plan to use Team Coding, we strongly recommend that you check Options > Procedure Editor > General > 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.
Threaded QueriesSQL 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.
ToolbarsToad's pre-packaged toolbar templates have been depreciated. 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.
Top

Windows Removed from Toad

NT Scheduler

NT Scheduler used for the "Schedule to run later" option in the Import/Export Utilities and SQL*Loader Wizard has been removed in favor of the "Task Scheduler"

Script Debugger

The Script Debugger window has been removed. All functionality previously available in the Script Debugger window is now available in the SQL Editor.

View Constraints

View Constraints window, previously accessible from the "View" menu, has been removed. The same functionality can be found in the Schema Browser "Views" tab.

Top

Enhancements

Enhancements for Base Toad

Browser Filters

Connection Task Bar

Data Grids

Database Browser

End Connection

Export Grants

FTP

HTML Schema Doc Generator

Import Table Data

Master/Detail Browser

Multiple Object Privileges

Options

Options > Editors

Options > Toolbars/Menus

Output Window

Pinned Code

Procedure Editor

Project Manager

Query Viewer

Rebuild Multiple Objects

SB > DB Links

SB > Filters

SB > Indexes > Stats/Size

SB > Jobs

SB > Procs

SB > Queues

SB > Snapshot Logs

SB > Snapshots

SB > Snapshots > Indexes

SB > Synonyms

SB > Tables

SB > Tables > Data

SB > Tables > Estimate Stats

SB > Tables > Indexes

SB > Triggers

SB > Types

SB > Users

SB > Users > Grants

SQL Editor

SQL Recall

Save As

Schema Browser

Script Manager

Server Login

Session Browser

Single Object Comparison

Single Record View

Table Editor

Table Script

Task Scheduler

Taskbar

Team Coding

Toad

User Editor

View Tablespace > Objects

Top

Enhancements in the Debugger

Export File Browser

Procedure Editor

SB > Procs

SQL Editor

Top

DBA Module Enhancements

Audit Objects

Data Pump Export Wizard

Data Pump Import Wizard

Data Pump Job Manager

Database Browser

Database Monitor

Database Probe

Export File Browser

Generate Database Script

Generate Schema Script

Health Check

Index Monitoring

Log Switch Frequency Map

Oracle Parameters

SB > DB Links

SB > Sched. Job Classes

SB > Sched. Jobs

SB > Sched. Programs

SB > Sched. Schedules

SB > Sched. Window Groups

SB > Sched. Windows

SB > Tablespaces

SB > Tablespaces > Extents

SB > Tablespaces > Objects

SGA Trace

Segment Advisor

Threaded Queries Viewer

Top Session Finder

Undo Advisor

View Tablespace > Objects

Top

Other Changes to Note

Code Snippets

Project Manager

SB > Snapshot Logs

SB > Tables

SQL Editor

Schema Browser

Script Manager

Server Login

Session Info

Top

Bug Fixes

Alter Table window

Analyze all Objects

Base

Compare Schemas

Compile

Copy Data To Another Schema

Create Index window

Create Script for Table

Create User

DBA Menu

Data Grid

Data Subset Wizard

Data Tab in Schema Browser

Data tab for Views

Datatypes Options

Debugger

Describe

Editor Options

Excel Style Filter

Export Table Data

Export Wizard

Favorites

File Menu

Generate Database Script

Grid Menu

HTML Schema Doc Generator

Import Source Files

Import Table Data Wizard

Indexes

Indexes Tab on Tables RHS

Log Miner

Master/Detail Browser

Memo editor

Menu/Toolbar Rewrite

New Connection

New Data Grid

ODAC integration

Object Search

Parameters Window (Debugger)

Print Grid (New)

Procs

Project Manager

Queue Tables

Replace

SQL Edit window

SQL Editor

SQL Modeler

SQL*Loader Wizard

Save As

Schema Browser

Script Engine

Session Browser

Snapshot Script

Startup Options

TNSNames Editor

TOAD Reports

Tables

Tables Referential Tab

Tablespace Map

Triggers Tab on Tables RHS

Types

View Tablespace Multi-tabbed Window

View Tablespaces

Views

Watches

Known Issues

Top
WINDOWDESCRIPTIONWORKAROUND
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
DebuggerCan't watch record declared in package body on Watches tabHover the mouse over the name of the record variable to watch the values
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".
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.
Procedure 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.
Project ManagerAfter 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 editor in this manner, select "no" to the Package spec/body split prompt.
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 EditorCannot close Script Output panel in Script Debugger.
SQL 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
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.
SQL TuningToad Xpert Edition is now supplied with a new in-process SQL Tuning component. This component relies on Microsoft's XML Parser. If the XML Parser is not installed on the client PC, then Toad will return a message "SQL Tuning cannot be found" or "class not registered".The parser can be downloaded and installed from Microsoft to resolve this issue.
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 Manager in Citrix EnvironmentInstalled Script Manager files are not found in a Citrix EnvironmentToad installs packaged SQL Scripts with it's Script Manager. When Toad runs in a Citrix 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 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.
Source ControlLegacy Source Control does not support Merrant Version Manager 8.0 and higher.
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.
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

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.

Release Statistics
Number of Bugs Fixed109
Number of Enhancements171
Number of Known Issues39