Quest Toad for Oracle
Version 9.7
Release Notes
August 25, 2008
These Release Notes are intended to provide an overview of new functionality and to list many of the fixes that have been implemented in this release of Toad. The Release Notes are also intended to help you upgrade to the new version. For a short summary of new features, also see the "New in Toad" topic in the Toad help file. For an introduction to Toad, please see Toad Getting Started Guide located in the 'docs' folder.
Toad for Oracle 9.7 continues our commitment to providing new features while improving and streamlining existing features and windows. The 9.7 development cycle focused on usability, stability, and consistency.
The Toad Action Palette has been expanded into the Toad AppDesigner. The AppDesigner provides a way for you to apply more fine control on your actions than previously available. Using this and new control actions you can create small Toad applications that automate your processes to a great degree.
You can now generate test data for your databases directly from the Schema Browser, Create Table window, and several other locations. The Trace File Browser provides a way to find and monitor Oracle trace files, and you can now extract code from existing code into a stored or local procedure.
Updates to Toad for Oracle 9.7
New Features in Toad for Oracle 9.7
TOAD version 9.7.2 is provided as a patch with selected fixes to version 9.7. This patch version is not intended to address all reported issues. Rather, it addresses a subset of the issues, selected based on severity and complexity.
During the upgrade from 9.7 to 9.7.2, the UninstallClientFiles.exe is automatically executed during the upgrade. This means that the Authorization key must be re-entered and all user settings (Toad Options, connections, passwords and so on) are lost. You can restore these settings so that you do not have to spend time reconfiguring your Toad desktop.
After you have upgraded to Toad 9.7.2, but with Toad closed:
| COMPONENT | DESCRIPTION |
|---|---|
| File Splitting | Package spec and body saved to same file not splitting when opened in editor |
| Team Coding | Access violation when selecting a third party source code control provider in the Settings component of the Team Coding Status |
| LDAP | LDAP not populating services on 11g client |
| Report Manager | Report Manager not saving TRD files when ending connection |
| Tablespace Script | Error in Tablespace script |
| Upgrading Passwords | Upgrading where user files were previously on a separate volume (D drive, for example), passwords are lost. Includes Citrix upgrades |
| Action Passwords | Action passwords using old encryption format |
| SFTP Download | Hangs at 100% and doesn't stop |
| eBiz Module | eBiz visible even though deprecated |
| FTP | The ftp keep-alive option to refresh every n minutes does not work |
| FTP | Download file does not overwrite if file already exists |
| Schema Compare | When selecting def files as comparison source Toad generates an access violation |
| Schema Compare | Compare option Only Compare Object Names Like not being respected |
| Schema Browser | Grant All on a non-queue table adds queue grants |
| Schema Browser | Table constraint name violation when using Create Like |
| Data Grid | Grid Save As to an Excel file has incorrect date format |
| User Files | File references (i.e Proc Templates and Project Manager files) not updating correctly when User Files location changed |
| Upgrade | Last User Files location not being respected after upgrade |
| Integration | Benchmark Factory scalability issue with test parameters |
| QP5 Formatter | Various bug fixes |
| AppDesigner | Compare Schema action steals focus when Diff Viewer is invoked |
The following is a list of issues addressed and enhancements implemented in this release of Toad for Oracle.
| Component | Description | QCM |
|---|---|---|
| ADDM/AWR Report Generator (DBA) | Toad crashes frequently with errors | 33558 |
| Base | Windows do not refresh / size properly | 34113 |
| Citrix | A Call to an OS Function has failed when minimizing /maximizing Citrix or Remote Desktop | 33917 |
| CodeXpert (Pro/Exp) | CRUD Matrix not displaying retrievals | 33605 |
| Create Database Link window | Creating DB LINKS issues | 33832 |
| Create Materialized Views Log | Issue with create materialized view log wizard in Toad | 34229 |
| DB Menu: Import Table Data Wizard | Excel spread sheet via Import Table Data contains ampersands. '&' becomes "&" | 34061 |
| Data Grid | Error loop when invalid date value is fetched | 33598 |
| Data Grid | Cannot focus a disabled or invisible window | 33820 |
| Data Grid | Data refresh causes List of index out of bounds | 33938 |
| Data Grid | Loading CLOB in grid popup editor slow / crashes Toad | 34187 |
| Data Grid | Grid fails to cancel; fetch causes grid cells to not be selected | 34368 |
| Data Grid | Columns missing in Schema Browser's Data tab | 33811 |
| Data Subset Wizard | Getting duplicate entries in script generated by Data Subset Wizard | 34034 |
| Database Browser (DBA) | Issue with opening the DB Browser without being connected to a Database | 33530 |
| Database Browser (DBA) | Optimizer Hint does not apply when selecting Top Sessions tab (Database Browser) | 33648 |
| Database Health Check (DBA) | Health Check - Alert log checks don't work when scheduled | 34030 |
| Database Health Check (DBA) | Custom report in Report Manager shows comments backward when export report in PDF | 34067 |
| Database Menu: Import | Toad Import Table Data utility imports number of rows incorrectly for Excel | 34012 |
| Database Probe (DBA) | ORA-01455 error when running DB Probe | 32209 |
| Editor | Toad hangs when trying to paste very large package into Editor | 33705 |
| Editor | Editor tab has <no name> after file loaded from disk | 34045 |
| Editor Window: Column/Object dropdown | Code Insight not displaying column pick list if table is accessed via a private synonym | 33783 |
| Editor Window: Column/Object dropdown | Toad hangs when using parameter completion | 33991 |
| Editor: Execute | Overloaded function A/V | 34151 |
| Editor: Explain Plan Tab | Explain Plan prints in black background | 34041 |
| Editor: PL/SQL Debugger (Pro) | RETAINVALUES in code section under parameter window | 34145 |
| Editor: Script Engine | Running a script with F5 hangs version 9.6 | 33830 |
| Editor: Script Engine | Problems with dbms_output | 33987 |
| Editor: Script Engine | Access Violation error and crash when running a query on gV$SESSION | 33918 |
| Editor: Window | Formatting problem with EMPTY and MEMBER OF keywords | 33704 |
| Editor: XML Editor for XMLType | Crash when using CLOB data | 34186 |
| Export File Browser | "Automatically detect schema and name" does not work in Export File Browser | 33814 |
| Find in Files | Find file window in Toad will cover both monitors in a dual monitor environment | 33910 |
| Generate Schema Script (DBA) | Materialized View Log in Export Schema | 34159 |
| Generate Schema Script (DBA) | Create schema script empty files | 34164 |
| Installation | Error 1603 will result if no Desktop found | 33140 |
| New Connection | Toad freezes when pulling up connection screen if already connected | 34168 |
| Object Palette | Object Palette, Schema/Owner-Pulldown menu in the query builder isn't fully shown | 33834 |
| Oracle Tuning Advisor | List Index OOB while dropping jobs | 33260 |
| Oracle Users List | Oracle Users List error | 34004 |
| QB: Reverse Engineer | Join does not show when function is on it | 33786 |
| QB: Save or Open Model | Opening DML returns wrong WHERE clause | 34054 |
| Query Builder | Getting "ORA-00920: invalid relational operator" error in Query Builder | 33984 |
| Query Builder | Query Builder incompatible data types use upper and lower case char with joins | 34179 |
| Rebuild table | Rebuild Table not showing rebuild of triggers when not owned by table owner | 34224 |
| SB Tables: RHS Data Tab | Schema Browser > Table Data tab generates 'qryData: Key field 'ID' not found' | 33942 |
| SB Tables: RHS Data Tab | Schema Browser | Data tab | Select Columns option automatically adds columns | 33955 |
| SB Tables: RHS Data Tab | Create insert for all rows for LONG columns doesn't work in 9.6.1 | 33958 |
| SB Tables: RHS Partitions Tab | Partitions tab on a partitioned table is missing information | 34157 |
| SB: Constraints | Constraint script tab is not showing any content | 33943 |
| SB: Packages | Access Violation error in Schema Browser under specific conditions | 33931 |
| SB: Packages | Clicking on Schema Browser package body hangs Toad | 34170 |
| SB: Procedures | Ref Cursor Result pane does not show TIMESTAMP type | 34265 |
| SB: Roles | Compare Role only displays the first line | 33937 |
| SB: Synonyms | Schema Browser, Public Synonyms, Object Owner heading sort causes hangs | 34044 |
| SB: Tables | Incorrect query being used to determine FK constraints when analyzing chained rows | 33908 |
| SB: Tables | FK constraints in rebuild table | 34018 |
| Schema Browser Navigation | The Image column in the LHS of the schema browser does not go away | 33924 |
| Session Menu | Compile Views in the "Invalid Object" tab versus the "View" tab yield different SQL | 34088 |
| StatsPack Browser (DBA) | '50007279297' is not a valid integer value | 33809 |
| StatsPack Browser (DBA) | Error when viewing Top Waits in StatsPack Browser | 33905 |
| Table Editor: Partitions Tab | Create table wizard doesn't create partitions for IOT | 34248 |
| Team Coding | Team Coding Enabled, choosing "Close All Tabs" results in read-only untitled tab | 33570 |
| View Tablespace Multi-tabbed (DBA) | ORA-22879: cannot use the LOB INDEX clause for partitioned tables | 33620 |
| View Tablespace Multi-tabbed (DBA) | Space History blank but IO History okay | 33782 |
| WINDOW | DESCRIPTION |
|---|---|
| Browser Filters | Filters for all schema-owned object types (except object types and collections) now have an option to filter by schema name, or show objects from all schemas. This feature is not available in treeview mode. |
| Compare Schemas | Compare Schemas has been converted to an action. Settings can be loaded and saved from the window using the snapshot button in the lower left status bar. A new recallable action will automatically be created in the AppDesigner every time a compare schema is executed and can be used (scripted) in the AppDesigner window (formally known as the Action Palette). |
| Compare Schemas | Multiple target schemas and def files can now be defined for comparison. |
| Editor | "Extract Procedure" function added to right click menu, extracts selected text into a new stored procedure, or locally defined procedure. |
| Formatter Plus | Formatter is now 10g and 11g compliant. |
| HTML Schema Doc Generator | HTML Health Check window has been converted to an action. Every time an HTML report is run, it's saved in the Action Palette's "vault" tab so they can be recalled at a later time. Settings can be saved to file using the lightning bolt button in the window caption and can be scheduled to run from the command line in the action palette. |
| Import Table Data | A checkbox labeled "Apply to timestamp fields" has been added to the "Dates Times and Numbers" groupbox. When unchecked (the default), timestamp format is expected to be the same as in your data grids. When checked, the expected format will be the same as date fields (and customizable). |
| Import Table Data | Expression builder added to the dropdown in the verify mapping section. |
| Import Table Data | Option added to import old SMI files from Toad 9.5 or prior. R-click on the "Select source" step to activate this option. |
| Menu Shortcuts | Editor Desktop panels are now included in the menu shortcut list. In order to achieve this, a new flyout menu called "Desktop Panels" has been added to the Editor main menu |
| Multiple Object Privileges | Now supports Queues |
| Object Palette | Tabbed and dropdown modes now offer all of the columns as in the schema browser. R-click the column header to enable. Treeview mode now shows same images as schema browser. |
| Options | Chained rows table option has been moved from the DBA options to Oracle > General. |
| Options | New options in Oracle > General which check Oracle Server/Client versions to ensure compatibility. |
| Options > Editor | Private synonyms added to Code Assist options > Toad Insight Objects list. |
| Options > Windows | New column: Available. Default is checked. If unchecked, the corresponding window will not be available in Toad. Think of it as a way to disable things you never (or don't want to) use. |
| Policy Group Editor | Added restrictions for ADDM/AWR Reports, AWR Browser and the Oracle Tuning Advisor |
| Query Builder | Added support for CASE and DECODE statements in GROUP BY clause |
| Query Builder | Added support for case-insensitive joins |
| Query Builder | Added support for joins between BINARY_DOUBLE and BINARY_FLOAT columns |
| Repair Chained Rows | If specified chained rows table (Options > DBA) is not found on the database, you will now be prompted to create/select one. |
| SB > Indexes | "Rebuild Index" right-click menu item is now enabled for multi-select and passes selected Indices to the rebuild multiple objects screen. |
| SB > Indexes | New right-click menu item added that passes the selected index to the index monitoring screen. |
| SB > Queues | Now has a right hand side "Grants" tab |
| Script Execution | Added ability to remember size for the variables window. The splitter was also resized. |
| Server Statistics | GUI has been updated to use newer grid style. |
| Session Browser | Sub-tabs now automatically switch to the one that is more likely to have data as rows are selected in the top panel. |
| Session Browser | User Locks tabs now have a filter for all locks/blocking locks/block locks. |
| TNSNames Editor | Added support for the "UR" tag located within the CONNECT_DATA tag of a TNS Entry. Support for this is limited to the text editor only. |
| Toad | All user files are now being stored in your user profile directory: C:\Documents and Settings\username\Application Data\Quest Software\Toad for Oracle\X.Y by default. On Vista, your user profiles will most likely be routed to C:\Users\username\AppData\Roaming\Quest Software\Toad for Oracle\X.Y . This was done for several reasons including full Vista compatibility, full support of multiple user profiles, built-in Citrix support, FDCC compliance, and support for roaming profiles. |
| Toad | QSE.dll v1.1.1.1. If using in debug mode for troubleshooting, the qsetrace.log files goes to the user file directory instead of the Toad root directory. |
| Toad | Schedule Script: All the various "Schedule..." buttons which are used to schedule a script for execution (i.e. the create windows) now use Toad instead of QSR. Scheduled scripts can be managed in the AppDesigner (Formally known as the Action Palette). |
| Toad | When session is dropped, the Toad message dialog that shows ORA error now has a reconnect button that performs the "test connection" routine available from the main session menu. |
| WINDOW | DESCRIPTION |
|---|---|
| Compare Databases | Results tabs combined into one. Summary tab information can be found via the toolbar button or r-click menu. The results tab can be saved to html or rtf as well as a text file. The results tab can be sent to excel. The results tab has checkboxes for each item that are checked by default. If the box is unchecked, the item will be removed from the sync script. Database definition files can now be created in the database compare window. |
| Compare Schemas | Results tabs combined into one. Summary tab information can be found via the toolbar button or r-click menu. The results tab can be saved to html or rtf as well as a text file. The results tab can be sent to excel. The results tab has checkboxes for each item that are checked by default. If the box is unchecked, the item will be removed from the sync script. Schema definition files can now be created in the schema compare window. |
| Export DDL | Added two new options to script options tab under Insert Statements: Warn if rowcount exceeds a set number and Warn if LOBS or LONGS exist. |
| Generate Database Script | "Object tree" tab has been renamed to "Object Listing" and has been reworked to include more features such as a toolbar and faster loading |
| Generate Schema Script | "Object tree" tab has been renamed to "Object Listing" and has been reworked to include more features such as a toolbar and faster loading |
| Generate Schema Script | Schema Definition files can now be created on multiple schemas at once |
| Generate Schema Script | Schema Definition files now default to the name_yyy_mm_dd_hh_mi.def, in the user files directory. |
| Health Check | HTML Output now has navigation links and is grouped in the same manner as the treeview. |
| Health Check | Health Check window has been converted to an action. All health check runs are saved in the Action Palette's "vault" tab so they can be recalled at a later time. Settings can be saved to file using the lightning bolt button in the window caption and can be scheduled to run from the command line in the action palette. |
| Health Check | New item: Alert.log - lists trace files with errors. |
| Health Check | New item: Archive results for differences report - Automatically saves health check reports to use files directory. When a health check is run on the same database(s), a new tab "Diffs since last run" displays differences in findings. |
| Health Check | New item: Save differences report to file - Automatically saves differences report to file using the current options set in the "diff since last run" tab. |
| Health Check | Results have been changed from straight text to a treeview with grouping options. |
| SB > Contexts | New tab added to the right hand side for "attributes". |
| SB > Tablespaces | Tablespaces now show usage information on the right side of the Schema Browser when objects are not selected in the left side. This column is also available to add to the left side of the Schema Browser. |
| Trace File Browser | The purpose of this window is to display the contents of an Oracle trace file in a manner that makes them easy to read, easy to navigate, so that problem areas can be quickly isolated. |
| WINDOW | DESCRIPTION |
|---|---|
| CodeXpert | Added email CX reports button to send contents of the results grid as an html attachment. Requires setting CX results e-mail properties in Options -> Email settings. |
| CodeXpert | Added the ability to save the rule set and each rules description to a file. |
| CodeXpert | Minimum 20 ruleset added as a subset of existing rulesets in CodeXpert. |
| ER Diagram | Added data generation functionality |
| SB > Tables | Added Data Generation tab to Create Table wizard |
| SB > Tables | Added Reuse / Drop Storage option to the Truncate Data selection on the Advanced Options tab for data generation. Also, added Transaction Commit Mode option to Advanced Options Tab and moved Truncate Data statements outside PL/SQL block |
| SB > Tables | Added column sorting / incremental search to the Column Options grid in the Generate Data window, added storage size estimates for each table when generating data and added support for CLOB and NCLOB data types |
| SB > Tables | Added support for reproducible data generation and added ability to schedule data generation tasks |
| SB > Tables | New Window - Added support for generating random data to existing tables. This window can be reached through the Schema Browser by right-clicking on one or more tables and selecting Generate Data. Currently, only string, integer, floating point, numeric precision, and date datatypes are supported. Also supported are options to truncate existing data, enforce referential integrity, disable / enable constraints and triggers, and the ability to script data generation to the clipboard and/or Editor. |
| eBiz Module | eBiz menu is no longer on the toolbar by default, even if you are licensed for it. You can easily customize the toolbar to add it back. Right-click on the toolbar and select Customize and then look at the Unused category. |
The following is a list of issues known to exist at the time of Toad for Oracle's release.
| WINDOW | DESCRIPTION | WORKAROUND |
|---|---|---|
| "File not found" error can occur when certain options are in use. | Browsing for a file name using certain browse for file dialogs in opitons unnecessarily adds double quotes to the path which results in error when the option is used. Double quotes are added when the file path/name isn't DOS/8.3 compatible. This issue will not occur if the path/file are entered manually. The following locations are affected: Options > Startup > "File to load on startup" and "File to execute on new connections", Options > Executables, Options > Monitors > "Alert file". | Remove the double quotes added by the browse dialog, or manually enter then path/file name into the field. |
| 11g Oracle ODP.NET client | If a customer uses an 11g Oracle ODP.NET client, located here, http://www.oracle.com/technology/tech/windows/odpnet/index.html, or any client in which the oci.dll is not in the client's BIN directory, but the directory above, Toad has these problems: 1) we show the client as invalid 2) we cannot detect the client version 3) as a result of 2), columns of the following datatypes are not shown in SB-Tables-Data: CLOB, BLOB, NCLOB, XMLTYPE, TIMESTAMP, INTERVAL, BINARY_DOUBLE, and BINARY_FLOAT. The user can work around it by copying oci.dll and oraociei11.dll from <oracle client directory> to <oracle client directory>\bin\. | |
| Install/Uninstall | If uninstalling Toad for Oracle 9.7 on Windows Vista using an extracted msi installer (silent install) while UAC is on, Error 1721 will occur. In this case, Toad will uninstall, but application data files and some registry keys will not be removed. | Turn UAC (User account control) off, or double click on "uninstall.exe" located in the Toad installation directory prior to uninstall. This will ensure all application data files/folders and registry keys are removed. If this error has already been encountered, the best course of action is to re-install Toad back into the same directory where it was installed before, follow the work-around, then uninstall. |
| SQL Optimizer | Toad 9.7 is deploying two versions of SQL Optimizer (6.0 and 7.4) In the next release of Toad for Oracle, v6.0 will not be included as another integration with SQL Optimizer will be provided. If there are any questions or feedback on this, please to go to the SQL Optimizer community to provide comments. | |
| Toad | If using 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 SB-Tables-Data: CLOB, BLOB, NCLOB, XMLTYPE, TIMESTAMP, INTERVAL, BINARY_DOUBLE, and BINARY_FLOAT. | |
| CodeXpert | Saving results to DB: When dealing with nested procedures, CodeXpert can only insert run data from procs one level deep. | |
| CodeXpert | Saving PL/SQL results to database may fail or save invalid data to database for invalid PL/SQL objects. | To ensure PL/SQL results get saved to database correctly, verify the validity of all objects before CodeXpert is run. |
| DBMS Output | DBMS Output doesn't display in the DBMS Output sub tab or the DBMS Output window while debugging or executing pl/sql with debug. | If DBMS Output is enabled in the Editor sub-tab or DBMS Output window, DBMS Output will not show while debugging or executing pl/sql in debug mode unless the following option is checked: View > Options > Debugger > "Enable DBMS Output before debug session" |
| Data Export | "Create Insert for Selected Rows" and "Data Export" from the schema browser are giving the error "No exportable columns found" when "Return object names in lower case from selection windows and drag drop" is checked under Options > Editors. | 1. Uncheck that option or 2. Right-click on the data grid and choose "Save As". Choose "Insert Statements". If you have selected multiple rows and want to only export those, then check "Selected rows only". If you want to put only certain columns in the Insert statements, then you will need to use the right-click "Select columns" function to choose the columns for the grid before going to "Save As" or 3. If you just want to get INSERT statements for a lot of tables, go to Database > Export > Table Data |
| Data Grids | Some users have received the error "invalid rowid" when adding a row to a data grid | The error appears to be linked to the use of Oracle 7 client calls. You are using Oracle 7 client calls if either of the following is true: 1. "SQL*Net compatible Net8" is checked on your Server Login window 2. You are using an Oracle 7 client (Note that "Force SQL*Net" will force TOAD to select the Oracle client on your machine.) We strongly recommend upgrading your Oracle client to at least the same version as the Oracle server that you are connecting to. We also recommend unchecking "SQL*Net compatible Net8" -- the only known advantage of using that setting with TOAD 7.5 is that for Oracle 8.0.x clients, it is the only way to get the error position in the SQL Editor |
| Data Grids | Data does not always display correctly when using an older Oracle Client on a newer Oracle Database. | We strongly recommend using Oracle Clients equal to or greater than the Oracle Databases you are on to ensure data integrity. |
| Data Grids | You may receive an "ORA-00902 invalid datatype" error when editing object, nested table, or varray data if you have redefined the data type for that data during the current session. | 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. |
| Data Grids | Pasting multiple rows of text into a cell will only register the first row of the data. | Paste multiple rows of text into the text editor (popup editor) instead of into the grid cell. |
| Database Probe | Database Probe does not work with Oracle version 8.1.5. | Upgrade to supported Oracle version 8.1.7 |
| Debugger | The debugger is not designed to work with word-wrapped lines, since the editor will then have a different set of line numbers than what is stored in Oracle. | Toad provides a warning message about this if you open the procedure editor while word-wrapping is enabled. To disable word-wrap, go to Edit > Editor Options and uncheck "word wrap lines" under "General". |
| Describe | Viewing XML_TYPE data in the F4 describe window may cause memory leaks. | 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 |
| Editor | 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. | Either: 1. Check Options > Data Grid - Data > Display large numbers in scientific notation, or 2. Upgrade the Oracle client to at least Oracle 8.1.6 |
| Editor | The Editor will jump 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 | If you add "PELineOffsetOverride=1" under the "[SETTINGS]" section in your Toad.ini, it should fix the offset problems, as long as the CREATE OR REPLACE is on the first line of the editor. |
| Editor | Parameter hints for overloaded packages are no longer scrollable. The parameter hint will be limited to the size of your screen. | |
| Editor | ANYTYPE datatype AV in Editor query - If you query a table (in the Editor window only) with a column datatype of "ANYTYPE", an AV occurs. When the Schema Browser accesses views that contain this datatype, the column is suppressed in the results grid. There is no known workaround for this issue. | |
| LDAP Support | 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. | |
| LogMiner | 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. | Upgrade to Oracle version 8.1.7.2.0 or higher, or see Oracle Metalink Note:124671.1 for details of how to fix the package. |
| Multi-file Formatting Results | After running a "Profilce Code", "Check Syntax", or "Format Code" against files in the Project Manager, a results tab appears in the output window. Clicking on an occurence 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 the manor and select "yes" to the Spec/Body file split prompt, your file will be split into 2 Procedure Editor tabs. At this point, selecting an occurence 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 occurence in the Body of the Package will always highlight the last line in the Spec tab. | When loading a package into the procedure edit in this manor, select "no" to the Package spec/body split prompt. |
| Query Builder Reverse Engineering | The Query Builder supports the reverse engineering of queries. SQL Reverse Engineering represents a considerable technological advancement for the Builder. Although it was heavily tested throughout its development lifecycle, due to the vast array of possible queries there may be some queries it can create but cannot reverse. We encourage users to inform Quest if they discover such queries. The main limitations of reverse engineering are that it only supports single-level subqueries in the SELECT and WHERE nodes, and no subqueries in the FROM clause, and some calculated fields that include arithmetic operators might not be reversed correctly. | |
| SB > Procs | Sometimes on Oracle 8.1.7 or higher, after pressing "Compile invalid objects", you may get: ORA-20000: You have insufficient privileges for an object in this schema. ORA-06512: at "SYS.DBMS_UTILITY", line 282 ORA-06512: at line 1 This could mean that you really don't 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. | 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. |
| SB > Tables > Data | -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. | Use drag-and-drop in the grid to change the column order. |
| SQL Monitor | The "Explain plan" options page describes SQL Monitor explain plan's limitations and potential side effects. Mainly, since SQL Monitor has to execute statements, it becomes proactive and can interfere with the program's execution flow. And since it executes statements, the statements may get into the SGA, and there is a remote possibility that they may affect the execution plan of the monitored application's statements. The only 100% guaranteed way of getting the execution plan that was actually used by Oracle for the statement is to turn on server-side tracing and get the plan from there. SQL Monitor is not guaranteed to display the plan that Oracle used, although it should be correct in most cases. | |
| SQL Monitor | In order to monitor services, you must run the SQL Monitor from one of your local drives. If you try to monitor a service while SQL Monitor is running on a mapped or network drive, you will get the message "Error installing monitor for the service process." This happens because services run under the "Local System" account, which can only see local drives. | Install SQL Monitor on a local drive and run it from there. |
| Save As > XLS | Exporting data grid cells of over 800 bytes (est.) could cause "OLE error 800A03EC" for Microsoft Office 2003 users when using the "XLS Instance" option. | Save using the "XLS file" option instead |
| Server Login | 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. | To ensure the proper home is used while logging on, 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. |
| Session Browser | Session Browser does not work with Oracle version 8.1.5 | Upgrade to supported Oracle version 8.1.7 |
| Session Browser | "PLS-00553: character set name is not recognized" error encountered when opening Session Browser | We received this when opening the Session Browser on a 9.0.1 database with a 7.3.4 client. We recommend always using a client version greater than or equal to the server version. |
| 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. | |
| Session Browser | 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. | Uncheck the "Use RAC Views" checkbox, and log into the appropriate instance of the database, if necessary. |
| Snapshot Script | 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. We have not been able to determine a way to tell the difference between indexes explicitly created on the snapshot and indexes automatically created when the snapshot is created. | 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 re-create 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. |
| Team Coding | When you are using CVS as a version control provider, Toad may fail to retrieve the list of projects for you to select from, either in the VCS Browser or in Code Control Groups configuration. | Toad determines which files and folders are in your CVS repository by reading the file named Entries. This normally resides in a folder named CVS under each of your working folders. If Toad cannot find this file in your top-level working folder, or if this file does not contain all the projects, then Toad cannot retrieve all the projects. Please see the "Missing CVS\Entries File Error" topic in Help for details about how to create the Entries file. |
| 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. | |
| Team Coding | When you log into CVS from within Toad, Toad opens a command prompt window to send the password to the CVS server. Sometimes, the command prompt window opens in the background instead of the foreground, and this causes the login to fail. When this happens, the user needs to select "Log in to VCS Provider" from the Team Coding menu or toolbar to re-do the login. The second attempt invariably succeeds. | |
| Team Coding | Team Coding and PVCS: -Integration via the SCC API is available but not recommended for PVCS 6.6 and up. -PVCS 6.6.1 is not supported. In testing, we were not able to get check in and check out to function properly. PVCS 6.6.0 and PVCS 6.7.0, however, worked correctly in testing. -PVCS 6.8.0 is not supported because it has been found to cause a crash in Toad after about 5 to 15 minutes of use. We therefore recommend upgrading to PVCS 6.8.1, which does not have this problem. -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. | A work-around for this problem is to 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 | Most version control providers that integrate with Toad through the SCC API ignore the "Force revision" flag and the "Create a new revision for existing objects" option when exporting. | |
| 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) | |
| Team Coding | 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 ignores ''Create a new revision for existing objects'' option when exporting | |
| Team Coding | Team Coding is disabled for mixed-case object names | |
| Unicode | Toad's data layer does not support UTF8 / Unicode data. Most non-ASCII characters will display as question marks in the data grid and should not produce any conversion errors except in TOAD Reports. TOAD Reports will produce errors and will not run on UTF8 / Unicode databases. It is therefore not advisable to edit non-ASCII Unicode data in Toad's data grids. Also, some users are still receiving "ORA-01026: multiple buffers of size > 4000 in the bind list" messages, which also seem to be related to Unicode data. | |
| XML Editor | The XML Editor has been tested successfully tested with client and database version 9iR2 and higher when the database version and client version match. Some errors in other configurations: With an Oracle 9.0.1 client and any server, XMLType columns will show up as "(ADT)" and be unreadable. With an Oracle 9.2.0.5 client and a 9.0.1 or 9.2.0.1 server, small XMLTypes seem to work, but trying to post an XML over 4000 bytes to a Unicode database yields "ORA-31011: XML parsing failed" even if the data is all English With an Oracle 9.2.0.1 client and a 9.2.0.4 server, attempting to post data causes "two-task conversion" errors or "ORA-31011: XML parsing failed" errors. With an Oracle 10g client and a 9.2.0.5 database, XMLType data shows in the editor as a long string of question marks. These errors seem to be a result of errors occurring at the Oracle client level, which we cannot control. | |
| XML Editor | An extra newline gets added to the value for a mixed-content node when the XML is stored as XMLSchema. A mixed-content node is a node that has a value as well as subnodes. For example, this: <node1>value1<subnode1/></node1> Returns exactly the same when it is in a CLOB or in an XMLType stored as CLOB: <node1>value1<subnode1/></node1> But, when it is in an XMLType stored as XMLSchema, it returns from Oracle to TOAD like this: <node1>value1 <subnode1/> </node1> As you can see, an extra newline appeared after value1. When TOAD posts altered data back to Oracle, that extra newline is posted along with the data (unless you manually eliminate it), and when TOAD then retrieves the data again, Oracle has added another newline: <node1>value1 <subnode1/> </node1> | If you wish to use TOAD's XML editor with mixed-content nodes in an XMLType stored as XMLSchema, then any code you use for parsing will need to be insensitive to newlines at the end of values. |
| XML Editor | "ORA-31001: Invalid resource handle or path name "%s" when trying to post XMLType data that points to a document type definition stored in the XML repository. Even though an insert statement with the same data may work, there appear to be problems with posting these items from the XML editor. | We do not really have a workaround for this. But note that XMLType data that uses a registered XMLSchema for validation seems to post successfully. Also, XMLType data with an inline document type definition also seems to post successfully. |
| TITLE | TEXT |
|---|---|
| 64 bit Windows | When trying to install Toad for Oracle in C:\Program Files\ in 64 bit OS environment, the OS/MSI will convert it to C:\Program Files (x86)\. In this case the install location path in QI is different from actual location. You cannot uninstall Toad for Oracle from QI (and will need to use 'Add & Remove Programs'). |
| Windows 2000/2003 DFS | Windows 2000 / 2003 DFS Needs to be installed by the administrator account (not an account with administrator rights) |
| Citrix support and testing | Citrix versions: Toad for Oracle 9.6 has been tested with Citrix 4.0.1 and is fully functional on a Windows 2003 Server setup. We recommend that the product be deployed via the "Full Desktop" feature in Citrix running on Windows 2003. If the correct permissions and options are set, Toad can be used with the "published application" feature in Citrix as well. |
| Formatter | The code Formatting component, "Formatter Plus" has been replaced with "QP5 Formatter". QP5 will provide support for 10g and 11g syntax as well as additional support for more complex statements. The new formatter also allows us to support future Oralce syntax as new versions are released. While the Formatter options window looks very similar, there are some differences. QP5 formatter will no longer behave exactly like Formatter plus. Running diffs with code formatted by Formatter Plus against code formatted by QP5 will result in differences just about every time. We suggest checking all source code out, re-formatting it with the new formatter, then checking it back in again. This will provide a point in time, one check-in version, which is only for the new formatter. Future diffs won't be affected. Also see the help file for a table of mapped options if previous options can't be easily found. QP5 formatting will also be slower, noticably slower while formating very large files or large sets of files. This is a known issue and performance will increase in future versions. |
| SQL Recall | Toad 9.6 introduces a new technology to load and save saved SQL statements. A conversion to the new format will take place on your first load of Toad 9.6. Performance is significantly faster after the initial cconversion takes place. Conversion of Saved SQL is supported back to Toad version 8.0 |
| Toolbars | As of Toad 9.6, Multiple toolbar configuration support has been removed. All toolbars are always customizable now. On upgrade, you will be asked if you want to restore default toolbar to see new items, or to not do anything and manually add new features to your custom toolbar. If you have been using multiple toolbars with previous versions of Toad, we suggest choosing your most used toolbar and making sure it is in use before you upgrade to Toad 9.6. This way, you can keep your favorite toolbar customization and add new windows manually after upgrade. |
| Desktops | Due to the Editor merge and the addition of new functionality in Toad 9.0, we can no longer preserve old desktop layouts from previous versions of Toad. All previously saved desktop layouts for the main Toad desktop and the Procedure/SQL Editor desktops will be overwritten to the new default layouts. Once Toad is upgraded, users are advised to add customizations back if they wish. |
| Editor Toolbars | Due to the Editor merge and the addition of new functionality in Toad 9.0, we can no longer preserve old SQL Editor and Procedure Editor toolbar layouts if upgrading from previous versions of Toad. Since the 2 Editors have been combined into a single Editor, there was no way for us to determine which toolbar to preserve. In addition, new toolbar items available in the single Editor would not be seen for upgrading users. |
| Toad Main Menu | The Toad menus have been completely restructured for Toad 9.0. The new Session menu contains session-specific items such as creating and ending connections and anything else that can modify specific connections. The Database menu has been greatly expanded and generally contains all of the Oracle functionality, arranged by function. The new Utilities menu contains non-connection/Oracle windows for the most part, such as Network Utilities, Archive, and FTP. In the Files menu, you will now find items that operate on files only. The View menu toggles the visibility state of dockable windows along with a few other items that fit nicely in that category. The Search menu contains all search-related functionality from searching text to Oracle object search. The Edit and Grid menus have been left untouched. The "SQL Editor" menu has been renamed to "Editor" menu and the debug menu has not changed with the exception of removing items whose only function was to toggle the visibility of Editor sub-tabs. |
| Editor Options | Toad now uses a new Editor component, therefore not all pre-9.0 Editor options could be preserved on upgrade. The new "Auto Replace" and "Code Templates" options will recognize your pre-9.0 configurations and will not be lost when upgrading. As for the rest of the old "Editor options" (linked from Toad's main options screen in previous versions), they are now merged in with the other Toad options. The options in question will now revert back to the default settings as if you were re-installing Toad. For example, any custom Editor key mappings that were set for previous Toad versions will not be remembered when you upgrade. The key mappings will be set to match the defaults for Toad 8.6 |
| eBiz Reports | As of Toad 9.0, eBiz Reports, which used to reside in the "eBiz" menu have been moved to Database > Reports > Reports Manager |
| Script Execution and DBMS Output | The script execution is an almost identical replacement for SQL*Plus so all script output will go to the script output tab in Toad 9.0. As with SQL*Plus, to see DBMS Output while running a script, a 'SET SERVEROUTPUT ON' command will have to appear at the beginning of your scripts. For frequent use of the server output command, we suggest adding this to your login.sql file. |
| Editor Key Mapping | As of Toad version 9.5, all custom Editor key mappings will be restet to defaults. Any customizations made in this area will have to be manually re-applied after upgrade. |
| Command Line Execution | As of Toad 9.1, some command line parameters have been desupported and changed to the standard convention, such as -c to connect, -min to minimize window, -max to maximize and -f to load files. |
| Parser and Syntax Highlighting in Editor | Due to the Editor merge and the addition of new functionality in Toad 9.0, we can no longer preserve custom syntax highlighting, or any other parser customizations made to Toad's pre-9.0 parser files. |
| Editors Merge | In Toad version 9.0, the SQL Editor, Procedure Editor, and Text Editor have been merged into a single Editor. The new Editor features context sensitive execution (F9 key or green arrow button). The new execution routine can identify the statement at your caret and perform the correct execution action when a single Editor tab contains heterogeneous statements. PL/SQL can also be compiled directly from the Editor's navigator panel via the Right-click menu. Script Execution is still available in the new editor as well as 3 debuggers (PL/SQL, JDWP, and Script). Only 1 debugger may be used at a time, use the "debug" main menu to switch between debuggers. "Execute Statement at cursor" is still available via Shift+F9, Ctrl+Enter, and the button may be added back to the toolbar using customizable toolbars. The new Editor now has 5 different "Tab Styles" that are used depending on what you are doing in the Editor. For example, if "XML" tab is selected, the tab will be in XML editor mode using the HTML parser and an XML tree will appear. Tab styles are also associated with a Desktop layout and file extensions. |
| Options | Due to the Editor merge and the introduction of a new Editor component, there has been some significant options re-work throughout Toad. For example, options previously found in the stand-alone "Editor Options" are now included with the rest of the Toad options. All of the old SQL Editor and Procedure Editor options have been moved and reorganized to be more intuitive with the single Editor. The best way to find the option you are looking for it to use the Options window's search function. |
| Team Coding | If you plan to use Team Coding, we strongly recommend that you check Options > Editor > Execute/Compile > Toggle modified flag after compiling source loaded from database. The option defaults to checked in TOAD 7.5, but it is remembered from your previous installs, where it defaulted to unchecked. If the option is unchecked, then switching tabs or windows will disable check-in until you compile again. |
| Number of Bugs Fixed | 66 |
| Number of Enhancements | 59 |
| Number of Known Issues | 45 |
Before installing Toad for Oracle, ensure your system meets the following minimum hardware and software requirements:
Hardware
Software
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 supports any single-byte character set. Double-byte or multi-byte character sets are not supported. 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 locale 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: Updating multi-byte or bidirectional character data, exporting multi-byte character data to excel. Visual display in some grids/views.
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 here.
| info@quest.com | |
| Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA 92656 USA |
|
| Web |
Refer to 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 commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global Support Guide.pdf.
© 2008 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software described in this document 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.
If you have any questions regarding your potential use of this material, contact:
|
Quest Software World Headquarters
LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656
Email: legal@quest.com |
Refer to our web site for regional and international office information.
Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.
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.