Quest Toad for Oracle
Version 9.6.1
Release Notes
April 14, 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.6 continues our commitment to providing new features while improving and streamlining existing features and windows. The 9.6 development cycle focused on stability, usability, and consistency.
The debugger has been moved from the Professional Edition to Standard Toad. In addition, the TNS Names Editor has been streamlined and made easier to use. For users who also license the Quest Code Tester, you can now send your code to the tester with a click of a toolbar button.
In the Toad Professional Edition, the Code Xpert has a new metric (the Toad Code Rating) that will give you a quick way to judge the results of the analysis.
In the DB Admin module, Flashback Archives support for Oracle 11g has been added to the Schema Browser, database level objects have been added to the Database Browser, and an AWR Browser has been added following the template formed by the Statspack Browser in Toad 9.5.
An issue was uncovered wherein executing/debugging multiple procedures within a PL/SQL package was problematic.
Only one sub-program could be run at once within a given package or debug session. Once the first sub-program was executed/debugged, the user could no longer execute/debug any other sub-program within that package.
Toad for Oracle version 9.6.1 remedies this issue.
NOTE: This patch version is not intended to address all reported issues. Rather, a specific high priority issue.
| Number of Bugs Fixed | 1 |
| Number of Enhancements | 0 |
| Number of Known Issues | 0 |
Updates to Toad for Oracle 9.6
New Features in Toad for Oracle 9.6
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) | Error when attempting to save addm.ini file | 33160 |
| Action Palette | Access Violation in Action Palette when history is full | 33024 |
| Compare Schemas | Schema Compare showing differences when they should not be shown | 33020 |
| Compare Schemas | Table without supplemental logging listed as not existing | 33150 |
| Compare Schemas | Loading Schema Compare scripts problems after upgrading | 33218 |
| Compare Schemas Settings | Compare schema with DBLInk and "SQL*Plus 'prompt' comments in script" is invalid | 30995 |
| Create Script for Table | Rebuilding table leaves ON DELETE SET NULL option off foreign keys | 33124 |
| Create or Alter View | View script creates 'alter table' command not 'alter view' for views with pk | 33444 |
| DB Menu: Import Table Data Wizard | Not all columns visible for mapping if file column names do not match table's | 33041 |
| Data Grid | Data Grid: Date error response (more user friendly message) | 33191 |
| Data Grid | Hitting CTRL-END twice in results grid hangs Toad | 33368 |
| Data Grid | '...' button appears for BLOB columns in Data Grid | 33202 |
| Data Grid | Schema Browser List index out of bounds when sorting | 33353 |
| Data Grid | Unable to copy row from the data grid | 33216 |
| Data Grid: Excel Style Filter | Sorting a column after applying a custom filter to a different column loses filter | 33146 |
| Data Grid: Single Record View | Column labels disappear in SRV on Vista | 33029 |
| Data Grid: Single Record View | Single Record View|Save|Favorites causes view to be brought to front, no focus | 33131 |
| Database Browser (DBA) | Browser does not populate LHS with entries that have HOST and PORT in lowercase | 33067 |
| Database Health Check (DBA) | Not recognizing second node's alert log on a two-node 9i RAC | 33108 |
| Database Menu: Administer | Sort on the Tablespace window and exporting to an Excel file, corrupted data | 33397 |
| Database Menu: Create | LIOOB when creating external table | 33139 |
| Database Menu: Create | Create Index Compute Stats option not added in with Bitmap option | 33342 |
| Database Menu: Diagnose | Log switch frequency map seems to show the incorrect number of logs cut on Oracle RAC | 33232 |
| Database Menu: Monitor | Database Monitor does not display statistics for a 10.1.x database | 33341 |
| Editor | Some characters in files cause errors upon opening in Editor | 33079 |
| Editor | DESC (F4)on non-existent DBLink resulted in application error | 33311 |
| Editor | Tab names in editor not being updated with new filename | 33292 |
| Editor | Running DBMS_SQLTUNE.execute_tunning_task() returns ORA-13605 & ORA-06512 | 33266 |
| Editor | Error "Unknown commit action. Rolling Back" after upgrade from 9.1 to 9.5 | 33162 |
| Editor | Create Constraint Window not refreshing Table drop down menus | 33340 |
| Editor | Access violation using SQL style tab, but not using text style tab. | 33478 |
| Editor Options: Code Assist | "Display pick list after typing object name..." option not obeyed when unchecked | 33132 |
| Editor Window: Column/Object dropdown | Constants chosen from pick list are wrapped in double quotes. | 33015 |
| Editor: DBMS Output Tab | DBMS Output not handling NULL correctly | 33111 |
| Editor: Execute | Alter index cannot run as statement in 11g if it has a terminating character | 33159 |
| Editor: Execute | Strings to lowercase when EXEC used in a procedure | 33206 |
| Editor: Explain Plan Tab | Explain Plan error ORA-00942 in Session Browser When Viewing Open Cursors | 33486 |
| Editor: Load Object from Database | Option to always include schema name non-functional when $ is in object name | 33018 |
| Editor: Navigator Panel | Navigator panel text is inconsistent | 33022 |
| Editor: Script Engine | Overflow error results despite all DBMS output off | 32493 |
| Editor: Script Engine | Blank lines inserted in spool file between select and "no records found" | 33116 |
| Editor: Syntax Parser | Error when sorting on grid that used REGEXP_LIKE (10g) | 33149 |
| Editor: Watches Tab | A watch added from the watch tab does not work in some instances | 33058 |
| Generate Schema Script (DBA) | Getting a memory error when generating script for large schema | 33042 |
| Generate Schema Script GUI | Table definitions extracted unexpectedly from definition file | 33057 |
| Grid Menu: Flat File Export | Timestamp format in flat file export | 33153 |
| New Connection | Auto connection caused error in 9.1/9.5 | 33229 |
| Object Palette | Object Palette, Unpinned to right side, missing slide bar, erratic behavior | 33298 |
| Pinned Code (DBA) | Sort triangles are reversed in column headers | 32977 |
| SB Tables: RHS Data Tab | AV when closing Toad with a Blob Edit dialog open and on top | 33167 |
| SB Users: Lock/Unlock/Expire User | Toad not prompting for password change | 32972 |
| SB: Auto refresh details option | refreshing all the lists in the schema browser AV error | 33193 |
| SB: Constraints | Suggest button not providing suggestions from SB|tablename|Constraints | 33477 |
| SB: Jobs | Single Quote Escape in Sched Job(Toad For Oracle 9.5) | 33485 |
| SB: Packages | R-click and saving packages to file adds extra file extension | 32473 |
| SB: Roles | Access Violation when debugging trigger with timestamp | 33069 |
| SB: Tables | Save as Excel CLOB issue in Columns tab | 33294 |
| SQLab | Cannot connect to SQL Optimizer when logged in as SYS | 32967 |
| SQLab | Toad to launch QSO | 33210 |
| Schema Browser | "In memory object list filter" in schema browser with lots of procedures | 33290 |
| Schema Browser Tree View | Schema Browser in Tree View AV error | 33300 |
| Tablespace Datafile Definition Window | Error when adding a datafile to a mixed case tablespace name | 33093 |
| Top Sessions (DBA) | Error when saving grid contents | 33095 |
| Component | Description |
|---|---|
| Action Palette | Added Import Table Data as an action. A new tab for imports appears in the palette. |
| Action Palette | Actions can now be drag-dropped from one action set to another. Hold down the CTRL to copy actions, otherwise they are moved. |
| Compare Schemas | New option added to exclude double quotes while comparing object source |
| Editor | Code Insight has been reworked. Support for more objects has been added to now include types(with attributes and methods), tables (with columns), views (with columns), functions, procedures, packages (with methods), java source, sequences, users, and public synonyms for all aforementioned object types. The Object list is customizable in options > editor > code assist. Other notable features include the ability to drill down into other schemas, object list caching, and DOS style auto-complete (shift+tab). |
| Editor | Formatting of XML tabs is now permitted even if the tab is Read Only. |
| Export DDL | New option available to not include schema in the filename when exporting to one file per object. |
| Export DDL | New checkbox in output section: "lowercase file names" |
| Import Table Data | Converted the wizard to an action. The "Execute Wizard" button is gone, all of the steps are built into the main window. The "Clear wizard settings" button is gone, it's no longer needed. The truncate/disable/enable options still exist in their manual forms on the first step, but they've also been added as automatic pre and post import items on the last step. The save/load specifications buttons are gone. They are no longer needed since you can now just save the action. If you rt-click a table, view, or MV from the schema browser to launch the import wizard, all settings from the last time you imported to that object are remembered, assuming the action was saved or is still in the vault. |
| Options > Editor | Editor options > Behavior: The languages options section has been expanded to include 3 new shortcut buttons for Code Templates, Syntax Highlighting, and Editor Font. |
| Options > Editor | New Code Assist option allows code insight results to be cached per unique connection string. |
| Oracle Tuning Advisor | New window added: Database > Optimize > Oracle Tuning Advisor. This window comes complete with a "create tuning task" window which can also be invoked from multiple areas of Toad, including the Editor (tuning fork button). The Oracle Tuning Advisor window allows you to report on existing tuning tasks and also allows you to browse and create SQL Profiles (SQL profile creation script only available on 10gR2 or higher database). An extra tab is available on 11g for configuring auto tuning parameters. |
| Quest Code Tester Integration | New button in the Editor and R-click in Schema Browser allows code to be tested with Quest Code Tester if the object has a pre existing test created with this application. Results are displayed in a popup window. |
| SB > Data Tab | "Auto refresh" right click option added to data grid navigator toolbar (R-click on VCR buttons). |
| SB > Tables > Data | Toad now automatically adjusts OC_ARRAY_BUFFER_SIZE for optimal fetch performance to prevent "out of memory" errors. |
| Schema Browser | Cleaned up the configure LHS object type dialog by bringing it up to date and added the ability to save and load configuration sets. |
| Schema Browser | R-click option added to Object lists toolbar to hide the current object type. Object types can be added back via "Configure LHS Object Types" item under the Browser Style dropdown button. |
| Server Login | If a password has expired within a grace period, a dialog will appear saying the password will expire within x number of days. |
| Single Object Comparison | A "columns only" checkbox has been added to compare only column lists for tables, views, and mat. views. This option also has a checkbox to list columns in alphabetical order. |
| TNSNames Editor | Added minimize/maximize capabilities to the editor window, save the editor window size and state when closing, select the address tab when clicking Edit on a Host Address, preview window now displays the parent node's entry if a host is selected, and clone a tns entry within the add/edit service window. |
| Table Editor | Added ability to specify flashback archive for table (11g) |
| Component | Description |
|---|---|
| AWR Browser | Much like the StatsPack Browser except that it browses AWR (Automated Workload Repository) data. Uses a series of graphs and data grids to depict DB performance metrics. |
| Compare Databases | Users to compare section added to options tab to compare users with or without objects |
| Database Browser | Nodes for database-level objects (tablespaces, users, roles, etc) have been added under the database-level nodes. When database-level nodes are selected, an imbedded Schema Browser will show for that object within the Database Browser. Schema level objects can also be browsed via an imbedded schema browser by selecting the "Schema Objects" database-level node. |
| Database Browser | Option added to have multiple Database Browser files. Database Browser files are lists of left hand side items. This file can be recreate from the current tnsnames.ora file, copied from your current file, or imported. |
| Health Check | "Vulnerability Assessment" section added with 22 new checks |
| Object Search | Added ability to search for Flashback Archives |
| Schema Browser | Flashback Archives tab added for 11g Database along with Create/Alter windows. |
| Schema Browser | Packages, Procedures, and Functions tabs: The corresponding left hand side node will become selected as the cursor moves around the right hand side source tab. |
| Component | Description |
|---|---|
| CodeXpert | Added new metric - Toad Code Rating (TCR). For each code metric, a value is assigned based on the color scale. Red = 4, Orange = 3, Yellow = 2, and Green = 1 |
The following is a list of issues known to exist at the time of Toad for Oracle's release.
| Component | Description | Workaround |
|---|---|---|
| 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. |
| Data Grids | Grid scrolls horizontally back to focused cell when scrolling vertically | Select a cell in the visible part of the grid before scrolling vertically. |
| 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 | |
| Formatter Plus | As long as the FmtPlus.dll exists in the Toad directory, Toad will read its formatting options from there, even if there are other installations of Formatter Plus on the machine | This behavior is meant to ensure that the version of the FmtPlus.dll that Toad is loading will be high enough. If you have Formatter Plus version 1.4.0.6 (FmtPlus.dll version 4.8.0.23) or higher in another place on the machine and you would like Toad to use the options there, uninstall Formatter Plus from the Toad directory and manually delete the FmtPlus.dll from the Toad directory. |
| 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 "Profile Code", "Check Syntax", or "Format Code" against files in the Project Manager, a results tab appears in the output window. Clicking on an occurrence 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 occurrence 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 occurrence 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 now supports, for the first time ever, 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 | 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. |
| 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. |
| 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 | |
| Toad Help | Toad Help file no longer opens for Network installs. Microsoft security update 896358 disables ActiveX Components, which renders the Toad help file useless for network installs. | Copy the Toad help file (Toad.chm) from the server to the client and change the following Toad.ini (located in main toad directory under the "User Files" folder) entry to point to the new location: [SETTINGS] HelpFileDir=C:\Program Files\Quest Software\Toad for Oracle 8.6 Client |
| 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. | |
| Windows Vista Support | If you install Toad on Windows Vista with UAC (user access control) enabled, you may encounter file access errors | Turn off UAC. If you don't have permission to do this, then when files are not found, such as lexlib.lxl, files may need to be renamed and/or moved to other locations. In the case of the lexlib.lxl error, you must copy this file from your local profile (where vista redirects your data) to your install directory \user files folder. |
| 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. |
| Component | Description |
|---|---|
| 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. |
| Editor Key Mapping | As of Toad version 9.5, all custom Editor key mappings will be reset to defaults. Any customizations made in this area will have to be manually re-applied 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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 |
| 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 |
| 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 | 63 |
| Number of Enhancements | 29 |
| 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.