The following is a list of issues addressed and enhancements implemented in this release of Toad for Oracle.
The following list of resolved issues includes issues received from the Toad for Oracle forum and Toad Beta users.
Issue ID | Link to Forum Post | Resolved Issue |
---|---|---|
TMB-2464 | link | Painting issues for unpinned (autohide) dock panels upon startup |
TMB-2454 | link | Resource leaks in script execution status dialog |
TMB-2431 | link | Incorrect recommendation that object name must be double quoted in select create (or alter) object windows |
TMB-2430 | link | Database Health Check fails to run via command line for all connections if only one has a wrong password specified |
TMB-2413 | Changes to a Code Analysis Rule Set are not saved when saving to previously exported Rule Set file | |
TMB-2408 | link | No Explain Plan results in some cases when the Explain Plan table exists in multiple schemas |
TMB-2393 | "Invalid Oracle Home" message shown for instant clients installed to a folder named "bin" | |
TMB-2354 | link | Sequence last cache value is incorrectly reporting the maximum value |
TMB-2340 | link | Error encountered when publishing Java class containing forward slash in its name to PL/SQL |
TMB-2299 | link | Cannot copy individual cell values from the Partitioning tab when viewing a table |
TMB-2297 | Incorrect DDL generated for table having foreign key referencing a view | |
TMB-2272 | link | Cannot edit saved direct connection so that it uses Service Name or SID |
TMB-2271 | link | Incorrect font used for some columns when viewing table data in grid |
TMB-2260 | Export Dataset data masking does not work in some cases | |
TMB-2256 | link | Export Dataset parses SQL file incorrectly in some cases |
TMB-2250 | ORA-00900 when using the Data Masking option with SQL Text dataset in the Export Dataset window and action | |
TMB-2249 | Copy/paste a block selection containing multibyte characters causes exception when pasting | |
TMB-2245 | link | Code navigator when describing a package does not update properly |
TMB-2243 | link | Export Dataset, Excel File format, exports the date 1-1-1900 as a string instead of a date |
TMB-2241 | link | Control alignment/position issues when resizing Session Browser |
TMB-2238 | Contexts, Dimensions, and Policies are not shown in the Schema Browser when connected to a database that does not support Java, e.g. Oracle XE | |
TMB-2226 | link | Data Grid is slow to load for queries having many columns in the result set when Sensitive Data Protection Awareness is enabled |
TMB-2225 | Editor, Toggle Full Screen Grid (Shift+F2) paints poorly and is non-functional in some cases | |
TMB-2212 | link | Export Dataset, Merge Statements, incorrect SQL generated when table primary key consists of all columns |
TMB-2201 | Administer Tablespace window problems (duplicate rows, privilege exception) when connected to Oracle 12.1 container database | |
TMB-2192 | Cannot edit data in grids for index-organized tables | |
TMB-2153 | The "OK" button does not enable when altering a tablespace and changing the maximum size value for a datafile | |
TMB-2146 | Auto-connect not working when more than one connection is set to connect automatically upon Toad startup | |
TMB-2057 | link | Compare Schemas incorrectly flags DEFAULT_COLLATION as a difference and produces SQL error on target database in some cases |
TMB-2034 | link | Window bar buttons do not update connection colors properly |
TMB-2030 | link | Query results take too long to become available |
TMB-2009 | Database Probe hangs on Oracle 11g Release 2 | |
TMB-1973 | link | Data Grid is read-only when executing SELECT from table having XMLTYPE column despite ROWID being returned |
TMB-1970 | Code Analysis results in JSON format specifies wrong object owner in some cases | |
TMB-1948 | link | Analyze Objects window opens to the wrong connection in some cases |
TMB-1918 | link | Export Dataset incorrectly excludes XMLTYPE columns when the option to exclude virtual columns is enabled |
TMB-1872 | Creating an Oracle 18c or 19c pluggable database fails if the container database is non-Exadata | |
TMB-1849 | link | Access Violation generating Explain Plan |
TMB-1818 | link | Duplicate Row in the data grid will hang Toad if followed a Find (Ctrl+F) |
TMB-1808 | link | Rebuild Table changes INTEGER to NUMBER |
TMB-1799 | link | SELECT * FROM TABLE(dbms_xplan.display_cursor) showing unexpected result |
TMB-1745 | link | Compare Files vertical scrolling is too aggressive when the scrollbar is clicked |
TMB-1704 | "Data type not supported" error when viewing cursor output containing TIMESTAMP or INTERVAL fields | |
TMB-1624 | link | Compare Schemas uses DBMS_REDEFINITION to sync tables at times when it shouldn't |
TMB-1609 | Sending PL/SQL from the Set Parameters window to Toad Script Runner for execution passes SQL that is incomplete resulting in error | |
TMB-1604 | link | Explain Plan results in "ORA-01775: looping chain of synonyms" error |
TMB-1587 | link | Windows high contrast option is not obeyed in some windows |
TMB-1552 | "No mapping for the Unicode character exists in the target multi-byte code page" exception upon Toad startup/shutdown |
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.
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:
|
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 |
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. |
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:
|
N/A |
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. |
N/A |
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. |
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. |
N/A |
Known Issue | Issue ID |
---|---|
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 |
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 |
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. |
N/A |
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 |
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 |
Known Issue | Issue ID |
---|---|
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. |
N/A |
Editor options to highlight object names may not work for object names that contain Unicode characters. |
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 |
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 |
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.
Requirement |
Details |
---|---|
Processor |
1 GHz processor |
Memory |
Note: The memory required may vary based on the following:
|
Hard disk space |
|
Operating system |
|
Requirement |
Details |
---|---|
Database client |
An Oracle client must be installed and configured on the system where you are running Toad. The following are supported:
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:
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.
Requirement |
Details |
---|---|
Additional Software |
|
Type |
Details |
---|---|
Application virtualization |
Citrix® XenApp |
Desktop virtualization (VDI) |
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. |
In order to install and run Toad, make a connection, and do basic operations, you must have the following privileges.
Operating System |
Requirements |
---|---|
Windows 7 |
|
Windows 8 and later Windows Server 2012 and 2016 |
|
Note: Other functionality in Toad may require additional privileges. |
To activate a trial
To activate a purchased commercial license
NoteS:
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー