Quest® Toad for Oracle

Version 10

Release Notes

September 8, 2009


Contents

Welcome to Toad for Oracle

New in this Release

Resolved Issues and Enhancements

Known Issues and Deprecated Items

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

For More Information


Welcome to Toad for Oracle

These release notes are intended to provide an overview of functionality and known issues in the current release (10.0).

This release has several changes in functionality, not least of which is Unicode support. Please carefully review the New in this Release section and the Known Issues section to see the changes. For additional information about Toad and how to use it, see the built-in Help (from within Toad press F1).

This page provides a quick overview of some of the features introduced in Toad® for Oracle 10. Links to video walk-throughs are provided where available. In addition, new videos are often being added to the Video Page at Toadworld where you can also find videos from previous versions. You can find details of the various Toad Editions and additional products included in them at Quest Software's Toad for Oracle product page.


New in Version 10

In All Toad Editions

Unicode Support Actions

Alter Type

Altering a Type in the Schema Browser now loads the object in the Editor.

Application Data Folders

Editor ER Diagram

In addition to the following information, there is an online video tutorial for this feature. This video opens in a new browser window and requires an internet connection.

Grids

In addition to this information, there is also an online video for this feature. This video opens in a new browser window and requires an internet connection.

Licensing structure

  • The licensing structure has been changed to support one key for all products in a Toad Edition. If you are upgrading your version of Toad, old license keys are still supported.

Load Database Object

Network Connection Info

  • Now stored in NetworkConnections.dat rather than Toad.ini. It is also encrypted using the same method as the connection information, and tied to the logged in user.

Profiler Analysis

Project Manager Rebuild Table Script Manager Search Functionality Server Side Objects Wizard Set Sequence TNS Names Editor

An online video tutorial is also available for this feature. This video opens in a new browser window and requires an internet connection.

User Data - Copy on Upgrade

A new migration tab is added to the initial startup wizard to copy your existing application data from a previous installation of Toad. Upon startup, Toad will attempt to detect the application data paths of previously installed versions. If one is found, it will select the most recent installed version and give you the option of migrating data files from that installation to the current installation. It will also provide the option of specifying a custom location, or the option to skip the migration and perform a clean install.

Variables

In the Professional, Xpert, Development Suite, and DBA Suite Editions

Code Xpert Data Generation

In the DB Admin Module and DBA Suite

Database Browser Database Health Check Database Monitor Instance Manager Options

Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of Toad for Oracle.

 

Feature

Resolved Issue

Defect ID

AppDesigner

File Iterator cannot accept a directory path that contains any spacing. CR#59274
Schema Compare maxes out at 500 differences. Setting cannot be changed for action. CR#58355
Option to suppress importing window when running silently added. CR#60220
Setting "multiple copies loaded" not saved. CR#61690
"Interface not supported" error in Windows Vista when scheduling a job. CR#60765
Load Action in Health Check causes access violation when saving a job. CR#55910

AWR Browser

AWR Browser does not show correct statistics on RAC. CR#59674

CodeXpert

CRUD matrix and Code metrics reports do not run on CITRIX installation. CR#56981
CodeXpert utility gives incorrect result analysis. CR#58603
Cannot run command-line CodeXpert for any package on any schema. CR#59107
Compare Schemas SchemaCompare sync script issue in 9.6.1 (ASCII at end of sync file.). CR#58854
Problems with Sync script created from compare (constraint added twice). CR#59861
Generates extra synonym statements. CR#60561
Sync script doesn't generate crorrect code for Revoke References command. CR#62278
Incorrect syntax from Schema Compare when altering primary key. CR#61537
Incorrect SQL shown in Show Differences Details window CR#62934
Does not reflect Storage Clause Options Tab selections CR#65343
Unable to generate difference script for materialized view. CR#62078
Compare Single Objects Toad closes if you have two compare objects windows open and you close them. CR#56548
Connection 11G instant client support. CR#56585
Connecting to RDB database with Oracle Emulatuion. CR#56075
Identifier 'QU_VERSION.MAJOR_NUMBER' must be declared. CR#57192
Cannot connect to RDB database with Oracle Emulation. CR#59845
Debugger error on RAC database due to commented lines in SQLNet.ora. CR#61261
Home Editor showing "not valid" when using ODT.NET 11g client. CR#64567
SERVICE_NAME not generated in the connect string for Direct connection method. CR#56729

Constraints

Access Violation error when generating script for a Constraint in Schema Browser. CR#57213
Access Violation when looking at the Script of a Not Null Constraint. CR#58113
Access Violation at address 01310E77, read of address 0000002C when creating a script in Schema Browser|Constraints|<right click> Create Script. CR#58350

Database Browser

Database Browser closes when disconnecting from menu. CR#57598

Database Probe

Database probe query does not include the selected optimizer hint. CR#60388
Data Generation

 

Generate Data feature causes Toad to close without error or message. CR#58918
Toad disappears with Show SQL CR#65619

Data Grids

Data grids containing data fron an ANYDATA column cause Access Violation. CR#56096
Export date to Excel 2007 does not draw borders. CR#56062
Page size is reset after re-starting TOAD. CR#56920
Error Excel Instance Export w/ "Start at Active Cell" is enabled. CR#58179
Scrolling right in data grid causes Access Violation. CR#59851
Delete key does not work in Save Grid Contents inside the Output File text box. CR#57013
Added ability to select and copy multiple records in one column. CR#61448
When sorting grid, do not make nulls either first OR last. CR#63065

Toad Grid INSERT fails with a table names & columns named after reserved words

(TYPE,REM and so on).

CR#57121
Not able to edit TYPE columns in Database Browser Data Tab. CR#56489
"Export to files named for the value in this column" the dropdown list is empty. CR#64800
"Connect by" query does not produce all Data Grid rows as expected with F9. CR#61348

DB Links

DBLink error in Schema Browser|Alter Materialized View. CR#60115
Error ORA-06502 in Schema Browser|DB Link|Used by tab - for large sized Materialized views. CR#60076

Editor

Schema Browser auto-openAuto-open bring to front - the drop down lists everything but should only reflect the ones that are set to "auto open" and should be disabled if none are choosen. CR#58469
Comment code only comments every second line. CR#65485
Cannot CTRL+Left click on Types (object) in Editor to bring up code. CR#59865

ER Diagram

ER Diagram not saving table formatting and position correctly. CR#57191
Better illustrate compound foreign key relationships in modeling area. CR#57452
Allow opening of the ER Diagram tool without a DB connection. CR#57447
When working on a diagram, and saved as a new filename, the old filename is still shown in title bar. CR#62522
Workspace format checkboxes not being saved. CR#62523
Option in workspace (object) format to display or hide schema name (fullname) in caption of DB object on workspace CR#61788
Added Select All option to popup menu in workspace CR#61786
After applying filter (Select objects) display focus on the first row in grid which is checked by the filter. CR#61787
Metadata in the Model Title should be editable. CR#61758
Explain Plan Tab Explain plan prints with black background. CR#60227
Wrong value in COST CR#62589
Explain plan does not show correct partition information. CR#58584
Export DDL Toad hash table DDL does not show LOB tablespace CR#61953
Toad exports bad DDL when last line of an object is a comment. CR#61946
Export File Browser PB in script generated by "Export File Browser". CR#57432

Export Utility Wizard

Doing a Save AS for two tables shows wrong table count. CR#56673
Flashback Archives Flashback archive causes an Access Violation in Oracle 11g. CR#60653
Generate Schema Script

 

Problem with the output files extensions in Database|Export|Generate Schema Script. CR#59636
Filtering causes issues with materialized views. CR#59837
Materialized View using "ON PREBUILT TABLE", table script not exported. CR#61415
Sort foreign keys in create schema script alphabetically if possible. CR#57033
Health Check

 

Additional information added in Healthcheck report screen. CR#57613
Access violation at address 00730060 running DB Health Check in 8i. CR#58083
Health check hanging when option "List unique keys with one or more nullable columns" is selected. CR#59862

Installation

License key is not working. The "OK" button is disabled when using OVCM to deploy Toad.

CR#58251

Instance Manager Instance Manager does not list all Server names. CR#57037

Jobs

ORA-27488: unable to set START_DATE because SCHEDULE_NAME was already set. CR#57042
ORA-27488: unable to set START_DATE because SCHEDULE_NAME was/were already set. CR#57042
Alter job generates incorrect SQL. CR#57160
Wrong Arguments Passed to DBMS_IJOB.INTERVAL. CR#57057

Materialized Views

Materialize view "Refresh Info" tab has sub-option checked. CR#55869
Choosing Date grays out Time field in Refresh Info tab. CR#55853
Duplicates in materialized view logs (differing from the DBA_MVIEW_LOGS). CR#57374
Problems Handling and display of Refresh Info' tab for Materialized View. CR#56639
Refresh Info tab has sub-option checked. CR#59840
Choosing Date disables Time field in Refresh Info tab. CR#59839
Need option set to create key and index together. CR#61831
Materialized view script missing WITHOUT parameter. CR#62426

Materialized View Logs

Incorrect Syntax when altering materialized view referring to a table in another database. CR#62530

Object Search

LIKE/INSR internal inconsistency in Object Search. CR#61435
Object Search clears search term and searches for blank/null. CR#61698

Options

Set DEFINE OFF to work in the login/glogin scripts. CR#60756

PL/SQL Debugger

Debugger Hangs with code that raises application error and/or the halt is used. CR#56906
"Set break on exceptions to false" causes debugger to hang in 11g. CR#60563

Procedures-Packages-Functions

Schema Browser filter errors. CR#56814
Profiler Analysis DBMS Profiler Analysis does not filter. CR#64564

Query Builder

Query Builder forces a re-run of the query when switching between tabs. CR#56821
Report Query Builder sample value American Date format inserts incorrectly. CR#56658
Reports Manager Reports disappear in grid. CR#64090

Roles

Standard license key removes the "create script" item in Roles tab. CR#55853

Scheduler Chains

Sched. Chains - "Used by" not filtered by owner. CR#59098
Scheduler Jobs DBMS_SCHEDULER request addition of Attribute 'MAX_RUN_DURATION' CR#66273
Run Log has a refresh issue. CR#56625
Schema Browser Clicking on package body causes Toad to crash CR#56581
Script Output Saving as Insert Statements leaves off last row. CR#59637

Script Debugger

Terminate execution button while debugging a proc in 11g DB will freeze Toad. CR#56991

Script Execution (F5)

Am/pm indicator wrong after setting nls_date_format running F5. CR#55856
SET Serveroutput on Size UNLIMITED using 10.2 database does not run in Toad. CR#56654
Script errors in German environment. ORA-01722 Invalid number error created. CR#56999
Executing scripts with 30,000 plus lines of code results in AV CR#66372
Leading zero minute digit dropped in date values when using F5. CR#58013

Set Parameters Window

Set parameters window does not update Code window with entered variable values. CR#60504

SGA Trace Optimization

"Skip check for debug" unselected causes issues in Schema Browser. CR#57288

StatsPack Browser

Error creating a new snapshot and selecting session ID. CR#61911

Tables

Toad's table DDL does not show VARRAY information CR# 56763
Toad-Generated table script for Oracle Spatial Table raises an ORA-22917 error. CR#63215
Problem editing data when partitions selected in the filter window. CR#62254
Securefile usage in script tab. CR#61954
Scheduled Analyze table tasks not working. CR#56166
Toad is hanging in SB after a WHERE and consecutive FILTER additions. CR#59608
Scheduled Analyze table tasks created and fails immediately in 9.7. CR#59844
Storage for LOB Index in create table script incorrect. CR#59842
Split partition is missing "update global indexes" clause from the update script. CR#64554
Insufficient Privileges error using Copy Data to Another Schema feature. CR#60896
Error inserting a record when in Schema Browser when username contains "." CR#65364
Partitioned Table Script DDL incorrect CR#65348
Problem generating sub-partitioned tables CR#56594
Triggers in scripts missing if they belong to a different schema when creating a Table CR#56432
Schema Browser Interface defect - anwering NO to "exit without saving?" loses changes. CR#61835
Tablespace Scripts generated by Toad don't have tablespace for XMLTYPE. CR#59843
Team Coding and Source Control VCS login window not masking password. CR#59853
Support for VSS 8.0 added. CR#57723
No support for objects with spaces in the name CR#57085

TNSNames Editor

TNS NAMES deletion features added. CR#59274
Trace File Browser

 

"Null" doesn't show up for Trace File Browser under SQL statement tab. CR#64552
Reports wrong "rows processed". CR#64054
Users Inconsistencies with " " when creating passwords. CR#60315
Toad not placing double quotes around profile value. CR#60316
Types Right-click Option to create Object and Collection Types incorrect. CR#56625
UNIX Job Scheduler Export Schema script is not removing old exports. CR#57044
UNIX Monitor Get "Key validation handler is not assigned" message connecting / UNIX monitor. CR#57277

Known Issues and Deprecated Items

The following is a list of issues known to exist at the time of this Toad for Oracle release.

 

Feature

Known Issue

Defect ID

11g Oracle ODP.NET Client

When using an 11g Oracle ODP.NET client, (located here: http://www.oracle.com/technology/tech/windows/odpnet/index.html), or any client in which the oci.dll is not in the client's BIN directory, but the directory above, Toad has these problems:

  1. Shows the client as invalid
  2. Cannot detect the client version
  3. As a result of (2), columns of the following datatypes are not shown in SB-Tables-Data: CLOB, BLOB, NCLOB, XMLTYPE, TIMESTAMP, INTERVAL, BINARY_DOUBLE, and BINARY_FLOAT.

Work around: Copy oci.dll and oraociei11.dll from <oracle client directory> to <oracle client directory>\bin\.

 
CodeXpert Saving results to DB: When dealing with nested procedures, CodeXpert can only insert run data from procs one level deep.  

Saving PL/SQL results to database may fail or save invalid data to database for invalid PL/SQL objects.

Work around: To ensure PL/SQL results get saved to database correctly, verify the validity of all objects before CodeXpert is run.

 
DBMS Output

DBMS Output doesn't display in the DBMS Output sub tab or the DBMS Output window while debugging or executing pl/sql with debug.

Work around:

  • 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"
 
Database | Import | Import Source Files Deprecated.  
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.

Work around:

  • Uncheck that option.
  • 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".
  • If you just want to get INSERT statements for a lot of tables, go to Database > Export > Table Data.
 
Data Grids

Some users have received the error "invalid rowid" when adding a row to a data grid. Work around:

  • The 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 does not always display correctly when using an older Oracle Client on a newer Oracle Database. Workaround:

  • We strongly recommend using Oracle Clients equal to or greater than the Oracle Databases you are on to ensure data integrity.
 

You 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. Workaround:

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

Pasting multiple rows of text into a cell will only register the first row of the data. Workaround:

  • Paste multiple rows of text into the text editor (popup editor) instead of into the grid cell.
 
Database Probe

Database Probe does not work with Oracle version 8.1.5. Workaround:

  • Upgrade to supported Oracle version 8.1.7
 
Debugger

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

Viewing XML_TYPE data in the F4 describe window may cause memory leaks.

  • Try to limit the amount of times the describe window is used to view XML_TYPE data during a given Toad session. Use the Editor or Schema Browser data grid to do the majority of your work with XML data
 
Editor

Toad error when query ona field of Oracle collection types.

Workaround:

  • Execute using SQL*Plus.
CR#64373

On 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
 

The 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 REPLACE

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

Parameter hints for overloaded packages are no longer scrollable. The parameter hint will be limited to the size of your screen

 
Editor (F9 Execution)

Bind Variables named "n" cause ORA-01036 using a 10g client.

Work-arounds:

  • Do not use "n" as a bind variable
  • Use something other than a 10g client
CR# 64568
Formatting Tools: Profile Code Count for lines of code and blank lines not always accurate.  
Install/Uninstall

If uninstalling Toad for Oracle 9.7 on Windows Vista using an extracted msi installer (silent install) while UAC is on, Error 1721 will occur. In this case, Toad will uninstall, but application data files and some registry keys will not be removed. Workaround:

  • Turn UAC (User account control) off, or double click on "uninstall.exe" located in the Toad installation directory prior to uninstall. This will ensure all application data files/folders and registry keys are removed. If this error has already been encountered, the best course of action is to re-install Toad back into the same directory where it was installed before, follow the work-around, then uninstall.
 
Drop Tables Incremental drop removed.  
JDWP Debugger Attempting to Halt debugging on Oracle 10g or above causes Toad to hang.  
LDAP Support

While Toad supports LDAP connectivity, some features of Toad depend on tnsnames.ora file to operate correctly. These features include but may not be limited to Quest Script Runner, Database Browser, and Service Manager.

 
LogMiner

You 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. Workaround:

  • 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 Results

After running a "Profilce Code", "Check Syntax", or "Format Code" against files in the Project Manager, a results tab appears in the output window. Clicking on an occurence 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 occurence 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 occurence in the Body of the Package will always highlight the last line in the Spec tab. Workaround:

  • When loading a package into the procedure edit in this manor, select "no" to the Package spec/body split prompt.
 
QueryBuilder Reverse Engineering

The Query Builder supports 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.

 
Right-to-Left Languages

With official support of Unicode may come the increased use of Right to Left (RTL) languages such as Hebrew, Arabic and Farsi. RTL is a topic separate from Unicode and was given very limited research for this release.

We hope to examine RTL support in greater depth for 10.1.

 
SB | Procs

Sometimes 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. Workaround:

  • 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. Workaround:

  • Use drag-and-drop in the grid to change the column order.
 
SQL Monitor The "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.  

In 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. Workaround:

  • Install SQL Monitor on a local drive and run it from there.
 
Export Dataset | XLS

Exporting data grid cells of over 800 bytes (est.) could cause "OLE error 800A03EC" for Microsoft Office 2003 users when using the "XLS Instance" option. Workaround:

  • Save using the "XLS file" option instead
 
Server Login

Selecting 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. Workaround:

  • 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

Session Browser does not work with Oracle version 8.1.5. Workaround:

  • Upgrade to supported Oracle version 8.1.7
 
The 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.  

In 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 <instance name> ORA-01008: not all variables bound) This problem does not occur in Non-RAC environments. Workaround:

  • Uncheck the "Use RAC Views" checkbox, and log into the appropriate instance of the database, if necessary.
 

"PLS-00553: character set name is not recognized" error encountered when opening Session Browser.

  • We 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.
 
Snapshot Script

If 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. Workaround:

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 Coding Team Coding is disabled for mixed-case object names  
Team 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 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  
When 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.  

Team 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. Workaround:

  • 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 Coding and Clearcase: Dynamic Views are not supported via SCC interface. Snapshot Views must be used instead. (Rational case id v0830629, Rational Defect # CMBU00053934)  
Most 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.  
Toolbars - customizing When customizing a menu or toolbar, items are not immediately displayed in the [Unused] list of the Customize form. You must close the window and then reopen it in order to see the removed items.  
XML Editor Removed due to an OCI bug preventing editing of XML data. Add an external XML editor from Options | Executables.  
Unicode Issues and Unsupported Features  
ASM Manager Does not support Unicode.  
CodeXpert Does not support Unicode.  
Connections Connections to Service Names with Unicode Characters are not not supported.  
DB Link Names Oracle does not support Unicode in DB link names.  
Directories Oracle directory objects can have names containing Unicode characters, but the directory path cannot contain Unicode characters.  Oracle allows such a directory to be created, but errors occur if you try to read from or write to it.  
Editor

The Editor has an inability to fully handle Unicode words. Issues relating to this include:

  • Highlight object names not working
  • CTRL + Click not working
  • Mouse over watch hints not working.

The fix is to change a regular expression in the PLSQL language parser. New installations will not have this issue, but the language parser is not applied for upgrading users (so you do not lose any language parser customizations).

If you are an upgrading user you need to modify the PLSQL language parser and add "?r)" (without quotes)  to the beginning of the “Any name" parser rule’s expression if you want full Unicode object name support. For detailed instructions, please see the Unicode Troubleshooting topic in the Help file. (Index Troubleshooting: Unicode)

 
Duplication of Arabic words when entered in quotes. CR#66590
Editor - Script Execution Error offset can be incorrect when running scripts with multi-byte object names  
Exception Logging Does not support Unicode characters in exception logging folder. Also documented in Third Party Known Issues - EurekaLog.  
Export Dataset XML (Plain) format creates bad XML if Unicode string values and Unicode column names are exported.  
Export File Browser Does not support Unicode.  
General Toad only supports Unicode for Oracle versions 9i and above.  
Hex Editor Does not support Unicode.  
Import Table Data

Korean (and probably some other languages) do not line up in fixed width, even when using a fixed width font, so importing from fixed width files is difficult or impossible to display correctly. This does not affect the actual import once the field lines are set.  It is just a display problem. This also affects other areas in Toad with a similar interface, such as the SQL Loader Import wizard.

 
Java Manager/Editor/Schema Browser

Java itself does not allow Unicode class names or file names.

 

New DB Wizard

Output files are always saved as ANSI as they are intended to be run in SQL Plus.

 
Oracle Utilities All Oracle utils (import/export wizards, data pump, SQL*Loader, SQL*Plus, Oracle Wrap Utility and so on) can only handle ANSI files.  
QSR Does not support Unicode.  
Script Output In Editor and Compare Files default to fixed-width "Courier New" font instead of System Font.  
SQL*Loader See Import Table Data.  
SQL Monitor Does not support Unicode.  
Team Coding Objects with Unicode contents are supported, objects with Unicode names are not. Supported Version Control Providers do not support Unicode names.  
Toad Group Policy Manager Does not support Unicode.  
XMLTYPE Toad can display XMLTYPE data, but the popup editor is read-only.  

Integrated Quest Products

Note: These are only the issues found during testing of Toad for Oracle. See release notes for each individual product for a full list of their known issues.

 
SQL Optimizer Object names do not support Unicode.  
Knowledge Xpert Displays only ??? when you enter Unicode characters in comments, or when you search for Unicode strings from Toad.  

 


Third Party Known Issues

The following is a list of third party issues known to exist at the time of Toad for Oracle release.

 

Feature

Known Issue

Defect ID

EurekaLog

Does not support Unicode characters in exception logging folder.

CR#65500

E-Control (Editor component) Odd word-wrapping behavior in some languages. Word wrapping may appear between symbols, with no space required to wrap, and some characters cannot be word-wrapped at all (for example, multi-byte characters in ANSI text).  

 


Upgrade and Compatibility

With Toad for Oracle 10, Toad files are no longer upgraded, but an additional installation is created. You can still choose to install the new version over the old installation of Toad, but this is not recommended. If installed side-by-side, when you first launch the new installation of Toad, you will be prompted to migrate your user settings from the old installation. This migration is optional.

 


System Requirements

 

Before installing Toad for Oracle, ensure your system meets the following minimum hardware and software requirements:

Hardware
  • CD-ROM drive or internet connection (needed for install only)
  • VGA monitor, 1024x768 resolution, small fonts
  • Mouse pointing device
Memory
  • 512 MB RAM required, 1 GB recommended
Hard Disk Space
  • 75 MB disk space required to run Toad
Operating System
    Client
  • Windows 2000
  • XP
  • 2003
  • Vista (64-bit support for Windows 2003/XP/Vista with 32-bit Oracle Client)
  • 2008
Additional Software
    Client
  • Oracle v8i Client Net 8 (32-bit only)
  • Oracle v9 Client (Net 9)
  • Oracle v10 Client (Net 10) or Instant Client
  • Oracle v11 Client (Net 11)
    Server
  • Oracle versions 8.0.6; 8.1.7; 9i; 9iR2; 10gR1; 10gR2; 11g

Note: It is recommended that your client version be of the same release (or higher) as your database version.

In addition, to take advantage of Toad's new Unicode support, you must be working with Oracle client/server 9i or above.

Back to Top


Global Operations

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, Central and Eastern Europe, Far-East Asia, Japan.

This release has the following known capabilities or limitations: Toad 10 is a Unicode application. As such, it has native support for any Oracle Unicode character set, such as UTF8 or AL32UTF8. There are some features in Toad which use or invoke Oracle Utilities or applications which are not themselves Unicode applications (CodeXpert). Their functionality is therefore limited to the character set of the client on which Toad is running (for example, Windows), and NLS_LANG must be carefully set to match the client character set. (See the Known Issues section of these Release Notes for additional information.)

 


For More Information

Get the latest product information, find helpful resources, and join a discussion with the Toad team and other community members. Join the Toad for Oracle community or visit ToadWorld for more information about Toad.

 

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our web site for regional and international office information.

Contacting Quest Support:

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.

This guide is available in English only.

 


© 2009 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

www.quest.com

Email: legal@quest.com

Refer to our web site for regional and international office information.

 

Trademarks

 

Quest, Quest Software, the Quest Software logo, Benchmark Factory, Toad, T.O.A.D., and Toad World are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

 

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.