March 04, 2014
For information related to the 12.1.1 patch, see Resolved Issues.
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:
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.
All commercial versions of Toad are bundled with additional Quest 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.
These features, described below, make Toad for Oracle 12.1 even more useful:
Quick connection help
If an error occurs during a connection, Toad now automatically examines your Windows PC environment, Oracle Home(s) and other variables to offer potential solutions. In addition to the Oracle “ORA-0XXXX” error message, you will see a list of items checked with possible causes and next steps.
Toad for Oracle 12.1 expands Oracle 12c support with the new Pluggable DBs tab on the Database Browser. Read Oracle details regarding their 12c multitenant option.
If you are using Oracle 12c multitenant/pluggable databases:
In Toad, see this Help topic for step-by-step instructions: "Using Pluggable Databases."
Regarding Toad's new refactoring support, read resident expert and author Bert Scalzo's blog post on Toad World.
These additional refactoring options are introduced in Toad 12.1.
Refactor menu items
Add Column Aliases
Remove Column Aliases
Adds or removes aliases to columns in select lists.
The bold aliases in the refactored SQL are added with "Add column aliases" and removed by "Remove column aliases."
SELECT empno, DECODE (deptno, 10, 'New York', 20, 'Dallas', 'Chicago') FROM emp e, dept d WHERE e.deptno = d.deptno;
SELECT empno EMPNO, DECODE (deptno, 10, 'New York', 20, 'Dallas', 'Chicago') COL FROM emp e, dept d WHERE e.deptno = d.deptno
Convert to ANSI Join Syntax
Convert to Oracle Join Syntax
Converts from proprietary Oracle join syntax to ANSI and from ANSI join syntax to the proprietary Oracle syntax.
ANSI join syntax is cross-platform compatible and compatible with queries. Using it should execute successfully on other database systems that support the ANSI syntax.
This query uses Oracle join syntax:
SELECT empno, DECODE (deptno, 10, 'New York', 20, 'Dallas', 'Chicago') FROM emp e, dept d WHERE e.deptno = d.deptno;
This query uses ANSI join syntax:
SELECT empno, DECODE (deptno, 10, 'New York', 20, 'Dallas', 'Chicago') FROM EMP E CROSS JOIN DEPT D WHERE e.deptno = d.deptno;
Remove Subqueries Using ANSI Join Syntax
Remove Subqueries Using Oracle Join Syntax
Queries are rewritten so that table joins and where clause expressions are used in place of subqueries. Notice that the original SQL includes an embedded SELECT statement. This subquery is removed in the refactored SQL, scott.dept is referenced in the main query, and the where condition is rewritten as EMP.deptno = DEP.deptno.
WHERE deptno IN (SELECT deptno FROM scott.dept);
FROM scott.emp EMP, scott.dept DEP
WHERE EMP.deptno = DEP.deptno;
The above example uses Oracle join syntax.
If the Remove using ANSI syntax was used, this would be the refactored SQL:
FROM SCOTT.EMP EMP INNER JOIN SCOTT.DEPT DEP ON (EMP.DEPTNO = DEP.DEPTNO);
|Correct Where Clause Indentation Level||
A query may be written so that a where clause expression occurs within a subquery, and that expression does not reference any identifiers in the subquery. In the following simple example, the "WHERE .empno > 5000" expression is operating on empno, which is a column of the "emp" table, and that table is referenced in the outermost query. The refactored SQL moved that expression out of the subquery. This is important for both readability and optimization.
FROM scott.emp e
WHERE e.deptno IN (SELECT d.deptno
FROM scott.dept d
WHERE e.empno > 5000);
FROM scott.emp e
WHERE e.deptno IN (SELECT d.deptno
FROM scott.dept d)
AND e.empno > 5000;
|Convert Decode Function to Case Statement||
Case statements are better suited for ANSI syntax compatibility.
Original SQL using DECODE function:
SELECT empno EMPNO,
DECODE (deptno, 10, 'New York', 20, 'Dallas', 'Chicago') COL
FROM emp e, dept d
WHERE e.deptno = d.deptno;
Refactored SQL using CASE statement:
SELECT empno EMPNO
WHEN deptno = 10 THEN 'New York'
WHEN deptno = 20 THEN 'Dallas'
FROM emp e, dept d
WHERE e.deptno = d.deptno;
You can select a portion of code and extract it into a new procedure.
The code for the new procedure is generated, and the original code is modified to call the newly generated procedure.
|Find Unused Variables||
Identifiers that are declared as variables, parameters, etc. within PL/SQL may be declared, but not used.
This refactoring item identifies all unused identifiers.
|DBMS_PARALLEL_EXECUTE Wizard||Incrementally update table data in parallel.|
|Rename Identifier||Select and rename an identifier. The identifier is renamed throughout your code while respecting variable scope.|
|Sync Order By with Group By||
When a GROUP BY clause is specified in a query, a corresponding ORDER BY is used to sort the result set.
An ORDER BY is not required, nor is it required to contain all of the items in the GROUP BY.
Oracle will implicitly order the items that are not specified, so adding the implicitly sorted items to the query aids in readability, because you can clearly see the order.
SELECT COUNT (*)
GROUP BY field_1, field_2, field_3
ORDER BY field_2;
SELECT COUNT (*)
GROUP BY field_1, field_2, field_3
ORDER BY field_2, field_1, field_3;
You can now take these actions via ODBC drivers:
Load Cols from File; import column definitions from tables in external databases
Export Dataset; export to external databases. The table must already exist in the target database.
Note that Toad’s login window does not support generic ODBC connections.
Now, when you are generating a schema or database script, or comparing schemas or databases, you can save and recall all of those options you select.
Note: You can compare schemas and databases in the Base Edition, but Snapshot files (formerly Definition files, see below) and sync scripts are only available with the DB Admin Module or Toad for Oracle Xpert Edition.
To see this enhancement:
You can save and recall those same settings (options) for:
You can also save and recall your settings for:
These settings do not include connection and output details, just the options you selected and saved.
Faster generation and comparison
Optimizations to schema script generation and schema comparison speed up performance; the more objects in the schema, the better the speed improvement.
Source control support for Git has been added. Toad handles standard check-ins, check-outs, and adds to a locally stored Git repository.
In Toad, see this Help topic for instructions: "Git Configuration."
TFS Work Items
When using Team Foundation Server (TFS) in Toad, you can now check-in TFS Work Items and link one or more TFS work items to the check-in change set. (Idea Pond idea 525)
In Toad, see this Help topic for step-by-step instructions: "TFS Work Items."
You can now compare a schema with a version control system (VCS) revision. This was previously available for individual objects but not an entire schema. (Idea Pond idea 661)
In Toad, see this Help topic for more detail: "About Code Collections."
You can now suppress the message when an exception is encountered during debugging, while still allowing the break to occur. Go to View | Options | Debugger to de-select or select Show Exception Break Message.
The "Grants Received" query on the Schema Browser | Users | Object Grants (tab) is now a threaded process, so you can do other things while you wait.
You can now rename your Favorites folders for better identification and management. (Idea Pond idea 850)
Code Analysis is Toad's powerful code review and analysis tool. It helps you ensure that the performance, maintainability, and reliability of code meets and exceeds your company’s best practice standards.
Code Analysis has the following new features:
You can now sort Rule Violations by RuleID.
Go to Database | Diagnose | Code Analysis to see the updated UI.
Wrapped objects are no longer supported. Because they are encrypted, they will not generate any valid information. When trying to add a wrapped object for analysis, a warning will specify the wrapped objects that cannot be analyzed.
Trace File Browser
When a file containing a deadlock is opened in the Trace File Browser, the statement causing the deadlock is now immediately brought to your attention. A new "Deadlock" tab along the bottom half of the window contains details provided in the trace file.
Definition files are now Snapshot files, with an easy preview
Note: This functionality is available with the DB Admin Module or Toad for Oracle Xpert Edition.
Schema and database definition files are now Snapshot files. These are available in Generate Schema/Database Script, Compare Schema/Database, and HTML Schema/Database doc generators.
Analyze All Objects
You can now use DBMS_STATS.GET_PREFS and DBMS_STATS.SET_PREFS (available on Oracle versions 11g and newer).
These give you the ability to define and use preferences for different dbms_stats parameters on a database, schema, or table level. If you have the DB Admin Module, go to Database | Analyze | Optimize All Objects.
Idea Pond is a site where you can submit your ideas to improve Toad and vote or comment on other people's ideas. Toad's development has always been driven by our customers, and now it is even easier for you to tell us what changes are most important. This site is free for all customers.
The following Idea Pond submissions were implemented for this release:
|Feature||Enhancement||Idea Pond ID|
|Team Coding and Version Control||Added functionality to associate TFS Work Items.||525|
|Provided functionality to compare a Schema with a VCS Revision. (This was previously available for individual objects but not an entire schema.)||661|
|Open and Save||You can now rename your Favorites folders for better identification and management.||850|
|Improved the performance and usability of the new Save dialog.||854|
In the Tablespaces window, you can now choose to display numbers in units such as Megabytes, Gigabytes, Terabytes, and so on. This affects the way tablespaces are shown in the Schema Browser.
Note: This patch does not support Oracle 10.1 database client software. If you are currently using an Oracle 10.1 client, we recommend upgrading to 10.2 or any other Oracle supported client.
|Team Coding||"Check in all" dialog did not retrieve correct locking information when Team Coding was set up with no VCS.||113686|
|Connections||Proxy log-in was failing using OID setup.||113668|
|Database Browser||Schema Browser was getting embedded in treeview mode.||113666|
|Schema Browser||Poor performance when a Schema has a lot of packages.||112352|
|Editor||Save new file: was not using last saved path, went to desktop instead.||112351|
|Editor||File|Open resulted in "Error connecting to the repository."||112341|
|Schema Browser||Icons were missing in dropdown/multi-tabbed layout.||112281|
|Database Browser||Schema Browser window initially appeared when clicking on a node.||109620|
|ASM Manager||Database|Administer|ASM Manager: Toad can now drop disks from the ASM disk group.||111926|
|Data Grid||Display of NUMBER columns in 64 bit Toad is now correct.||111924|
|View Tablespace||Space History Graph now functions properly.||110481|
|Compare Schemas||More than 1000 queue tables in a schema was generating an error.||110432|
|Open and Save dialog||Open file window was slow to open.||110103|
|SQL Loader Wizard||SQLLDR and EUS function properly now.||105136|
|Automation Designer||File Exists action was not supporting wildcards.||111678|
|Editor||Commit didn't work with Proxy User.||110929|
|Import Table Data||Toad now completes this successfully.||111113|
|Open and Save dialog||File Open dialog was freezing when a server folder was selected.||110831|
|Schema Browser||The date was changing when using all caps in month name in data grid.||110637|
|Schema Browser||System Generated Named objects now work properly.||110527|
|Schema Browser||Importing an empty table no longer causes Toad to crash.||109991|
|F5 Script Execution||Autotrace output ambiguity is resolved.||111562|
|Schema Browser||LHS pane now shows full Object names; scroll bar functions.||110484|
|PLSQL Debugger||Watch on package variable now shows value.||86006|
|Schema Browser||The Rebuild Table GUI now lets you change parallel options for partitioned tables.||
|Open and Save dialog||Typing the file path now brings the information into the File Name field.||110887|
|Export Utility Wizard||Oracle error 1031 is no longer encountered.||110983|
|Open and Save dialog||The correct directory is now available in the Save As dialog.||111679|
|Connections||Schema Compare sync script now works properly.||109761|
|Import||Boolean values are now treated correctly.||110025|
|Compare Schemas||Invalid syntax is no longer returned in play script.||110022|
|Schema Browser||ORA-22853 no longer encountered when funning DDL script generated by Toad.||111212|
|Schema Browser||Toad properly handles Optimize Views SQL | Auto Optimize on a view.||110079|
|Import Table Data||Last rows are now imported when using 'Last Row' and 'User array DML' options.||110928|
|Import||Toad now imports multiple tables from an Access source during Database | Import.||110556|
The following is a list of issues known to exist at the time of this release.
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.
|Task Scheduler||Reordering of Actions within the Task Scheduler on Windows Vista and higher is currently not supported. However, action items can be reordered within the Windows Task Scheduler.|
|64-bit SQL Tracker||
Launching SQL Tracker (in the UI: Database | Monitor | SQL Tracker) gives the following error:
If the .NET framework v2.0.50727 or higher is not installed, launching SQL Tracker will give you the following error:
“The application failed to initialize properly."
The error should indicate:
“To run this application, you first must install one of the following versions of the .NET Framework: v2.0.50727. Contact your application publisher for instructions about obtaining the appropriate version of the .NET Framework.”
Workaround: Install the latest .NET framework.
The 64 bit version of Toad does not provide native support for the following Version Control Providers:
- Microsoft Visual SourceSafe
- Merant Version Manager (PVCS) version 5.2/5.3/6.0
- Merant Version Manager (PVCS) version 6.6 and later
Integration with vendors who support the SCC API is dependent on the provider’s 64 bit implementation of SCC.
Database Probe does not work with Oracle version 8.1.5.
Workaround: Upgrade to supported Oracle version 8.1.7
|General||Toad's help cannot be opened from an installation path that contains Unicode characters.||ST72966|
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 18.104.22.168.0 and 22.214.171.124.0.
Workaround: Upgrade to Oracle version 126.96.36.199.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:
|Code Analysis||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.
|Connections||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.||N/A|
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.
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.
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.
|Editor||If you select object tables with nested VARRAYs, the statement is busy and cannot be aborted.||ST62336|
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.
|Import/Export||Constraint scripts from Export DDL do not contain the "using index" or "tablespace" clause.||ST59228|
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.
Session Browser does not work with Oracle version 8.1.5.
Workaround: Upgrade to supported Oracle version 8.1.7 or later.
|Session Browser||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.
When using Microsoft Team Foundation Server, customers may receive an "Unable to get revision from VCS repository" error followed by "VCS archive is empty". This error generally occurs if customers use different workspaces when logged in to TFS.
Workaround: See Quest Support Solution SOL74899.
|Team Coding||Team Coding is disabled for mixed-case object names.||N/A|
Team Coding and SourceSafe:
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||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.||N/A|
Team Coding and PVCS:
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||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|
The following features in Toad do not support Unicode:
In addition, Java itself does not allow Unicode class names or file names. This is relevant to the Java Manager, Editor, and Schema Browser.
|Unicode||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.
|Unicode||Script Execution in Editor: Error offset can be incorrect when running scripts with multi-byte object names.||N/A|
|Unicode||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).
|Unicode||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|
|Virtualization||An access violation error may display when you close Toad in a Citrix XenApp environment.||ST76354|
The following is a list of third party issues known to exist at the time of this Toad for Oracle release.
|Feature||Known Issue||Defect 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.
|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 does not support Unicode in XMLTYPE (editing of XMLTYPE data is not supported).
Querying of XMLTYPE with binary storage will lead to an error.
Upgrades for Toad install side-by-side with any previous versions you have installed. You can run the new and previous versions concurrently.
The first time you run the new version of Toad, settings files from the previous version will be automatically imported. If you wish to start with a clean set of user files, run the Copy User Settings utility under the Utilities menu and select 'Create a clean set of user files from the base installation.'
Note: Toad supports importing settings only if the new version is within two releases of the previous version. If your versions are more than two releases apart, you need to install an intermediate version to successfully import the files.
No features were deprecated in this release.
Before installing Toad, ensure your system meets the following minimum hardware and software requirements.
1 GB RAM required for 32-bit
2 GB RAM required for 64-bit
Note: The memory required may vary based on the following:
|Hard Disk Space||
Windows Server 2003 (32-bit and 64-bit)
Windows XP (32-bit and 64-bit)
Windows Vista (32-bit and 64-bit)
Windows Server 2008 (32-bit and 64-bit) - 2 CPU required
Windows Server 2008 R2 (64-bit) - 2 CPU required
Windows 7 (32-bit and 64-bit)
Windows 8 (32-bit and 64-bit)
Windows Server 2012 (64-bit)
64-bit Toad's SQL Tracker requires Windows Vista or later.
Oracle Client 188.8.131.52
Oracle Client or Instant Client 10.2.0.3/10.2.0.4
Oracle Client or Instant Client 184.108.40.206/220.127.116.11
Oracle Client or Instant Client 12c
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.
Oracle 8.0.6; 8.1.7; 9i; 9i R2; 10g; 10g R2; 11g, 11g R2, 12c.
Toad has been tested on Oracle Exadata 2.0 running Oracle database 11g R2.
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 databases running on Amazon EC2
|IPv6||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 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 such as /nSoftware's IP*Works that are IPv6 compliant. For access to Web sites by way of the Toad Online window, Toad simply invokes the user-defined or default Web browser.|
Microsoft Internet Explorer 6.0 or later (to view the Release Notes)
Adobe Acrobat Reader 7.0 or later (to view the Installation Guide)
Before installing Toad, review the following for virtualization support:
Citrix XenApp 5.0 and 6.5 have been tested.
|Desktop Virtualization (VDI)||
Quest vWorkspace 7.0 has been tested.
Oracle VM 3.1 has been tested.
VMware ESX Server 3.5 has been tested.
Note: Toad may work in virtualization environments other than the ones listed.
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 local 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 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. Their functionality is therefore limited to the character set of the client on which Toad is running, and NLS_LANG must be carefully set to match the Windows character set.
We have also observed issues with US7ASCII when used with non-Latin characters.
The Toad release package contains the following products:
Toad for Oracle 12.1.1
Note: Toad is available in different editions. The release package includes the edition that you purchased.
Refer to the Toad for Oracle Installation Guide for installation instructions.
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.
Quest Software, Inc.
5 Polaris Way
Aliso Viejo, CA 92656
See our Web site for regional and international office information.
Quest Support is available to customers who have a trial version of a Quest product or who have purchased a Quest product and have a valid maintenance contract. Quest Support provides unlimited 24x7 access to our Support Portal at www.quest.com/support. From our Support Portal, you can do the following:
The guide is available at www.quest.com/support.
Note: This document is only available in English.
© 2013 Quest Software, Inc.
ALL RIGHTS RESERVED.
This guide contains proprietary information protected by copyright. The software described in this guide 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.
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.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
Refer to our Web site (www.quest.com) for regional and international office information.
Quest, Quest Software, the Quest Software logo, Benchmark Factory, Knowledge Xpert, Quest vWorkSpace, Spotlight, Toad, T.O.A.D., Toad World, and vToad are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please seehttp://www.quest.com/legal/trademark-information.aspx