Chat now with support
Chat with Support

Toad for Oracle 13.0 - Release Notes

Resolved Issues

This section contains a list of the issues that were resolved in this release of Toad for Oracle.

Toad for Oracle

These fixes include issues received from Toad beta and Forum users.

Issue ID

Link (If from Forums)

Resolved Issue


Session browser resets filters, they don't stay set.


Ctrl+B and Shift+Ctrl+B (comment/uncomment line) do not work in modal dialogs


Left/Right navigation keys do not filter Code Insight


Query to load packages to the Schema Browser slow in some cases


Compare current val option not working for sequences


Error when running Health check with "FK Constraints with nonmatching column definitions"


Cursor results showing numbers in scientific notation
TOR-1194   SQL Recall not saving Named SQL


Export File Browser hanging
TOR-1744 Link Access Violation pasting large text in 64-bit



Out of bounds after removing connections

TOR-1835   Invalid column suggestion for un-aliased subquery


Ora-02248 after altering datafile in 12c non-pluggable database
TOR-1867   DBMS Output for PL/SQL Table (associative array) is not generated


Syntax error occurred for dblink in this case.
TOR-2020   Entering single(s) quote into the check in/out comment box cause errors.


Schema compare synonym bug


Private synonyms going into wrong schema



Invalid command to lock/unlock partition stats



RAW datatype is incorrectly unsupported for unit test creation



Search Match transparency results in difficult to read text



Toad defaulting to TNS entries, even when LDAP connections are made



Describe menu does not come to the front



F4 does not always open DESC



Ctrl+T causes AV



Poor Performance of behind scenes Constraints Query



Dropping a type with force option from schema browser does not work



"Exact match" not working correctly in Object Search



Can't connect from "create login record" window when using direct method



Paste non-functional in Editor data grid



Schema Browser bug in procedure/function query for pre-11g



"ORA-12538: TNS:no such protocol adapter" opening workspace

TOR-2155   set define off in glogin.sql changes escaped characters to UPPERCASE



Project Manager width not retained



Object compare - next/previous difference option setting not being saved



Primary/Secondary Instances showing incorrectly in Queue Table Ganeral Tab



Oracle ODBC connection not working



Ctrl+C and Ctrl+V not always functioning in SDI mode when Project Manager is open



DB Links weren't being closed after testing



Generated join conditions are incorrect



ORA-12154 error when using Direct Connect and calling TSR or Auto Optimize SQL



SQL*Loader sometimes not connecting



Toad forms sometimes opening off-screen when in SDI mode



Uncomment block does not work in Alter windows



Code Insight not working for CTE with a union



"An invalid character was found in text content"

TOR-2240 Link Package isn't split



Explain Plan columns get reset on editor tab switch



Words matching selected word not highlighted

TOR-2253   Improvement Program Window still displays on first launch/close of Toad with RESTRICTIONS=i install



The Script Tab not showing NULL values

TOR-2263   Jump not enabled when Internet is restricted with RESTRICTIONS=i installation



LIOOB when copying tables with Clobs and logged in as SYSDBA



Session Browser doesn't use correct schema for Auto-Optimize



Undo checkout is recreating table and therefore all data is lost



Find Next not working



Wrong "Min size" query if non-empty recyclebin



Can't close Toad when session disconnected



Rebuild Table fails without SELECT privilege



Make Schema Compare more responsive

TOR-2294 Link Rebuild Table fails without SELECT privilege

TOR-2435 and TOR-2434


  • Change the default for Spool encoding to ANSI
  • Add support for setting the encoding option at an action level



Extend the width of Foreign Column and Sequences in Data Generation

TOR-2313   Session adds itself to login recently used list every time it is established
TOR-2344 Link AV on closing SB or Editor after CLOB edit
TOR-2355 Link Macro with newline does not observe auto-indent option
TOR-2362   Object Search treating underscore as a word boundary character
TOR-2376   ESC to cancel query execution cannot be disabled
TOR-2382 Link File reopen menu inconsistencies
TOR-2391   Missing InMemory information for partitioned tables
TOR-2403   Custom colors in login window don't show in the grid
TOR-2421 Link AV sorting grid column
TOR-2431 Link Additional Editor opened unnecessarily
TOR-2441 Link Output window doesn't automatically scroll to the added line for TC messages
TOR-2443   Auto Replace activates on whitespace
TOR-2497 Link Reopen File menu is empty
TOR-2499   "One/Connection" and "One/Toad" Windows behavior options are not working for Describe window.
TOR-2502 Link Error due to "Enable FK Lookup"
TOR-2507 Link Custom dates from excel files don't preview in data import
TOR-2529 Link Add Schema dialog showing off screen in SDI mode
TOR-2537   Executing the Generated Query does not return results, but the same query returns results in the Editor.
TOR-2561   "send selected sync scripts" top panel button does not respect checkboxes below
TOR-2586 Link Editor hang editing text

QP5 (Quest Parser)

The following are fixes made to the parser, formatter, and Code Analysis rules.

Issue ID Resolved Issue



Fix: Possible stack overflow on very deeply nested code. This will now be handled gracefully.

Code Analysis:

  • Fix: Rule 4001 ("Avoid using GOTO out of a loop.") did not check that the GOTO actually goes out of the loop.
  • Fix: Rule 6806 ("Use native execution for PL/SQL that is compute intensive and has little SQL.") : This rule has been removed because when it raises it will raise forever. That nagging behavior cannot be stopped by compiling natively because at this time Code Analysis cannot get to know the actual mode of compilation.
  • Fix: Rule 2102 ("Avoid comments that are not explanatory within the body of the code.") : This rule has been removed because the criteria are too vague, too subjective.





  • Fix (-QP-2599-) : MERGE statement: A data-source in the USING clause can now be of the form identifier.identifier@dblink.
  • Fix (-QP-2615-) : Support for SQL*Plus multi-line comments following the statement at the right.

    Example:@myproc /* some comment*/

    In Sql*Plus the /* must be followed by a space

  • Fix (-QP-2604-) : CREATE TABLESPACE: LOGGING could not be used together with FORCE LOGGING.


Fix (-QP-2628-) : Since version 5.311 a end-of-line comment was positioned one space further to the right, leaving two spaces between the statement and the comment. This has be brought back to one space.


p_partno => r.partno, p_synonym_of => r.synonym_of, p_value_lines => COALESCE (r.value_lines, 0) + COALESCE (r.repl_value_lines, 0), Former output (5.307): p_partno => r.partno, p_synonym_of => r.synonym_of, p_value_lines => COALESCE (r.value_lines, 0) + COALESCE (r.repl_value_lines, 0), New output: p_partno => r.partno, p_synonym_of => r.synonym_of, p_value_lines => COALESCE (r.value_lines, 0) + COALESCE (r.repl_value_lines, 0),

Code Analysis:

  • Fix (-QP-2299-) : Rule 4002 ("Avoid using a backward GOTO.") was rewritten to take advantage of QP5 XPath.
  • Fix (-QP-2306-) : Rule 5804 ("Ensure SELECT COUNT( * ) is being used to check the number of rows and not merely the existence of rows.") was rewritten to take advantage of QP5 XPath.
  • Fix (-QP-2579-) : Rule 2831 ("Use PLS_INTEGER instead of INTEGER or equivalent subtypes.") no longer raises for CREATE TYPE.
  • Fix (-QP-2600-) : Rule 4503 ("Calls to DBMS_ADDM require optional OEM packs for DIAGNOSTIC + TUNING.") : DBMS_ADM renamed to DBMS_ADDM wherevever applicable.
  • Fix (-QP-2601-) : Rule 4204 ("Avoid IF when assigning values to boolean variables.") : Example code fixed.
  • Fix (-QP-2612-) : Rule 4537 ("Consider using a CONTINUE statement to eliminate a backward GOTO to the beginning of the loop.") was renamed from "Utilize the CONTINUE statement rather than a GOTO or an extra level of conditional logic within a looping construct".




Formatter :

Fix (QP-2534) : Fix (QP-2689) : Due to a required change all list parentheses will now figure inside their list node. Formerly, they were positioned around the list. As a result, about all list constructs will now obey the List Arrangement formatter options, there should not be any "hard coded" lists anymore. Hence the layout of several lists may be a bit different Work on lists is still in progress on the short term.

Code Analysis:

Fix (QP-807) : [ Rule 4403|http://qp5/do/view/QP5/CodeAnalysisRule4403] ("Avoid unlabeled nested blocks.") : Converted to XPath expression.



  • Fix (QP 2678) : Support added for user defined analytic functions.
  • Fix (QP 2714) : Parse error on Json_objectagg(KEY identifier ...)

Formatter changes with respect to version 5.319:

  • About all lists now obey the "list arrangement" settings; many infrequently used list resort under "Other" lists.
  • Less folding if folding not required, especially single names between parentheses are now output on a same line.
  • More SELECT statements will be formatted on a single line when that option is selected.
  • SELECT list aliases: when on a same line than room (one indent unit) is left between select list item and index;this should result in a more transparent statement.
  • Other enhanced formatting:


    CREATE TABLE: data types were not aligned

    PARTITION clause

    EXECUTE Code Analysis:

    Fix (QP 2648) : Rule 5809 ("Ensure elements in the SELECT list (either columns or expressions) are qualified by a table/view name when needed.") This rule will hit in the following cases (subquery and PL/SQL variable cases):

         SELECT * FROM tab1
           WHERE EXISTS (SELECT * FROM tab2 
                          WHERE col2 = 10);    -- hit on col2
           name   VARCHAR2 (100);
            name,   -- hit
          INTO e, f 
          FROM t;





Fix (QP 2766) : Packages: Chunking fixed when the keyword AS is used in a CAST function.


Fix (QP 2768) : Formatter fails to align values in VALUE clause.

Code Analysis:

  • Fix (QP 2735) : Rule 2746 ("A CASE statement should have an ELSE clause") Rule type, category and severity were missing, causing the rule not to appear in the Toad rule universe.
  • Fix (QP 2735) : Rule 6748 ("Consider writing IF THEN CONTINUE as CONTINUE WHEN.") Rule type, category and severity were missing, causing the rule not to appear in the Toad rule universe.





  • Fix (QP 2788) :
  • Distance between parameters and data types fixed to become exactly one indent (from one indent + one space). This change is due to a required major refactoring of the parameter declaration formatter code.
  • Stacked parameter declaration lists now have the IN, OUT, INOUT and NOCOPY keywords of their parameter declarations justified.

Code Analysis

  • Fix (QP 2800): Rule 5914 ("Use untransformed column values in the WHERE clause.")

    • Speedup (around 70 times) fixing possible multi-second delays.
    • Parameter specifications were not taken into account.
  • Fix (QP 2786): Rule 5920 ("Apply the invoker rights method to all stored code that executes dynamic SQL")

    • Speedup (around 70 times) fixing possible multi-second delays.


Code Analysis

Fix (QP 2304) :

Rule 4806 ("Avoid use of unreferenced FOR loop indexes.") RULE REMOVED.

Rule 2746 ("A CASE statement should have an ELSE clause") : Topic text added.

Rule 2757 ("A CASE expression should have an ELSE clause to avoid it returning NULL") : Topic text amended.

Rule 5920 ("Apply the invoker rights method to all stored code that executes dynamic SQL") : Example code added.

Known Issues

The following is a list of issues, including those attributed to third-party products, known to exist in this release line at the time of the current release.

General known issues

Known Issue Issue ID
Toad's help cannot be opened from an installation path that contains Unicode characters. 72966

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.


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


If there is an exception during debugging on a 10Gr2 or greater database, REFCURSOR output and DBMS output will not be available when debugging is completed. This is due to the target session not being available.

Workaround: To see REFCURSOR output and DBMS output, execute the procedure without the debugger.



While Toad supports LDAP connectivity, some features of Toad depend on tnsnames.ora file to operate correctly, such as Toad Script Runner (TSR).


Schema Browser

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



An access violation error may display when you close Toad in a Citrix XenApp environment.



Constraint scripts from Export DDL do not contain the "using index" or "tablespace" clause.


Data Modeler:

  • Generation of HTML reports of large diagrams may fail during generation of an image of the ER Diagram.
  • Comparison of large models may consume too much memory.

Data Grids known issues

Known Issue Issue ID

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.


Full table data is not displaying in the live data grid (results from F9) if the data contains "zero" characers (ACII 0). In this case, all data after the zero character will not show in the grid.

Workaround: Double click on the data cell in the data grid to view full contents of data in a popup editor.


Code Analysis known issues

Known Issue Issue ID
Saving results to a database: When dealing with nested procedures, Code Analysis can only insert run data from procs one level deep. N/A

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


Editor known issues

Known Issue Issue ID

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.


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.


Session Browser known issues

Known Issue Issue ID
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. N/A

In RAC databases, version (and possibly other 10.1 versions), the query used to 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 known issues

Known Issue Issue ID

Creating a new revision or attempting to force a check-in to Visual Studio Team Services may result in a "404: Not Found" error. The current version of Team Foundation Server used by Visual Studio Team Services compares the source being uploaded with the source already in the repository. If the source has not changed, it may incorrectly return an error rather than allowing the forced revision. This appears to be a Microsoft issue. As a result, these two commands may fail.


When using the Team Foundation Server internal client and Team Foundation Server 2012 or 2013 alternate Team Project Collections, workspaces created outside of Toad are not visible from within Toad. A workspace may be created from Toad by clicking the ‘New’ button during the Team Foundation Server log in.

This is not an issue when using the Team Foundation Server external client.

Team Coding is disabled for mixed-case object names. N/A

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 Clearcase: Dynamic Views are not supported via SCC interface. Snapshot Views must be used instead. (Rational case ID v0830629, Rational Defect # CMBU00053934) N/A

Unicode known issues

Known Issue Issue ID

The following features in Toad do not support Unicode:

  • ASM Manager
  • Export File Browser
  • Hex Editor

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


Editor options to highlight object names may not work for object names that contain Unicode characters.

Script Execution in Editor: Error offset can be incorrect when running scripts with multi-byte object names. N/A
XML (Plain) format creates bad XML if Unicode string values and Unicode column names are exported through Export Dataset. N/A

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

In Team Coding, objects with Unicode contents are supported, objects with Unicode names are not. Supported Version Control Providers do not support Unicode names. N/A

Third-party known issues

Known Issue Issue ID


(Affects the 64-bit version of Toad only)

If IE9 is installed, clicking a link in the Help file may crash Toad 64-bit, even if IE9 is not the default browser.

Workaround: Users who have IE9 installed can open Help from outside of Toad.



ODAC does not support Unicode in XMLTYPE (editing of XMLTYPE data is not supported). Querying of XMLTYPE with binary storage will lead to an error.


System Requirements

This section contains the hardware, software, and privileges required to run Toad for Oracle, as well as the database and virtual environments that Toad for Oracle supports.

Hardware requirements




  • 1 GB RAM - Toad for Oracle 32 bit
  • 2 GB RAM - Toad for Oracle 64 bit

Note: The memory required may vary based on the following: 

  • Applications that are running on your system
  • Size and complexity of the database
  • Amount of database activity
  • Number of concurrent users accessing the database

Hard disk space

  • 120 MB - Toad for Oracle 32 bit
  • 150 MB - Toad for Oracle 64 bit

Operating system

  • Windows Server 2008 R2 (64-bit) - 2 CPU required
  • Windows 7 (32-bit and 64-bit)
  • Windows 8 and 8.1 (32-bit and 64-bit)
  • Windows Server 2012 (32-bit and 64-bit) - 2 CPU required
  • Windows Server 2012 R1 and R2 (64-bit) - 2 CPU required
  • Windows Server 2016
  • Windows 10

Database requirements



Database client

An Oracle client must be installed and configured on the system where you are running Toad. The following are supported:

  • Oracle Client or Instant Client
  • Oracle Client or Instant Client
  • Oracle Client or Instant Client 12c Release 1 and 2

Note: You must use the 32-bit version of Toad with the 32-bit Oracle client, and the 64-bit version of Toad with the 64-bit Oracle client.

Database server

Oracle versions:
  • 10g R2
  • 11g, 11g R2
  • 12c Release 1 and 2


Toad has been tested on Oracle Exadata 5.0 running Oracle database 12.1.

Important: It is recommended that your client version be of the same release (or later) as your database server. This is an Oracle recommendation to prevent performance issues.

Cloud database service

Oracle Database as a Service on Amazon EC2 and Oracle Cloud


Internet Protocol Version 6 (IPv6) is being adopted by the US Federal Government and industries around the world. In its most basic format, the new protocol uses 128-bit addresses instead of 32-bit addresses, which are used by the current IPv4 to route packets over the Internet. Toad for Oracle features, such as FTP, access the Internet through third-party vendors that are IPv6 compliant, such as /nSoftware's IP*Works. For access to Web sites by way of the Toad Online window, Toad simply invokes the user-defined or default Web browser.

Additional requirements



Additional Software

  • Microsoft Internet Explorer 6.0 or later (to view video from the Jump list within Toad, and to view the product documentation in HTML format).
  • Microsoft Office 2016 and recent earlier releases are supported for Word and Excel output.
  • Adobe Acrobat Reader 7.0 or later (to view the product documentation in PDF format).
  • Microsoft .NET Framework 4.0 to support the Toad for Oracle Editions Installer.

Virtualization support



Application virtualization

Citrix® XenApp

Desktop virtualization (VDI)

Dell™ vWorkspace™ 7.0 has been tested.

Server virtualization

Oracle VM 3.1 has been tested.

VMware ESX Server 3.5, 4.0, and 5.5 have been tested.

Note: Toad may work in virtualization environments other than the ones listed.

Windows Privileges

In order to install and run Toad, make a connection, and do basic operations, you must have the following privileges.

Operating System


Windows 7

  • Read access to the Oracle client folder
  • Read/write privileges on the Oracle Home directories that you use for your connections

Windows 8 and later

Windows Server 2012 and 2016

  • Read access to the Oracle client folder
  • Read/write privileges on the Oracle Home directories that you use for your connections

Note: Other functionality in Toad may require additional privileges.

Product Licensing

To activate a trial

  1. Go to the trial download web page:, accessed through the product page.
  2. Select the Toad for Oracle Edition that you want to try.
  3. Log in to your account or register.
  4. Accept the license terms.
  5. Download the trial file.

To activate a purchased commercial license

  1. Go to the Quest Support website:
  2. Type the name of the product that you want to activate in the Enter your product to find support field.
  3. Select Download New Releases.
  4. Download the installer file.


  • License keys compatible with Oracle 9.7 and earlier versions are no longer supported.
  • Only the newer 48-character license keys are supported.
  • If you have an older license type, the Editions installer points you to the license web page where you can update it.
Related Documents