Welcome to Toad for Oracle

New in This Release

Resolved Issues and Enhancements

Known Issues

Third Party Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

For More Information

ST78519,

78725

ST77758,

ST77851

If the query is on multiple lines, an error message no longer displays when you use the EDIT command and a WHERE clause.

An access violation error no longer occurs if your default browser is not set when you open the Project Manager.

When you type parameters for a stored procedure or function, the parameter code complete now keeps up with the typed input for the parameter.

The Query Builder no longer displays a join compatibility warning message when it should not.

The Editor no longer jumps 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 statement.

Bind Variables named "n" no longer cause ORA-01036 errors using a 10g client in the Editor.

Oracle SQL*Plus keywords and identifiers are now capitalized just like regular SQL and PL/SQL items.

Added an option to fold qualified names. The default is disabled, meaning that qualified names are not folded.

The Newlines options pane has new options:

• Add a newline after a GOTO, RETURN, EXIT or CONTINUE.
• Suppress blank lines after indenting (or before unindenting) keywords. For example: after BEGIN and before END, or after IF and before END IF. The default value is false.

A Paste Options from Clipboard button has been added to the Settings pane. When pasting, all existing options are reset to default values first. If you want to preserve any settings, copy them to the clipboard, paste into an editor, pick one format (INI or XML), and append your new options. Then, paste the new set of options.

Improved formatting for many Oracle statements, such as CREATE TABLE, CREATE INDEX, DELETE, and partitioning clauses.

Export DDL has a new option on the Storage Objects tab. You can now choose to always include partitions (the default), never include partitions (useful for getting a non-partitioned script from a partitioned object), or the default/max value only.

Added support for a few new SQL*Plus commands and extended support for many already-supported commands.

Added support for new combinations of joins and the PARTITION BY clause.

A syntax error now displays when the qualified table name in COMMENT ON TABLE has more than two identifiers.

Added support for Unicode characters in q-quoted strings.

In hash table partitioning for CREATE TABLE, multiple items of a partitioning storage clause are now supported.

The expression for a CREATE TRIGGER: WHEN clause must now always be written between parentheses.

For table partitioning, individual hash partitions can be specified without a name or partitioning storage clause.

In addition, nested column properties are now supported in a table partition description.

The Email action now supports adding directories as attachment names. All files in the folder will be added as attachments to the single email (non recursive). You can also set the email importance as Low, Normal and High.

You can now add a directory for the Execute Script action. Toad executes all files in the specified directory. A variable can represent a variable as well.

You can now set a password to open the zip files in the Archive action.

If you have McAfee Antivirus installed, it can cause issues like menu icons not functioning, slowness in launching Toad from start up, and ntdll.dll errors.

Workaround: Add Toad to the McAfee exceptions list.

Database Probe does not work with Oracle version 8.1.5.

Workaround: Upgrade to supported Oracle version 8.1.7

Viewing nested data object types on a 10g database with the 8i client closes Toad.

Workaround: Use a newer client.

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.

Toad currently does not differentiate between indexes created explicitly on the snapshot and indexes created automatically 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 recreate 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.

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 later, or see Oracle Metalink Note:124671.1 for details of how to fix the package.

If you use 11g Oracle ODP.NET client or any other client that does not have the oci.dll in the BIN directory, Toad has the following problems:

1. Client shows as invalid
2. Client version is not detected
3. As a result of #2, columns of the following datatypes are not shown in the Schema Browser table data: CLOB, BLOB, NCLOB, XMLTYPE, TIMESTAMP, INTERVAL, BINARY_DOUBLE, and BINARY_FLOAT

After 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 this manner and select "yes" to the Spec/Body file split prompt, your file will be split into two 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.

Workaround: When loading a package into the procedure edit in this manner, select "no" to the Package spec/body split prompt.

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

Workaround: To ensure PL/SQL results are saved to the database correctly, verify the validity of all objects before running CodeXpert.

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

You may receive an "ORA-00902 invalid datatype" error when editing an 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.

The data grid may hang while scrolling data on Windows 2000.

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.

Toad errors when you query on a field of Oracle collection types.

Workaround: Execute using SQL*Plus.

When spooling to an unpinned output window, the window becomes unresponsive and errors are given when Toad is closed ("Canvas does not allow drawing").

Workaround: Keep the output window pinned.

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.

Workarounds:

• Select Display large numbers in scientific notation on the Options | Data Grid | Data page.
• Upgrade to Oracle client 8.1.6 or later.

If you use a non fixed-width font, the results are misaligned in the of Script Output tab in Editor after executing a SQL script.

Workaround: Go to Options | Scripts and select a fixed-width font for script output.

Exporting data grid cells of over approximately 800 bytes could cause "OLE error 800A03EC" for Microsoft Office 2003 when using the "XLS Instance" option.

Workaround: Save using the "XLS file" option instead.

Sometimes on Oracle 8.1.7 or higher, after pressing "Compile invalid objects", you may get ORA-20000, ORA-06512, or ORA-06512 errors. This could mean that you do not 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.

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

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

For data in tables, 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.

Session Browser

Session Browser does not work with Oracle version 8.1.5.

Workaround: Upgrade to supported Oracle version 8.1.7 or later.

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: Clear the "Use RAC Views" checkbox, and log into the appropriate instance of the database, if necessary.

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 ''Create a new revision for existing objects'' option when exporting.

With CVS, Toad may fail to retrieve the list of projects for you to select from in the CVS browser or in the Code Control Groups configuration.

Workaround: See "Missing CVS\Entries File Error" in the online help.

Team Coding and PVCS:

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

The following features in Toad do not support Unicode:

• ASM Manager
• CodeXpert
• Export File Browser
• Hex Editor
• Toad Group Policy Manager

In addition, Java itself does not allow Unicode class names or file names. This is relevant to the Java Manager, Editor, and Schema Browser.

The Editor does not fully handle Unicode words, and as a result highlight object names, CTRL + Click, and mousing over watch hints may not work.

Workaround: The fix is to change a regular expression in the PL/SQL 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 upgrading, you need to modify the PL/SQL 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.

Import mapping for Unicode characters is incorrect if the characters are not a fixed width (such as Korean).

ODAC does not support Unicode in XMLTYPE.

Toad uses Secure Black Box for FTP/SSH connections. The FTP/SSH connection in Toad may fail with the following message: "Logon failed: Authentication (keyboard) failure". This issue occurs because Secure Black Box has known issues with public Putty keys.

Email

info@quest.com

Mail

Quest Software, Inc.

World Headquarters

5 Polaris Way

Aliso Viejo, CA 92656 

USA

Web site

www.quest.com