SQL Navigator® for Oracle

Version 6.1.0 Release Notes

Release Notes

November 2008


Contents

Welcome to SQL Navigator for Oracle 6.1.0

New in this Release

Getting Started

Resolved Issues and Enhancements

Third Party Team Coding Support

Support of the Euro Character

Support of Oracle features

Known Issues

Third Party Provider Known Issues

System Requirements

Global Operations

For More Information

 


Welcome to SQL Navigator for Oracle 6.1.0

Thank you for installing SQL Navigator® 6.1.0, the Professional Oracle Development Environment of choice for thousands of developers and corporations worldwide.

SQL Navigator provides an integrated environment for developing and testing stored programs, schemas, SQL scripts, and more - all from an easy-to-use graphical user interface. The SQL Navigator® family of products is a complete development environment for Oracle server-side development and management. It has been conceived, designed and developed by Oracle developers and DBAs with hands-on experience in the most common problems facing Oracle developers.

 

View the latest Release Notes containing late-breaking information and known issues about SQL Navigator®.

 

We trust you will find that SQL Navigator® significantly improves your productivity, so that your projects are completed faster with a higher level of quality than ever before.

 


Getting Started

Contents of the Release Package

The SQL Navigator® for Oracle release package contains the following products:

  1. SQL Navigator® for Oracle 6.1.0
  2. Knowledge Xpert for PL/SQL 10.1.0
  3. Quest SQL Optimizer for Oracle 7.4.1
  4. SQL Monitor 2.4.3
  5. Product Documentation, including:


A "ready to print" copy of the Users Guide, Users Guide Supplement and Getting Started manuals are provided in Adobe Acrobat format (also available from Start Menu). If you do not have a copy of Adobe Acrobat installed on your system, please visit http://www.adobe.com/. Printed manuals are available for purchase from our e-Store at http://www.quest.com/ (navigate to the SQL Navigator® page).
 

On the installation CD we have also provided several "Tips & Tricks" articles to help you get the most from SQL Navigator®. To view additional Tips as they are added, please regularly visit our SQL Navigator Inside Community.


Installation Instructions

Refer to SQLNavigator_InstallationNotes.htm for installation instructions. 

 


New in This Release

 

New Features in SQL Navigator® 6.1.0

        From the Session Browser you can:

 

New Features in SQL Navigator® 6.0.0

 

Updates to SQL Navigator® 5.5 

New Features in SQL Navigator® 5.5 

 


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of SQL Navigator® for Oracle: 

View the latest List of resolved issues and enhancements for this release

Area

Resolved Issue

Defect ID
General
Knowledge Xpert  is now part of the Standard Edition     
Incorrect Extract DDL, when object type is altered CR95865/ Case 291012
Extract DDL does not include NOLOGGING keyword. CR53676/ Case 189992
Extract DDL of Java classes - '/' is included as the separator character CR77381/ Case 247141
Extract DDL creates system generated constraints when it should not. CR94377/ Case 286926, 287262
Extract DDL for table shows SYNONYM incorrectly, if it's created by another user CR98168/ Case 298000
Separator character ';' problem in Extract DDL for packages. CR119442/ Case 330949
Extracting DDL doesn't include system named check constraints CR225675/Case 550196
Extract DDL on Spatial Indexes generates incorrect syntax

- CR120123/ Case 331487

Cannot open Clipboard error message and "Invalid Pointer Operation"
CR209268/ Case 498537, 623219
Release 5.5: Server output is not displaying dbms_output messages.
 
Add preference not to display the SQL Navigator splash screen
- CR 232442/Case 621602, 509979
Check for updates has been added.  
Query Builder Conversion Utility is not retaining the column schemas. - CR228233/Case 572212
Allow to save Workspace on Terminal Server/Citrix - CR110444/ Case 319204, 330144

- CR0091042/ Case 277829

- CR0068456/ Case 225016

View Difference doesn't work when the same objects from different instances are compared. CR212451/ Case 502612
View Difference without OWNER CR214014/ Case 519825
View Differences fails for objects outside the session schema CR213678/ Case 516102
View Differences - can't compare objects from another schema CR209509/ Case 506261, 51500, 530807
Add support for Visual Studio 2005 Team Foundation Server - CR214152/ Case 520605

- CR 221239/ Case 541215

Find and Replace: Find Next (F3) stops working CR211591/ Case 514151
Error: "Quest Software IE plug in protocol: Unable to locate QCOM service CR221377/ Case 539939
Auto hide functionality of dock-able windows not working correctly CR212223/ Case 515402
Floating dock-able window shifts when display.  
Connectivity Support connection to 11g DB.  
Add LDAP support for Active Directory  
Code Editor Split windows feature has been added. CR194150/ Case 464090
SQL NAV Stored Program Editor uppercases the module name CR 100284/ Case 474256
Problem when displaying numbers and dates CR199961/ Case 478297
Allow a "Save As" for extracted DDL file to use as default only object name without schema prefix. CR214300/ Case 513067
Running multiple SQL as a script, doesn't place results in separate Tabs for each SQL, despite having preference set on. CR209849/Case 506112
Release 5.5: Server output is not displaying dbms_output messages CR207094/ Case 493284
Oracle Query: FieldAsInteger: '3601815192' is not a valid integer value CR204053/ Case 491413
Out of Memory when parsing a large subquery factoring WITH...AS SELECT sql statement CR0171670/ Case 411645
Problems when doing a SELECT in SQL Navigator that includes a CLOB column CR132684/ Case 349733
Parsing and formatting error with special packages CR119892/ Case 332909
ORA-01455, when querying database from 9i client on XP CR102922/ Case 303524
ORA-03130, when viewing CLOBs in Oracle 9.2.0.4.0 patch (OCI issue) CR0065494/ Case 211195
LONG data type editor truncates Return char when data modified on grid CR0063452/ Case 206784
SQL Nav 4.1.2, Vertical Scrollbar Changes Focus on Data Grid Cell CR0096080/ Case 129375, 405016, 537235, 537212
Sqlnav4 trims strings in dynamic sql if slash "\\" is followed by pipe "||" CR124762/ Case 337596
Not passing the parameters when trying to debug CR144732/ Case 359263
Font in the Data grid is same as UI, should be different. CR167791/ Case 415286
Extend functionality of code completion to include object names (i.e. TABLE emp, when half-typed, a list of tables beginning with "em" should be displayed). CR176582/ Case 427682
Indication of the parenthesis disappears as the page is scrolled up. CR178485/ Case 434217
Add support in Code Editor for the SQL*Plus command SPOOL ON/OFF CR219350/ Case 532578
Double click on gutter selects only 106 characters of a line in Stored Programmed editor CR54599/ Case 186121
Pick list in Code Completion displays objects indiscreetly, if char is typed in. CR69780/ Case 229062
Some procedure names in Code Explorer are shown in red, despite being VALID CR71541/ Case 233410
SQL Navigator - Stored Program Editor Hangs After Compiling Package CR117478/ Case 327718
Rollback from Session menu or/and from Main sqlnav5 Toolbar requires Refreshing CR144494/ Case 366395
Statements with colons fail when executing CR161813/ Case 402935
Allow SQL Optimizer to be launched from within SQL Nav without typing in first the SQL statement CR180786/ Case 438928
Trigger (on Insert) doesn't insert data on NOT NULL column, if action is performed from grid - error message "Field filed name must have a value" CR171749/ Case 422396
Add "Outline" on side of editor displaying code structure CR194827/ Case 467278
Out of memory error when executing query CR200651/ Case 471289, 609411
DBMS_OUTPUT>>>>: Output windows not working & can't run multiple sql statements CR215100/ Case 522547
Decimal rounding issue>>>Result Displayed in Decimal CR216218/ Case 518752
Add preference to display on the grid NULL for Null Values - CR86644/ Case 268739

- CR105277/ Case 311260

Error "Invalid time display option" in SQL Editor, while debugging. CR217924/ Case 502963, 589386, 625684
Indenting indents one row too much CR170445/ST1990/Case 419771
Code Completion drop down list enhancement request. CR59496/ ST1884/ Case 200249, 207705
Syntax Highlight of JOIN Keywords CR169760/ST1989/ Case 418166
In Stored Program Editor, double click on invalid component doesn't navigate to Body. CR61146/ST1885/ Case 204210, 425064
SQL Navigator hangs after compiling package CR216587/ CR 519190
Set height of Code Editor window bigger as default CR184279/ST2024/Case 441630
When focus is on date field in "View Single Record" date format changes - user cannot copy & paste the required format. CR149206/ST1937/Case 373773
Issues with the large size of sql history .hst file. In 6.0, no longer use the .hst format CR149245/ ST1938/Case 366680
Allow to View longer text in Single View of Results pane of SQL Editor CR149622/ST1941/ Case 367664
SQL Navigator freezes during a query when table contains 292 columns CR194153/ST2087/Case 465202
ORA-01481 when using ROUND function within TO_DATE function of select statement, when Updateable is ON. CR193403/ST2082/Case 463201, 606278
Getting error message: Task "SQL Editor Execution" in DoTerminate(): Stream read error CR158703/ST1955/Case 381638, 571716
SQL Navigator crashes when selecting multiple rows in grid and doing Ctrl+C repeatedly. CR188132/ST2069/Case 445998
The numeric data is not sorted correctly in data grid. CR212456/ Case 504998
Code Explorer reporting the incorrect status CR175669/ST2000/Case 437324
Extend Code Completion and Dot Lookup functionalities to allow to the Code Explorer reporting the incorrect status on table names in progressive search.

CR182711/ Case 442040

Installation Using the Quest Installer which support silent, push and side by side installations.  

Third Party Team Coding Support

SQL Navigator's Team Coding module directly supports the following products:



Team Coding will also operate with certain products providing Microsoft's SCC API. Implementation of this interface varies between products however. The products tested with, and supported by, SQL Navigator® include:

 


Each third party product may require a custom installation to install the SCC interface. Please refer to the topics "Installing Team Coding options" and "Installing third-party version control products" in the Online Help, as well as documentation supplied by the vendor. There may also be a SCC interface installer available on the vendor's website. 


Please note that a Third Party Version Control product is not a requirement for Team Coding - all functionality except for revision history (Version Control Browser) is always available if Team Coding is enabled.


Using User Mapping with Triggers and Views 

If you are using User Mapping (please refer to Online Help for details), Team Coding must modify the DDL in order to create the object in the User's schema. This primarily involves replacing any references to the original schema. For example, consider the DDL for the following Views: 

            create or replace VIEW scott.vemp1 as select * from scott.emp;

            create or replace VIEW scott.vemp2 as select * from emp;
 

The DDL which will be executed during import, Get Latest Revision, etc. will be modified to: 

            create or replace VIEW otheruser.vemp1 as select * from otheruser.emp;

            create or replace VIEW otheruser.vemp2 as select * from emp; 

In both cases, the referenced table must exist in the other user's schema, or the view will be invalid. In the case of triggers, it will not be created by Oracle. If you require that the triggers and views refer to the tables in the original schema, we recommend creating synonyms for them in the other users schema. 

Note: Schema replacement affects all objects maintained by Team Coding, so it is possible that explicit schema references in any stored program may result in invalid objects when using User Mapping


Accessing Triggers from a different user
 
When using Team Coding to manipulate triggers as a user other than the owner of the objects, certain steps must be followed prior to performing check in/out operations. Failure to follow these steps will lead to errors such as "ORA-00942: table or view does not exist". 
  1. The steps to avoid this problem are as follows. They should be performed before creating any revisions in your Version Control provider's repository; however, they can be performed at any time:
  2. When connected as a user with Team Coding Administration privileges, ensure that the Team Coding connection setting "Use Trigger Description for DDL" is enabled.
  3. When connected as any user with access to triggers, use the Find Objects Tool or the Details Panel of the DB Navigator to select all triggers mapped to a Team Coding group
  4. From the Object menu/toolbar or pop-up menu, choose Extract DDL.
  5. In Extract DDL Preferences, ensure that "Prefix with Schema Name" is enabled, and that "Show Trigger Snapshot" is not enabled, then click OK
  6. Execute the generated script.
  7. From the Code Control Groups window, perform an Export of your triggers to your Version Control provider project. Ensure that the "Create a revision only if the object has changed" option is enabled.

Following these steps will ensure that the original schema name is stored in the DESCRIPTION column of the ALL_TRIGGERS view, and that Team Coding will use the original DDL text rather than generating the DDL from the other columns of this view. Subsequent use of Team Coding operations which replace the trigger will perform correctly. Functionality affected includes Get Latest Version,  Check In (with the preference "Update database after Check-In" enabled) Import and Export (with the preference "Update database after Check-In" enabled).

Note: if the trigger owner using the Trigger Editor subsequently modifies a trigger, the DDL generated does not include the schema, which will re-introduce this issue. It is recommended that for this release you do not mix trigger modification between trigger owner and other users if Team Coding controls the trigger.

Finally, the CREATE ANY TRIGGER privilege is required for User mapping or when modifying or importing a Trigger as a different user. The SELECT privilege may also need to be granted to users creating views in different schemas for the table referred to by the view.                                                                                                                                                                  

Back to Top

Support of the Euro Character


SQL Navigator® 6.1.0 provides full support of the Euro character (€). The default fonts permit the Euro character to be displayed or entered in all areas of the SQL Navigator® user interface. Support of the Euro can however be affected by user configuration, such as choosing a font set which does not include the symbol. It is also dependant on operating system, Oracle client and Oracle server configuration.  

These issues are well documented by both Oracle and Microsoft, and Quest Software can provide details upon request. Basic requirements are detailed below:
 

 To test Euro support in the SQL Editor (spool window and results grid), execute the following statement:

            select chr(128) from dual;


Back to Top

Support of Oracle Features


Oracle feature

Support

Tables

·         Standard relational tables

YES

·         Partitioned (range, hash and composite) Tables +

YES

·         Partitioned (list) Tables +++

YES

·         Object tables +

YES

·         Queue tables + (including schedules)

NO

·         Index-organized tables +

YES

·         Temporary tables +

YES

·         External tables +++

YES

Views

·         Standard views

YES

·         Inline views

YES

·         Object views +

YES

·         Join views (including updateable) +

YES

·         Check option on views +

YES

·         Read only option on views +

YES

·         Polymorphic Views +++

NO

·         Views Hierarchies +++

NO

·         Views with Constraints +++

NO

Constraints (definition, clauses and storage)

·         Primary keys

YES

·         Unique keys

YES

·         Foreign keys(including external FKs, views FKs+++)

YES

Procedures

YES

·      Java/C Methods Calls +

YES

·      Invokers Right +

YES

Functions

YES

·      Java/C Methods Calls +

YES

·      Invokers Right +

YES

Packages

YES

·         Header

YES

·         Body

YES

·      Invokers Right +

YES

Indexes

·         Standard

YES

·         Bitmap

YES

·         Bitmap Join Index +++

NO

·         Descending ++

YES

·         Reverse key +

YES

·         Partitioned +

YES

·         Global +

YES

·         Local +

YES

·         Non-prefixed +

YES

·         Pre-fixed +

YES

·         Function-based ++

YES

Materialized views ++

YES

·         Index-Organized Materialized Views +++

YES

·         Indexes on Materialized Views +++

YES

·         XML, LOB, nested table, varray type columns +++

YES

Materialized view Logs ++

NO

Snapshots (Oracle 7.3.4 up to Oracle 8.0.x Only)

NO

·         Simple and complex

NO

·         Registered

NO

·         Read-only and updateable

NO

·         Complete, ROWID and primary key fast refreshes

NO

Snapshot logs (Oracle 7.3.4 up to Oracle 8.0.x only)

NO

·         Record with Object ID or Sequence +++

NO

Refresh groups ++

NO

Datatypes

Built-in Datatypes

YES

Character

YES

CHAR

YES

NCHAR+

YES

VARCHAR2

YES

NVARCHAR2+

YES

LONG

YES

CLOB+

YES

NCLOB+

YES

Number

YES

Date types

DATE

YES

TIMESTAMP +++

YES

TIMESTAMP WITH TIME ZONE +++

YES

TIMESTAMP WITH LOCAL TIME ZONE+++

YES

INTERVAL YEAR TO MONTH +++

YES

INTERVAL DAY TO SECOND+++

YES

Binary data types

RAW

YES

LONG RAW

YES

BLOB

YES

BFILE +

YES

Binary_Float ++++

YES

Binary_Double ++++

YES

Ids

ROWID

YES

UROWID +

YES

 ANSI DB2, SQL/DS datatypes

YES

User defined data types+

Collection Types +

YES

Object Types +

YES

Oracle Supplied types+

"Any" Types +++

NO

XML Types +++

YES

Spatial Types +

NO

Media Types ++

NO

Context Text Types +

NO

Operators

NO

·         User defined ++

NO

·         Ancillary ++

NO

Triggers

·         Standard

YES

·         Instead-of +

YES

·         Database-event +

YES

·         Nested-table view triggers ++

YES

Clusters

YES

·         Non-hash

YES

·         Hash

YES

·      Row level dependency tracking +++

NO

Collections

YES

·         Nested tables +

YES

·         VARRAYs +

YES

Java support

·         JDBC code +

NO

·         SQLJ code +

NO

·         JAVA SOURCE +

YES

·         JAVA CLASS +

YES

·         JAVA RESOURCE +

YES

Database links

YES

PFILE, SPFILE +++

NO

Libraries +

YES

Synonym

YES

Sequence

YES

Dimensions ++

YES

Directories +

YES

Indextypes ++

YES

Jobs

YES

Outlines ++

NO

Policies ++

NO

Histograms

NO

Sum Deltas ++

NO

Object support +

·         Types

YES

·         Attributes

YES

·         Methods

YES

·         REF support(columns and attributes)

YES

·         Inheritance

NO

·        Substitutability

NO

·        Polymorphism

NO

User defined statistics ++

NO

Context Namespaces +

NO

Audit options +

NO

Profiles +

YES

Roles

YES

Privileges

YES

Resources +

·         Resource plans

NO

·         Consumer groups

NO

·         Plan Directives

NO

·         Allocation method

NO

·      Alter Resource Cost dynamically +++

NO

Rulesets ++

NO

External objects ++

NO

Tablespaces

·         Standard

YES

·         Temporary

YES

·         Read-only

YES

·         Locally managed ++

YES

·         Transportable +

YES

·         Undo Tablespace+++

NO

Partition manipulation +

YES

PL/SQL server pages ++

NO

Fine grained access control +

NO

Application contexts +

NO

Labels (Trusted Oracle)

NO

National Language Support

NO

Legend:

+          Available in Oracle 8.0.x onwards           

++        Available in Oracle 8.1.x onwards           

+++      Available in Oracle 9.0.1 onwards

++++    Available in Oracle 10g onwards 

YES     Supported fully or partially                                  

NO       Not Supported                          

-           Not relevant to this product 


Known Issues

The following is a list of issues known to exist at the time of SQL Navigator® for Oracle release.

Area

Known Issue

Change Request

 

Installation
When performing an upgrade v6.1 in the same folder as v6.0: the v6.0 icon still exists, there are 2 entries (v6.0 and v6.1) in the Add/Remove program. When uninstall v6.0 using Remove/Program, it also removes most of files of v6.1.

 

Work around: Uninstall v6.0 using Quest Installer before running v6.1 installation.

ST 4846
Code Editor
Dot look up does not work consistently on some environments. It takes a while to bring up the list, or the dot look up list is not shown at all. ST 4735
Migration for Side-By-Side Support User-setting files such as .cac (Code Assistant), .wsf (Workspace) in the application folder of SQL Navigator 5.0 and older will be not automatically migrated to the user profile folder created by SQL Navigator 5.1 and above (if the newer SQL Navigator is installed in a separate location from the older SQL Navigator).

Workaround: Copy these files manually into C:\Documents and Settings\'UserName'\Application Data\Quest Software\SQL Navigator 6.1.0.
64bit Support

 

Only support 32bit Oracle clients.


By default SQL Navigator is installed in ‘c:\Quest software/SQL Navigator 6.1.0’.  SQL Navigator cannot detect location of OCI.dll if there is ‘()’ in the installation path.
Hyper-Threading impacts on performance. The following link is from Intel and outlines the limitations of running Hyper-Threading processors on Windows operating systems: http://www.intel.com/support/processors/pentium4/sb/CS-017371.htm. If you experience performance issues, turn off the Hyper-Threading in the bios.

Citrix installation

Citrix client does not allow you terminate SQL Navigator: The Citrix client's program Neighbourhood Centre does not display applications that are run on the host, therefore you cannot terminate the application from the client.


Do not use SQL Navigator with multiple connections running with the same user name.
SQL Monitor is not picking up the SQL Navigator license key.

Workaround: copy QSAuthorize12.key file from a User profile location to the installation directory.

When publishing SQL Navigator, it is recommended that SQL Navigator be published with 16 bit color depth or higher and a Session Window Size of 1024x768.


LAN Server/Client Installation Help content body does not load in SQL Navigator, SQL Optimizer or Knowledge Xpert help files if the client has had Microsoft Security Update 896358 or Microsoft Windows Server 2003 Service Pack 1 (SP1) installed. Please refer to Microsoft KB Article ID892675 (http://support.microsoft.com/default.aspx?scid=kb;en-us;892675) for information and workarounds.
SQL Monitor is not picking up the SQL Navigator license key.

Workaround: copy QSAuthorize12.key file from the Shared directory on the server to the client installation directory.
SQL Optimizer cannot be launched from the client when the client/server installation is performed.

Workaround: Install SQL Optimizer on each client PC.
When installing Knowledge Xpert in a Server/Client configuration, the server install of Knowledge Xpert must be located in a shared directory or the client install cannot pickup the PL/SQL Development knowledge file (Plsql.rev.)  Quest recommends that the server installation of Knowledge Xpert be placed in a folder in the SQL Navigator shared server directory.
Taskbar More items button on the taskbar not available when using the Standard theme in the preferences. (Native theme will be Standard if OS theme is Windows Classic).

Workaround: Select a theme other than Standard (or Native).
Execution Console When using the Execution Console with REF CURSOR IN parameters, the user must modify the generated code in the SQL Editor before continuing. REF CURSOR OUT parameters are supported.
External Product Integration Formatting Options screen "erases" main application window while it is open (#47014). CR# 47014
Extract DDL The Extract DDL statement for an Object Type may require the object qualifier to be entered in manually into the statement before it will execute successfully.
National Language Support
There is a new preference “General->Session->National Language Support level”. These options require a restart of SQL Navigator.
SQL Navigator can ONLY support Unicode data in Data grids . SQL Navigator does not support object names and object attributes in Unicode char sets.  

Name field in both Find Objects and in Code Search does not accept NLS char sets.
It is not possible to execute package with Chinese names used within a code.
Oracle Client or Server Version Related  Data from NCHAR or NVARCHAR2 columns will not display from a 9i database with default character set when using an 8i client. This issue is covered by Oracle technical note 140014.1 "Oracle8/8i to Oracle9i using New "AL16UTF16" National Character Set". To display this type of data, update to the 9i Client, or change to a character set supported by your client.
Oracle Instant Client Light Some Instant Client Light client zip package distributions have been found contain the oraociei10.dll Data Shared Library instead oraociicus10.dll (specific for the light client). SQL Navigator requires oraociicus10.dlln if using the light client or it will fail to start; workaround: add the oraociicus10.dll to the light client directory.
Oracle Instant Client LDAP support Instant Client LDAP support is dependant on specific LDAP DLL which Oracle does not install by default. The ORALDAPCLNT10.DLL must be located in the same location as oci.dll file. 
TNSNAMES.ora, LDAP.ora, SQLNET.ora must exist in the same location specified by the TNS_ADMIN system variable.
The LDAP dropdown list in the Logon Dialog will not be populated, but connection can be carried out by manually enter the DB name into the ‘Database field’ on the logon screen.
Team Coding "Deny Drop for checked-out/frozen objects" pref not working for Team Coding objects: tables, index, java source, sequence, cluster and synonym.
Team Coding can't distinguish mixed-case object names in the case-sensitive manner. CR# 40712
Check In fails when object name is mixed case or contains spaces/special characters. CR# 41256
Changing Version Control providers is not supported well by Team Coding. If you need to change the Version Control product you are using, we recommend that you delete all your code control groups.
When adding scripts from a shared network resource to a Team Coding Code Control Group, a common mapped drive letter must be used. (UNC naming support may be automated in a future release)
Can edit a locked SQL script by switching sessions; in general, we don't recommend that users switch to another session when a script is checked out, because scripts, unlike database objects, do not have a known owner CR# 55979
Problem with Team Coding when migrate from 5.5 to 6.0 - Getting errors in Output window that the path of Team coding dlls not valid.

Work around: Make sure all paths specified in the following registry key HKEY_CURRENT_USER\Software\Quest Software\SQL Navigator 6.1.0\Plugin\VCS\ProviderPath points to the application installation folder.

 
Cloning may not transfer 'checked-out' status to the cloned package spec and body. A workaround is to enable the preference "Simultaneously Check in/Out spec and body" prior to the initial checking out of the package spec or body, or to close and reopen the Stored Program Editor if the status has only been transferred to one object.
Materialized View / Snapshot VOE Materialized views/Snapshots does not have UI for Prebuild table and Cluster option.
Refresh type script generates incorrectly when saving changes.
General/Other When launching SQL Navigator from the short cut created manually without the start path in the properties of the short cut, CodeXpert feature does not display graphical information. Work around: Make sure the start in path of the short cut should be the SQL Navigation installation directory.
When using an Oracle 10.2.0.2 client, NAV might freeze or an AV occurs with one of the oracle DLL. Basically, the problem only occurs when Spool Output in the SQL Editor is disabled while executing the command. Workaround: Turning Spool Output on resolves the issue.
SQL Navigator will have some performance issues when all of the following options are enabled: Enabling Trace option, DBMS Output and Debugger Session.
Loss of connection while debugging or while performing actions against multiple objects is not handled gracefully. CR# 50762, CR#50763
Clicking an MDI window title doesn't activate the associated actions on the main menu/toolbars if focus is inside a docked window.

Workaround: click inside the MDI window to make it active.
CR# 47273
Pressing F1 for help on the welcome screen does not launch online help and dropdown menu's do not operate; workaround: Close the welcome screen.
Full DBtree expand with trace on might cause SQL Nav to shut down.
SQL Monitor is not picking up the SQL Navigator license key.

Workaround: copy QSAuthorize12.key file from a User profile location to the installation directory.
"Save to File" is not supported by every Object Editor. Some editors (Java, Role, Profile) only permit save for new or modified objects.
Amendments to Index Storage for an Object Table is not supported via the Index Storage button.

Workaround: Alterations to Index Storage for Object Tables can be made via the Index tab located within the Table Editor as a workaround
When creating shared DB Links, "Public" must also be selected. CR# 48186
Session is disconnected when trying to connect across a database link using 9i client to connect to 8i databases. CR# 54327
PL/SQL Profiler groups created in v4.3 and later cannot be browsed in v4.2.

Workaround: all users should upgrade to v5.n at the same time if planning on using the Profiler
CR# 56106
The View Editor will not correctly display the new 10g datatypes binary_float and binary_double. CR# 89867
Some functions may fail to load and report an error mixed-case object names; workaround: rename the object with a unique name.
Session is disconnected when trying to add tables with the new 10g datatypes binary_float and binary_double in the SQL Modeler (#94314)
Formatter Plus Options modified within SQL Navigator will not be replicated in the options file when running Formatter Plus outside of SQL Navigator (#92784)
Launching SQL Navigator from SQL Monitor fails (#0126578); workaround: Launch SQL Nav separately.
Cannot close SQL Modeler after saving an invalid subquery (#0129352); workaround: Click the 'Cancel Sub query and return to Master query' button on the toolbar of SQL Modeler.
Floating dockable windows always stay on top (#0127520); workaround: Dock the window then set to Auto Hide.
Find/Replace confirmation dialog box may open behind the Find/Replace actions window causing SQL Nav to be appear not responding; (#124262); workaround: Hit Escape key to close the hidden confirmation dialog box.
The “More Buttons” & “Customize” toolbar dropdown list is not available when using basic UI styles (Flat, Standard and, in the case that the Windows OS is running a basic theme eg “Classic”, the Native UI style); workaround: Right-click the toolbar to access toolbar customization options.
When upgrading from SQL Navigator 4.x, existing dockable window layouts will have new defaults configured and applied to enable the upgraded windows docking functionality.
 Duplicate CodeXpert rulesets may sometimes appear in the ruleset list.
Dockable windows might not be visible.

Work around: Close SQL Navigator; Delete the registry key HKEY_CURRENT_USER\Software\Quest Software\SQL Navigator 6.1.0\Docking Windows then restart SQL Navigator.

 
Columns in table were created with double quotes, cannot insert/update on grid.

The following is a list of known problems in Oracle that may affect functionality of SQL Navigator®. They are reproduced here as an aid to problem identification. Additional information can be obtained from Oracle Metalink.

Debugger Like other third-party PL/SQL debugging tools, SQL Navigator's debugger employs Oracle's Probe API via the standard DBMS_DEBUG package, available since RDMBS v7.3.3. Users should be aware that this API is part of the Oracle Server kernel and that older versions of this API (prior to RDBMS v8.0.5) have certain limitations and are less stable. See the manual for details on the limitations of particular versions.
When the execution stack contains wrapped packages, particularly system packages, attempting to select an entry in the call stack may cause the debugger to hang
Aborting a debug session can destabilize the Oracle session
If a timeout occurs during debug session, there is no secure way to continue debugging

LOB Viewer
(May result in lost data)
Accessing 8.1.6 BFILEs using any client other than 8.1.6 can TRUNCATE the files to 0 bytes
Oracle Bug# 1240843
Dropping Java Resources When unloading a Java file (.class, .zip etc.) using Java Manager, the relevant Java objects will be dropped in SQL Navigator. However, it is an Oracle-client related problem when it comes to the automatic dropping of Java Resources. If you are using SQL Navigator from an 8i client, unloading Java files will not automatically drop the relevant resources if you are doing this to a schema other than the one that you are logged onto. This works only if you are using a 9i client (and connected to 8i or 9i) or if you are unloading from your own schema.


Third Party Provider Known Issues

The following is a list of third party issues known to exist at the time of SQL Navigator® for Oracle release. While every attempt has been made to provide seamless integration with supported third-party version control products, certain combinations of Windows client and vendor API have exhibited issues that cannot be resolved. In general, the SCC interface (no longer supported by Microsoft with the release of Visual SourceSafe 5.0) has proven to be problematic, and is not fully implemented by all products claiming support of the API. The development team has investigated integration with numerous other products - and may add support for additional providers in subsequent releases.

With respect to products that are currently supported, Quest Software recommends using the SCC interface only for Rational ClearCase and Borland StarTeam. Users of Serena PVCS 6.6 (or above) or Microsoft Visual SourceSafe should use the OLE (COM) interface provided as it is much more reliable. 

All known vendor-specific issues are listed below:

Vendor/Product   

Known Issue

Change Request

Serena PVCS Version Manager 6.6.x, 6.7.x 6.8.x, 7.5.x, 8.0.2 Integration via SCC is available, but not recommended by Quest.
PVCS Version Manager only supports "Tip Revisions" via the COM interface used by SQL Navigator. Attempting to retrieve a non-tip revision using the Version Control Browser will always return the latest revision. Serena Case ID# 1230782
Integration with PVCS Version Manager 6.8.00 (unpatched) causes SQL Navigator to abnormally terminate. This usually occurs 5 to 15 minutes after connecting to a database. This may cause loss of unsaved work. Quest therefore recommends against using PVCS Version Manager 6.8.00 (unpatched) with Team Coding. Serena has released patches that correct this problem. At the time of writing, the latest release is PVCS Version Manager 6.8.10. For current users of PVCS Version Manager 6.8.00, Quest recommends updating to PVCS Version Manager 6.8.10
After connecting to a PVCS database, successive connections made during the same SQL Navigator 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 SQL Navigator 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 SQL Navigator.
PVCS Version Manager 6.6.0 will always create a new revision on check-in even if the file is unchanged.
Microsoft Visual SourceSafe 6.0 Number of consecutive operations via SCC is limited. Use of SCC interface is not recommended by Quest for this product.

IBM Rational ClearCase 4.1 and 2002
Using Dynamic Views via SCC interface may cause intermittent problems. Using Snapshot Views is recommended.
Rational Case ID# v0830629, Rational Defect # CMBU00053934)
UCM configuration is not supported. Base ClearCase configuration must be used instead.
When working with UCM projects, a ClearCase activity selection prompt will appear for each new object during exporting.
Browsing to "My Computer" when choosing a project for your CCG may "freeze" under some circumstances.
Ignores 'Create a new revision for existing objects' option when exporting.
For script support to function correctly when using ClearCase, the scripts that are intended to be placed under Team Coding control need to be placed in the working folder of the view as specified in the Code Control Group.
Difference detection will not work for hijacked script files (please refer to your ClearCase documentation for an explanation of hijacked files).
Microsoft Team Foundation Server A Team Foundation Server check-in dialog will appear for each new object during exporting (see http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=738761&SiteID=1)
Borland StarTeam 4.2, 5.1, 5.4, 6.0 and 2005 Performing operations within StarTeam client while connected via SCC renders SCC interface unstable (close all connections within SQL Navigator before making changes).
Ignores 'Create a new revision for existing objects' option when exporting.

 


System Requirements

Before installing SQL Navigator®, ensure your system meets the following minimum hardware and software requirements:

Platform Intel Pentium 3 (600MHz or higher)
Memory Minimum 512MB RAM/1GB*
Hard Disk Space 100MB**
Display XGA (1024x768) or better monitor
DirectDraw 7 capable graphics adapter
Operating System
  • Windows 2000/SP4 Workstation and Server versions

- or -

- or -
  • Microsoft Windows Server 2003 with the latest Service Pack.
Oracle Client SQL Navigator 6.1.0 supports Oracle clients 8i through 11g.
Oracle Server SQL Navigator 6.1.0 supports Oracle versions 8.1.7 through 11g. However it is recommended that you connect to Oracle 9i or above databases via Oracle client versions 9i or above. 

Please refer to the Oracle documentation for 10g or above instant client server compatibility.
Citrix/Terminal Server Support

Citrix products supported include:

  • Platform Level - MetaFrame XPa 1.0 Server for Windows
  • Feature Release - MetaFrame XP 1.0, Feature Release 1,2 and 3.


For installation notes on installing SQL Navigator 6.1.0 in a Citrix environment, refer to the Installation section in "Getting Started" below.

* 1GB RAM recommended for running SQL Optimizer in Xpert Edition

** More disk space required for Xpert installation, less for Standard & Professional Editions.



Global Operations


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 or multi-byte character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same 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.

This release has the following known capabilities or limitations: There are 3 levels of SLAAT (Supports a single Language At A Time) support. See the release notes for detailed information.

 


For More Information

 

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our Web site for regional and international office information.


Contacting Quest Support:

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%20Support%20Guide.pdf.

 


This document contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 

© 2008 Quest Software, Inc. ALL RIGHTS RESERVED.

 

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Fastlane, Final, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, Knowledge Xpert, LeccoTech, LiteSpeed, LiveReorg, Matrix Insight, Matrix.Net, MIQ, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Speed Change Manager, Speed Coefficient, Spotlight, SQL Firewall, SQL Impact, SQL LiteSpeed, SQL Navigator, SQLab, SQLGuardian, SQLProtector, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., 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 following third party libraries, re-distributables, and files were used in the creation of SQL Navigator®:

    * BeyondCompare
    * CueSoft XML
    * DatasetPrinter
    * Dev Express Component Suite (including DevExpress Bars,  Dev Express Grids)
    * DOA
    * DreamTree
    * Expression Evaluator
    * Hash
    * HTMLHelpAPI.pas
    * HTMLViewer
    * ODAC
    * Rapware - MAPI
    * Report Builder
    * rmcontrols
    * SynEdit

    * TBX 1.0
    * TdfsBrowseDirectoryDlg
    * TeeChart
    * Turbo Power String Resource Manager
    * Turbo Power Systools
    * Toolbar97

    * Toolbar2000 2.1
    * ThemeManager

    * VirtualTreeview 4.42

    * TntWare Delphi Unicode 2005
    * ZLib 

 

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

Disclaimer

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.