Quest has been named as an ASP "Ten Best Web Support Sites" award winner. Learn more.

Toad for Oracle 12.6 - Release Notes

Release Notes

Release Notes

Toad™ for Oracle® 12.6

August, 2014

About Toad for Oracle

Toad for Oracle provides an intuitive and efficient way for database professionals of all skill and experience levels to perform their jobs with an overall improvement in workflow effectiveness and productivity. With Toad for Oracle you can:

  • Understand your database environment through visual representations
  • Meet deadlines easily through automation and smooth workflows
  • Perform essential development and administration tasks from a single tool
  • Deploy high-quality applications that meet user requirements; perform predictably and reliably in production
  • Validate database code to ensure the best-possible performance and adherence to best-practice standards
  • Manage and share projects, templates, scripts, and more with ease

The Toad for Oracle solutions are built for you, by you. Over 10 years of development and feedback from various communities like Toad World have made it the most powerful and functional tool available. With an installed-base of over two million, Toad for Oracle continues to be the “de facto” standard tool for database development and administration.

Toad for Oracle Editions

All commercial versions of Toad are bundled with additional Dell Software products, based upon the Edition that you purchased. For more information about the latest features in your Toad Edition and the bundled products, see the Toad Editions Release Notes:

http://documents.software.dell.com

 


Was this topic helpful?

[Select Rating]



New Features

New features and enhancements

General new features and enhancements in Toad for Oracle 12.6

  • A new ASH Browser lets you view ASH session history in graphical form according to different performance criteria. Drill-down panes show the most active queries and their statistics, execution plan, and syntax.
  • The ASM Manager has new Space History and IO History tabs. These tabs are similar to the Space History and IO History tabs in the Tablespaces window.
  • The Tablespace window has been enhanced:
    • The By Datafile checkbox on the Space History tab is now next to the Datafiles field, and you can now select multiple files.
    • The Tablespace and Datafile drop-down lists on the Tablespace Space Manager graphs are now multiselect enabled.
    • You can now export the graphs to Excel by right-clicking the grid.
    • A new toolbar button on the Space History graph takes you to a new Object Growth chart in the AWR Browser.
  • The Query Builder page of the Options window has a new Maximum Visible Columns setting. It limits the size of entities within the Query Builder window to the number of columns specified, turning the entity into a scrollable window. Leaving the option unchecked displays table entities with all columns displayed.
  • There is a new Unified Audit Policies tab in the Schema Browser. It provides context selections to create and alter policies and perform filtering. This is an Oracle 12c feature available in the DBA Module only.
  • Compare Files now shows differences in formatting or comments in code that is otherwise equivalent. A new toolbar option enables you to format one or both files for easier comparison. The formatting is done in-memory and does not alter the files on disk. Enable or disable this feature in the Comparison Rules dialog in the Compare Files window.
  • You can now specify &InstanceID as a variable in custom charts. When you connect to a RAC instance, the currently selected Instance ID will be substituted into your query. This also works for a non-RAC instance.
  • In Export Data, you can now export multiple tables in an Insert or Merge format into one file. Select multiple tables from the Schema Browser left-hand side, then right click and select Export Data. Select Create one file for all tables.
  • In Toad Advisor, a new alert is triggered if the option to format files when opened is enabled. Formatting can cause unexpected differences between files on disk and database source or files in version control. A no nag message has also been added to the Editor for this option.
  • Spotlight Essentials no longer requires server side objects, and the option to install them was removed. If old Project Lucy server side objects are detected, there still is an option to remove them.
  • Source Control now supports the ability to create Version Control Projects from the Version Control Select Project dialog. This feature does not support the following VCS interfaces: Microsoft Visual Sourcesafe, SCC API, and Tortoise SVN.
  • You can now debug on a RAC instance without having separate TNSNames entries for each node in the cluster if the following conditions are met
    • The user has SELECT privilege on GV$LISTENER_NETWORK and GV$INSTANCE.
    • The Oracle version number is 11gR2 or newer.
    • EZCONNECT is specified in the NAMES.DIRECTORY_PATH parameter of SQLNET.Ora.

Team Coding enhancements

  • Team coding now supports tables, constraints, indexes, and sequences. This support is only available when the Code Collections option is selected in Team Coding Configuration.
  • VCS integration is enhanced:
    • You can create VCS sub-projects from within Toad by selecting a project in Utilities | Team Coding | Select VCS Project and then clicking New....*
    • The Version Control window in Toad Options has a new option to control whether or not objects are removed from the VCS when they are deleted in Team Coding.
  • The Schema Browser has new Team Coding Status and Collection Name grid columns. To show these columns, right-click the heading area of the left-hand side object list, and then select them from the list.
  • Code Collection setup is simplified with the ability to create VCS project sub-folders for schemas and object types. Select the new Sub-Projects option in the Code Collection configuration dialog, and optionally specify a parent folder.*

    * These features do not support the following VCS interfaces: Microsoft Visual Sourcesafe, SCC API, and Tortoise SVN.

See also:

Resolved issues


Was this topic helpful?

[Select Rating]



Resolved Issues

Resolved issues

The following is a list of issues addressed in this release, grouped by feature and then sorted in ascending order by Issue ID.

Table 1: General Resolved Issues

Resolved Issue Issue ID
In the Database Health Check, DB_EXTENDED was used in place of DB,EXTENDED for Audit Trail options based on an Oracle version. 114222
An error was returned when adding a new login record by editing an existing one. 114495
When attempting remote script execution from the MyToad website, the SQL failed with an immediate error generated in the website. 115015
Toad Reports emails were not working correctly. 115124
The auto debugger inserted DBMS_OUTPUT.PUT_LINE statements in the middle of case statements when the statement had an END statement. 115149
Toad prompted to save files after opening a workspace, whether or not they were modified. 115161
An error occurred when using variables with a Move File Child action in the Automation Designer. 115299
The date format was not preserved in the data grid when Toad Options | Data Grid | Data was selected and then a data format was clicked. 115412

Table 2: Editor Resolved Issues

Resolved Issue Issue ID
Perl code generated by Toad in Make Code Statement used a plus sign instead of a period as the string concatenation operator. 114521
Toad returned an error when the STATE of a SUBCHAIN step was changed. 114980
Renaming a NOT NULL column caused an error. 115556

Table 3: Schema Browser Resolved Issues

Resolved Issue Issue ID
In the Schema Browser,when a default tab was set and then the browser style was set from Dropdown back to Single Tab, the default tab was not visible. 114025
In the Schema Browser, the Rowid column did not follow a user-defined parameter naming convention 114317
In the Schema Browser, Create Role in another database using the same role from the source database did not show the schema name for object grants. 115006
The Stats/Size tab for a table in the Schema Browser did not format numeric fields with a thousands separator. 115028
The Table Browser and Schema Browser sorted names incorrectly if any name contained an underscore. 115083
When a Schema Compare was performed, it correctly identified a datatype difference but incorrectly identified a change in nullability when none existed. 115092
The Open Cursors filter in the Session Browser did not work properly for long queries 115188
The Schema Browser returned an error when going to the Scripts tab for a table that is partitioned and also has an XMLTYPE column. 115322

Table 4: Team Coding Resolved Issues

Resolved Issue Issue ID
In Team Coding, it took a long time for the Toad Clearcase Explorer to open. 109705
The Configure Team Coding dashboard was disabled even though Team Coding with collections was enabled. This occured when a connection was made to the database from the Project Manager. 114679
Invalid repository directory values in PVCS version control caused Toad to return an error message. 115035

Table 5: Code Insight Resolved Issues

Resolved Issue Issue ID
In Code Insight, the alias was replaced by the table name when using the column drop-down list. 115024
In Code Insight, duplicate tables were created in the popup selection list. 115064
In Code Insight the drop-down list was missing when the statement contained two aliases. 115249

 

 

 


Was this topic helpful?

[Select Rating]



Known Issues

Known issues

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

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

N/A

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
N/A

Debugger

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.

N/A

Connections

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

N/A

Data Grids

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.

N/A

Schema Browser

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.

N/A

Virtualization

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

76354

Import/Export

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

59228

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

 

Table 7: Code Analysis known issues

Known Issue Issue ID
Saving results to a database: When dealing with nested procedures, CodeXpert 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 CodeXpert.

N/A

 

Table 8: Editor known issues

Known Issue Issue ID

When file splitting is used in the Editor, Code Analysis does not automatically check the code in the Editor.

Workaround: Click the "Analyze Code in Editor" button.

85604

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

Workaround: Execute using SQL*Plus.

64373

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.

68523

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.

62234

 

Table 9: 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 10.1.0.3 (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.

N/A

 

Table 10: Team Coding known issues

Known Issue Issue ID

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.

114334
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.
N/A

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.

N/A
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

 

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

N/A
Connections to Service Names with Unicode Characters are not supported. N/A

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.

N/A
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).

63221
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

 

Table 12: Third-party known issues

Known Issue Issue ID

Help

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

N/A

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

N/A

ODAC

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.

62654

Was this topic helpful?

[Select Rating]



Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
Related Documents