SQL Navigator® for Oracle

Version 5.5.4 - Release Notes

Release Notes

November 2007

Contents

Welcome to SQL Navigator for Oracle 5.5.4

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 5.5.4

Thank you for installing SQL Navigator® 5.5.4, 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 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.

 

Back to Top

Getting Started

Contents of the Release Package

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

  1. SQL Navigator® for Oracle 5.5.4
  2. Knowledge Xpert for PL/SQL 9.1.1
  3. Quest SQL Optimizer for Oracle 7.2
  4. Quest Toad Data Modeler 3.0
  5. SQL Monitor 2.4.3
  6. Adobe® Acrobat Reader 7.0
  7. 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. 

 

Back to Top

New in This Release

 

Updates to SQL Navigator® 5.5.4

 

Updates to SQL Navigator® 5.5 

 

New Features in SQL Navigator® 5.5 

 

Back to Top

Resolved Issues and Enhancements

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

Area

Resolved Issue

Change Request

General Migration problems from 5.5 to 5.5.4CR# 207235
PLSQL Debugger is now part of the Standard Edition   CR# 197901 
The Output window does not have horizontal scroll bar, as it used to have in 5.0CR# 174464
Add SQL Navigator edition information in support bundle    CR# 195712
Implement the ability to use all windows in the current session when having multiple projectsCR# 194450
Error when naming a user defined template with more than 15 charactersCR# 192900
Access Violation when using 'Reflection' software with SQL Navigator.    CR# 192039
Operation Description' dialog in Explain Plan is modal over everything  CR# 185649
Include Code Assistant Case statement snippetCR# 185070
Replace current dbms_output.put_line with latest 10g utility dbms_utility  CR# 181765
Allow a visual differentiation of sqlnav5 on startup to be able to see whether sqlnav5 is standard, professional, or xpertCR# 180982 
ConnectivityAdd LDAP support for Active DirectoryCR# 190990
Sqlnav loses connection while selecting unusable dblinksCR# 192580

Extract DDL 

Add 'FORCE' option, while extracting DDL for VIEWS.

CR# 180565

In the DDL for tables, the character setting should be included.
CR# 182554 
Extract DDL does not extract full DDL statement for partitioned tables
CR# 196224
Extract ddl of roles   
CR# 199385
Program become unstable after multi extract DDL to seperate editors    CR# 200117 
Include ACCOUNT LOCK clause in Extract ddl from locked userCR# 199387
SQL EditorResults Pane (Grid) Copy+Paste adds blank spaces when exporting to Excel
CR# 62928
Allow to remember Format file set as default by user in Export Data, after closing application
CR# 165089
When multiple editors are open (with data displayed): switching Editors is causing active window reverse to SQL tab
CR# 173987
SQL Editor Open inconsistency   
CR# 184444 
Could not able to run the Code Xpert on stored objects or on any SQL script in sql editorCR# 204992
Allow to remove extra carriage return when updating through Editing Box in SQL NavigatorCR# 191702
Copying to clipboard: Values from grids: Not working as expectedCR# 184476
Add syntax highlighting for SQL/X functions    CR# 60346
Reserved words list to be updatedCR# 184116
Export Data dialog usability enhancementsCR# 183685
Visual Object Editors"SQL" button in User Editor becomes active, when focus moves to another radio-buttonCR# 182553
Restrictive character length for data entry in View Editor text tab CR# 185067
Rename table column enhancement for Table Editor    CR# 185069
Constraint Editor: AV on opening constraints that does not have any parent TableCR# 198252
User Edition: Cannot add new quotaCR# 186076
Difference ViewerDifference View should remember the last paths used when selecting scriptsCR# 172403
Allow direct entry for object namesCR# 183689
Implement ability to send SQL from Diff Viewer to SQL Editor    CR# 196680
Difference Viewer should have copy/edit abilityCR# 184805
Find ObjectsCannot find objects with lowercase in Find Objects    CR# 193073
Implement case sensitive checbox in the 'Find Objects' dialog    CR# 185650
DB Navigator TreeTable high/low values not displayed correctlyCR# 185436
Marking locked_users in users list in db_nav tree    CR# 186808 
If trigger is alter session to set to current_schema: DB Nav tree displays errorCR# 190523
Connection to database lost during disabling triggers by right click action  CR# 205146
Add "Revoke" command to RH menu on "Granted Roles" sub-node under "Users" node on DB Nav tree CR# 157421
When the user opens the Databse Browser, the (+) and (-) signs are missing for the 'Views', 'Indexes' and 'triggers'CR# 193968
Third Party IntegrationUpdate TDM to v2.25    CR# 203208
Wrapper Utility: Change to open dialogue workflowCR# 184475
Activation of the SQL Optimizer option is not intuitive    CR# 187546
After installing standard edition of sqlnav 5 in LAN client/workspace installation type: SQL Optimizer doesn't runCR# 195737 
Team CodingExpand object support for Team Coding import script generationCR# 196523
Exporting Grants on objectsCR# 90109
Formatter options cannot be saved or imported CR# 199959  
Online HelpRemove references to Data Factory CR# 203210, CR# 203213
Team coding actions should not be enabled for Store TablesCR# 173973
InstallationSilent Install does not work for a particular combinationCR# 194649

Back to Top

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. 


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® 5.5.4 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 +