Download Support of Oracle features in SQL Navigator 5.1

Release Notes
February 2006 (Version 5.1)
Contents
Choose EditFind to locate a specific topic.










Welcome to SQL Navigator for Oracle 5.1
System Requirements
Installation and Configuration
What's New in version 5.1
What's New in version 5.0
Team Coding Third Party Support
Support of the Euro Character
Known Issues with this release
Appendix: Support of Oracle features in SQL Navigator 5.1
Further information...
Welcome to SQL Navigator for Oracle 5.1
Thank you for installing SQL Navigator® 5.1, 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.
This release includes the following:
 Support for Oracle 10g (Release1 and Release2).
 Citrix/Terminal Server support.
 Improved support for XML data types.
 In-process SQL Tuning component included with Xpert edition.
 New functionalities.
 Miscellaneous enhancements and bug fixes.
Refer to the section "What's New in version 5.1" for full details.
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
Please refer to the Online Help (available from Help menu in SQL Navigator, or from the Start Menu under
Programs/Quest Software/SQL Navigator 5/On-Line Documentation) for details about the changes and
enhancements in this release. In particular, please view the "Quick Tour" and "Features" sections of the help
system.
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
http://www.quest.com/sql_navigator/nav_tips.
System Requirements
Minimum Hardware Requirements





Pentium 3 600MHz
256MB RAM/1GB*
CD-ROM Drive (for CD based installs)
XGA (1024x768) or better monitor
DirectDraw 7 capable graphics adapter
NB: 110MB disk space required for Xpert installation, less for Standard & Professional Editions.
* 1GB RAM recommended for running SQL Tuning in Xpert Edition
Software Requirements
Client configuration
 Microsoft Windows NT4/SP6a, Windows 2000/SP4 Workstation and Server versions
- or -
 Microsoft Windows XP Pro SP1 and SP2
- or -
 Microsoft Windows Server 2003 SP1
NB: Windows 95, 98 & ME are not supported









Oracle client 8i, 9i and 10g (Release1, Release2) Thick client, 10g (Release1, Release2) Instant
Client.
DataFactory 5.0 or greater (optional)
DataFactory 5.0 or greater (optional)
Benchmark Factory 3.1 or greater (optional)
Formatter Plus DLL 4.8.5 or greater (v4.8.5.5 included)
Knowledge XPert for PL/SQL 6.0 or greater (optional)
Knowledge XPert for Oracle Administration 6.0 or greater (optional)
SQL Monitor 2.4.x
SQL Lab Tuning 5.0 or greater (optional)
Server configuration
SQL Navigator 5.1 supports Oracle versions 7.3.4 through 10g (Release1, Release2). However it is
recommended that you connect to Oracle 8.0.6 databases via Oracle client versions 8.1.7 through to 9 i.
Please refer to the Oracle documentation for 10g 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 5.1 in a Citrix environment, refer to Installation and
Configuration section below.
Installation and Configuration
Software Installation
The Windows user that installs and licenses SQL Navigator requires certain write-access privileges and
therefore must be a member of either the Administrators group within Windows, or have equivalent
privileges.
SQL Navigator 5.1 is provided in three editions - Standard, Professional and XPert. All editions install in the
same manner. The Installation wizard offers the following options:
Installation Type
 PC install - all files are installed on to the client workstation
 LAN Server install - creates master installation of all files on a common file server; SQL Navigator is
not configured for use on the workstation performing the installation
 LAN Client install - creates program shortcuts and registry entries referring to the LAN Server
installation. Executable files are not installed locally
 Citrix install - all files are installed on the Citrix server(s). It gives you the ability to run SQL
Navigator from a remote location without having to install the entire system on your own machine.
Destination Directory
 The physical location to install the SQL Navigator files. If a previous installation of SQL Navigator
4.x or above is detected, its location will be pre-selected by default
 For LAN Client installations, browse to the network resource containing the LAN Server installation
Backup
 You may choose to backup your existing installation. This backup will be restored upon subsequent
un-installation
Installation Options
 Create a shortcut for SQL Navigator on the desktop (shortcut is always created in Start menu
regardless of this setting)
 Associate file extension .sql with SQL Navigator - Allows SQL Navigator to be launched directly from
a SQL Script
 Install Server-Side Objects - Required only for the specific functionality detailed below
As well as installing all required SQL Navigator files, the installation wizard also automatically installs SQL
Monitor, Knowledge Xpert for PL/SQL (Professional and Xpert editions), and in the case of the XPert Edition,
the SQL Tuning module is also installed. These products are installed in folders below your chosen
installation directory.
This release may require a new Authorization key. If an obsolete version of SQL Navigator (3.x or 4.0)
is detected during installation, a 30-day trial will be installed automatically, enabling all SQL Navigator
options. To obtain an updated Authorization key, please send an email to [email protected].
Please state "SQL Navigator Maintenance Request" as the Subject of the email. To speed responses, please
also include the following information in your email:







Name
Company Name
Site Location
Phone Number
Fax Number
Current License Key
Current Site Message
Trial-only Version
The trial-only version that can be downloaded from quest.com requires a license key to function. This trial
key is a single use key. If you have problems with your key, or would like to extend your trial, contact
Quest Software Sales.
If you wish to speak with a sales representative concerning placing an order or any other questions, please
call +1 949 754 8000.
If you decide to purchase a commercial license for SQL Navigator, you will be directed towards the
Commercial SQL Navigator download page at Quest.com. You will also be given a commercial key. You
cannot activate your trial copy with a commercial key.
The SQL Monitor tool bundled in the trial-only version has limited functionality.
Server-Side Installation
No server-side configuration is required for general operation of SQL Navigator, however it is required for
operation of the Explain Plan Tool, Team Coding, or if connecting to Oracle v7.3.0 or earlier. The PL/SQL
Profiler and Java->PL/SQL Publisher requires server-side support, which is installed on demand.
You can invoke the Server-Side Installation Wizard from the Tools menu. The wizard requires connection as a
DBA user so that the SQLNAV user can be created, as well as a number of roles. The wizard permits you to
specify a password of your choice for this user. Note that the option "Base SQLNAV Repository" must be
selected on at least one occasion to allow the other support features to be installed. All objects installed by
the wizard are installed into the SQLNAV schema.
To install support for Explain Plan
In order to save SQL statements in the Explain Plan tool, a special table is required in the SQLNAV
schema. Follow these steps:
1
2
3
4
5
6
7
Start the Server-Side Installation Wizard from the Tools Menu.
Choose Install Server-Side Objects and click Next.
Ensure that "Base SQLNAV Repository" and "Explain Plan Support" are selected, and click Next.
Enter a username (DBA user, such as SYS), password and connection, and click Connect.
Choose a tablespace for the objects to be created in the SQLNAV schema, then click Next.
Enter a password for the SQLNAV user, enter it again in the confirmation box, and then click Next.
Perform one of the following:
 Click Install, then Next
- or -

8
As a DBA user, run the script CRTUSER.SQL located in the install folder under the SQL Navigator
installation (C:\Program Files\Quest Software\SQL Navigator 5 by default) to create the SQLNAV
schema
As user SQLNAV, run the script CRTSQLTB.SQL to create the Saved SQL's table.
To install support for Arguments View
SQL Navigator requires the arguments view provided by Oracle in release 7.3.1. If you are using a version
of Oracle prior to 7.3.1, this view must be created in the SYS schema. Follow these steps:
1
2
Run the Server-side installation wizard following the steps above.
Note: You must connect as user SYS
Perform one of the following:
 On the script selection page, choose "Arguments View"

- or -
As user SYS, run the script CRTVIEW.SQL
To install support for Team Coding
The Team Coding module (version control) requires a number of server-side tables, all of which exist in
the SQLNAV schema.
Note:
1
2
3
4
5
6
It is highly recommended that you close all SQL Navigator sessions before performing
server-side installation for Team Coding
Run the Server-side installation wizard following the steps detailed for Explain Plan.
Choose "Base SQLNAV Repository" and "Team Coding" on the script selection page.
If you previously were using Version Control with SQL Navigator 3.2 or 4.x, choose a migration
option after checking the "Migrate" option. Please read carefully the documents linked by the "More
Info" buttons before proceeding. (These documents, VCSMigrate01.wri, VCSMigrate02.wri and
VCSMigrate03.wri are all available in the \Doc subdirectory after installation.)
Choose an existing role, or create a new role (you may choose any role name or take the default) for
the "Administrator" of Team Coding. Users assigned this role may perform such actions as enabling
or disabling the Team Coding module for this Oracle instance.
Choose an existing role, or create a new role for your "Project Managers". Users assigned this role
may fully configure Team Coding, but may not administer it.
Choose an existing role, or create a new role for your "Team Leaders". Users assigned this role may
modify existing Team Coding configurations, but may not administer it or delete "groups".
Once Team Coding is installed, users granted the "Administrator" role could configure Team Coding. The
roles created during installation are not granted to any users by default - you must make these grants
yourself. Please refer to online help for details of Team Coding configuration.
To install support for PL/SQL Profiler
The PL/SQL Profiler (Oracle 8.1.6 or higher) requires server-side support provided by Oracle. Follow these
steps:
1
2
Install Oracle's DBMS_PROFILER package as the SYS user.
In order to collect statistics, grant users SELECT privilege on the following system views:
V$SESSION
V$SESSTAT
V$STATNAME
To install SQL Navigator-specific support for a single schema
1
2
3
4
5
6
Start SQL Navigator.
Connect to the instance containing objects you wish to profile.
Select a stored program to profile in the DB Navigator.
Press F9 or click the Execute button on the session toolbar to invoke the Execution Wizard.
Progress through execution wizard, selecting "Enable Profiling" on the profiling tab.
Perform one of the following:
 When prompted to install Profiler support, click Yes
- or -
 Connected as user for schema containing objects you wish to profile, run the script
PROF_INSTALL.SQL
You can also install a central set of tables for storage of Profiler data, however this is not recommended,
as these tables may grow quite large. To install, follow the steps above to install into any schema, then
(connected as that user) run the script PROF_GLOBAL_INSTALL.SQL.
To install support for Java Publisher
In order to publish a Java class to PL/SQL, a Java class (com/quest/sqlnav/reflector) and an Oracle
package (SQLN_JAVA) is required in the user's schema. These objects are installed on demand in a similar
manner to the Profiler objects.
Note: If you attempt to publish a Java class which is located in a different schema the 'publisher' user
requires execute privilege on the class and the public synonym must be created for that class.
Recommended configuration for PL/SQL Debugger
(See the online help for details about Oracle support for the SQL Navigator Debugger.)
 Oracle for Windows version 7.3.4 or higher
 SQL*Net 32-bit to connect to the database
Recommended configuration for Oracle Web Development support
Oracle Web Toolkit version 2 or higher installed on database
Recommended configuration for Job Manager
In order to successfully use the Job Manager feature, a number of settings may need to be adjusted on your
server in the INIT.ORA configuration file so that the DBMS_JOBS package may be utilized. It is
recommended that you set the following values:
 job_queue_processes = 2
 job_queue_interval = 10
 job_queue_keep_connections = false
(You will need to restart your server before these settings take effect)
The purposes of the above settings are as follows:
 job_queue_processes specifies the number of concurrent processes to use in order to process
DBMS_JOBS. A minimum of two processes is required to ensure that a resubmission of a failed job
does not block all other jobs
 job_queue_interval is the time in seconds that controls how often the job processes "wake up" to
process pending jobs
Citrix Presentation Server Installation Notes
To install SQL Navigator on Citrix machine
1
2
3
4
5
Connect to the Citrix environment as an administrator.
If required, copy the applications to be installed to the Citrix machine.
Before installation, open a command line and execute: change user /install
Using the Windows Add/Remove program, install SQL Navigator.
NOTE: The Citrix Administrator will have to install the application on every machine in the Citrix farm.
However, the application only needs to be published once.
When setup is complete, verify the installation by launching SQL Navigator and Knowledge
XPert*/SQL Tuning*
*If installed.
Working with TNS Names
To enable all of the databases defined in the tnsnames.ora to be available to all the users in a Citrix
environment, use the TNS_ADMIN environment variable on each machine where SQL Navigator is published
to point to the location of the TNSNames.ora file.
What's New in Version 5.1
New Functionality in 5.1
 Full Support for Citrix Technology (including Citrix farms): SQL Navigator can be run in conjunction
with Citrix Presentation Server for Windows.
 Visual Object Editor for Materialized View (Snapshot).
 Wrap Code editor - The Wrap Code utility provides an easy way to access Oracle’s Wrap Code utility.
 New TNSNames Editor is available from the Oracle Logon dialog.
 Oracle Home selection for connection is available from the Oracle Logon dialog.
 Oracle error information integration with KnowledgeXpert product(s).
Enhancements & bug fixes in 5.1
 Windows is closing when click on the taskbar.
 Unable to fully expand the sql query and data result panel in the SQL Editor.
 Lose focus on editor when using Dot Lookup and code complete.
 New Team Coding support for the following object types: Tables, Index, Java Source, Sequence,
Cluster and Synonym.
 CodeXpert window displays as tab/embedded style in code editors based on preferences.
 Enhancements to taskbar - preferences added to give users full control on the behaviour of the
taskbar.

Windows Itanium server support.
 Full support to run SQL Navigator as non-admin/normal user.
 Support for StarTeam2005.
 SQL Navigator now handles Tab character correctly when specified in the preferences.
 Path and File name is printed when printing from the data grid.
 Printing of selected rows and column in the data grid is now available from the SQL Editor
File->Print...menu item.
 Foreign key constraint VOE does not show any information about the "on delete” clause [ cascade | set
null ].
 ORA-06550 after compiling some packages in SQL Navigator
 Appended ctrl-M to the lines corrupting PL/SQL source code in UNIX environment.
 Getting error PLS-00103 when compiling code which contains ampersand values.
 Constraint not refreshed after update.
 DESC for table linked to other database doesn't work.
 Running Delete in SQL Editor gives inconsistent results in errors panel.
 Extract DDL to the same editor not working as expected.
 In PL/SQL code -strings containing (&) are wiped out, if first quote is missing.
 Getting error ORA-1036 when trying to create an external table.
 Cannot compile dynamic SQL call packages.
 Execution of large code stopped before it completed (>=3 MB).
 New option in the preference for selecting main window background color as in SQLNavigator3.
 New preference added to setup sql editor so it always comes up upon opening SQL Navigator.
 10g R.2 datafiles are not displayed under tablespaces.
 Trigger VOE cannot be opened from the Code search screen.
 Run the block in the PL/SQL Profiler" button missing.
 In Table Editor LENGTH columns for date data type not displayed correctly.
 Add option to close window editor after "Auto run script at connect" pref is run.
 Upper case for reserved words is not consistently working.
 Refresh issue of (+) & (-) on DB Nav Tree disappearing.
 When adding a new column, a default value for VARCHAR2 datatype in Table Editor causes
ORA-02263.
 Recall Properties" feature to export the queries data does not always work if you choose "Delimited
Files.
 Packages/Package Bodies In "Export to VCS" Screen sorted not in any particular order.
 Access violation when trying to browse for HTML file from HTML editor while the focus is on output
window.
What's New in Version 5.0
New Functionality in 5.0
 The ER Diagrammer (Entity Relationship Diagrammer) lets you quickly model a table and graphically
see the dependencies and joins to other tables.
 The CodeXpert is a utility accessible via Editors in SQL Navigator that analyzes the code against a set
of rules for best practices. These rules are stored in a ruleset and can be either user-defined or
pre-defined.
 The Code Road Map graphically displays the complex PL/SQL interdependencies within a database.
 Team Coding for CVS is now included in SQL Navigator.
 A SQL Monitor tool is now bundled and installed automatically with SQL Navigator. This tool enables
the monitoring of connections to databases and SQL-queries.
 The look and feel of the SQL Navigator windows can now be changed as required by selecting from
the styles available in the User Interface preferences.
 New docking windows look and feel. Dockable windows, as well the Code Assistant can now be moved
outside of the SQL Navigator main window enabling you to have a more effective SQL Navigator
desktop. This feature can be extremely useful for multi-monitor desktops.
Enhancements & bug fixes in 5.0
 No undo after saving/compiling code in the Stored Program Editor (ID356149, 300021, 332670)
 Update bundled SQL Tuning to version 6.1.1.166 (CR0131445)
 Multi File formatting (CR0128316)
 Resolved issues with deleting multiple folders in Workspace (CR0130486)
 SQL Tuning cannot be found due to collision with some Quest DLL files (ID290786, 298774, 302429,
303935)
 Incorrect Information on Describing Remote Tables via DB Link (ID139147, 243929)
 Unable to Use CTRL+ALT+L Hotkey to Lowercase (ID272538, 239493, 312764, 271092)
 Pasting column into excel creates trailing spaces (ID227215, 209018)
 Large font supported (ID130644, 56629, 138237, 196150)
 A small edit window on LONG column field pops up incorrectly (ID185828)
 Ability to copy an existing row in a grid and paste it as a new row like EXCEL (ID8109291)
 Find/Replace Inserts Instead Of Replaces (ID238290, 240202)
 Receiving Access Violations Randomly when editing data (ID169896)
 Allow to save a set of "Export Properties" and invoke them to use, when required (ID208915)
 Add support for version control product CVS (ID240587, 316231, 230107, 246764)
 Unpredictable Varchar(2) datatypes size, when DESC synonym for DB-linked table (ID243749)
 SQL Editor results tabs from multiple queries appears null (ID299499, 316621)
 Allow duplicating rows from grid in Data tab in Table Editor (ID289640)
 Unable to resize split SQL Editor window (ID289235)
 Failure to execute a view with object types in oracle 10G database (ID275944)
 Windows cursor focus is getting back to SE in Win XP SP2 (ID272948)
 Cannot see selected column name in Table & View Editors (ID267296)
 Wildcard (%) in Code Search from triggers do not work (ID290477)
 Unable to View Roles Granted to Roles (ID284743)
 LOB Viewer positioned wrongly on screen in 800x600 resolution (ID286276)
 SQL Modeler - is not a valid floating point value (ID269672, 282297, 288529)
 Cannot Edit Saved SQL (Team Coding) (ID266221)
 Wrong schema prefix during Extract DDL for multiple objects (ID263833, 342879)
 Dot lookup sometimes still works when turned off from preferences (ID263373)
 Insert data in new record on grid & switch Tabs - input is replaced by existing record (ID321158)
 Column comments lost when using slider bar (ID174192)
 SQL Nav shuts down while navigating Enabled Roles and using keyboard (ID224302, 243048, 305574)
 Allow to set a selected Export Data Format as Default (ID194795, 221206, 327039)
 If TNS_ADMIN is in OraHome & TNS is on network drive, Logon doesn't show entries (ID308402)
 SQL editor and parenthesis (ID322587)
 Access violation in Results tab of Execution Console with output of collection (ID341894)
 TC's Difference Viewer displays code on single line, if comparing external object (ID328409)
 Auto Commit on Logoff (ID314169)
 Oracle server logon DB drop down is blank (TNS) (ID214446)
 Launching SQL Tunning is causing AV, when Task Bar is docked at top, of window (ID307373)
 Incorrect display of data for MDSYS SDO_Geometry format (ID303268)
 Invalid variant type conversion when running query with bind variables (ID305043)
 Down arrow does not scroll to next database at login (ID168117)
 SQL Impact Where Used Option Greyed Out on Menu (ID163191)
 Allow for default filename in Export Data, derived from table_name used in query (ID221304)
 Allow to print a record from single record view (ID206792)
 When a full record from grid is copied & pasted a width of fields is not trimmed (ID218776)
Team Coding Third Party Support
SQL Navigator's Team Coding module directly supports the following products:
 Microsoft Visual SourceSafe 5.0/6.0 SP6d (Windows NT 4, 2000, XP)
 Merant PVCS VM 6.6/6.7/6.8/7.5/8.0.2 (Windows NT 4, 2000, XP)
 Merant PVCS VM 5.2/5.3/6.0 (Windows NT 4, 2000, XP)
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:
 Rational ClearCase 4.1/2002 (Windows NT 4, 2000, XP)
 Borland StarTeam 4.2/5.1/5.4/6.0/2005 (Windows NT 4, 2000, XP)
 CVS Server 1.x/2.x* (Up to 2.5x for CVSNT)
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.
Known Issues with Third Party Providers
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 Merant 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:
Merant 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.

The following issues apply to integration using the COM interface.

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. (Merant 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. Merant 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.
Rational ClearCase 4.1 and 2002
 Dynamic Views are not supported via SCC interface. Snapshot Views must be used instead. (Rational
case id v0830629, Rational Defect # CMBU00053934)
 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)
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
Working with Triggers and Views
There are a number of important pre-requisites when using Team Coding with Triggers and Views which
relate to creation of the objects in different schemas.
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"
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:
1
2
3
4
5
6
When connected as a user with Team Coding Administration privileges, ensure that the Team Coding
connection setting "Use Trigger Description for DDL" is enabled.
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
From the Object menu/toolbar or pop-up menu, choose Extract DDL.
In Extract DDL Preferences, ensure that "Prefix with Schema Name" is enabled, and that "Show
Trigger Snapshot" is not enabled, then click OK
Execute the generated script.
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.
Support of the Euro Character
SQL Navigator 5.1 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:
 The original release of Microsoft Windows NT 4 did not include Euro support. Patches are available
from Microsoft to provide this support (NT SP4 or greater).
 The following fonts supplied with all versions of Microsoft Windows do not include the Euro symbol:
 Courier
 Fixedsys
 MS Sans Serif
 MS Serif
 Small Fonts
 System
 Terminal
 If your keyboard does not provide the Euro symbol, it may be entered by using the numeric keypad
and the ALT+0128 key combination
 Both Oracle Server and Client must be configured to NLS_LANG character sets which include the
Euro symbol. Refer to Oracle Metalink, document ID 68790.1
To test Euro support in the SQL Editor (spool window and results grid), execute the following statement:
select chr(128) from dual;
Known Issues with 5.1 release
The information below has been extracted from Quest's internal bug-tracking database; a workaround is
given where appropriate:
Citrix installation:

Citrix client does not allow you terminate SQL Navigator: The Citrix client's program Neighborhood
Centre does not display application that are run on the host, therefore you cannot terminate the
application from the client.

Publishing SQL Navigator: 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.

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.
LAN Server/Client Installation:

Help content body does not load in SQL Navigator, SQL Tuning 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.

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).
SQL Tuning

Please refer to the file named 'README-SQLTuning.WRI' which is located in 'Doc' folder, under the
main SQL Navigator installation directory for more information.
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).

SQL Navigator does not launch older version of Data Factory when running on a Windows 2003
client.
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

SQL Navigator does not fully support the use of Mixed Case metadata in all Visual Object Editors. In
particular, errors may be encountered where two objects have clashing names (e.g.: "MyProc" vs.
MYPROC).

SQL Navigator does not fully support multi-byte character sets.
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.
SQL Editor

Terminating semi-colon required for SQL*Plus EXECUTE command (#52639)

The DESC command in the SQL Editor requires that the spool is enabled

The SQL Editor does not always handle disconnection gracefully. It is recommended that you close
the SQL Editor before reconnecting to a lost session.

The default size of the SQL Editor window may obscure grid results; workaround: expand or
maximise the SQL Editor window
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 (#40712)

Check In fails when object name is mixed case or contains spaces/special characters (#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 (#55979); 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

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

No filter of snapshot in the Code search window.

Materialized views/Snapshots does not have UI for Prebuild table and Cluster option.
Refresh type script generates incorrectly when saving changes.
General/Other

SQL Navigator fails to load without a root ORACLE key in HKEY_LOCAL_MACHINE (Applies to Instant
client machines only); workaround: Add the key “ORACLE” to the
HKEY_LOCAL_MACHINE/SOFTWARE registry. The ORACLE key can be empty but must be present.
(#154470).

Loss of connection while debugging or while performing actions against multiple objects is not
handled gracefully (#50762, 50763)

Clicking an MDI window title doesn't activate the associated actions on the main menu/toolbars if
focus is inside a docked window (#47273); workaround: click inside the MDI window to make it
active.

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 (#48186)

Session is disconnected when trying to connect across a database link using 9i client to connect to 8i
databases (#54327)

PL/SQL Profiler groups created in v4.3 and later cannot be browsed in v4.2 (#56106); all users
should upgrade to v5.0 at the same time if planning on using the Profiler

The View Editor will not correctly display the new 10g datatypes binary_float and binary_double
(#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)

Execution console outputs a blank field instead of "(empty)" (#93448)

Launching SQL Navigator from SQL Monitor fails (#0126578); workaround: Launch SQL Nav
separately.

Initiating a SQL Navigator shutdown and choosing 'Cancel' at the "Do you want to save changes?"
conformation dialog, whilst a modified query exists in SQL Tuning (SQL Tuning prompt) will generate
and AV upon close.; workaround: Choose Yes or No at the confirmation dialog.

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.

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
 An attempt to view the value of an uninitialized NUMBER variable causes session to crash (Oracle
versions below 7.3.4.1)
 Aborting a debug session can destabilize the Oracle session
 Viewing values of package global variables is not supported on Oracle versions below 8.0.5
 If a timeout occurs during debug session, there is no secure way to continue debugging
 SQL Navigator hangs after terminating a debug session on Oracle 8.0.4
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)
Editing Data under Oracle 7.3.4
Oracle 7 does not support the returning ROWID when selecting rows. Subsequently, updates to table data
from the SQL Editor require that the row is re-selected for update, using unmodified columns to fetch the
correct row. In some circumstances, this may result in multiple rows matching the where clause, resulting in
inability to update the table (an appropriate error message is displayed in the output window).
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.
Appendix: Support of Oracle features in SQL
Navigator 5.1
Oracle feature
Tables
·
Standard relational tables
·
Partitioned (range, hash and composite)
Tables +
·
Partitioned (list) Tables +++
·
Object tables +
·
Queue tables + (including schedules)
·
Index-organized tables +
·
Temporary tables +
·
External tables +++
Views
·
Standard views
·
Inline views
·
Object views +
·
Join views (including updateable) +
·
Check option on views +
·
Read only option on views +
·
Polymorphic Views +++
·
Views Hierarchies +++
·
Views with Constraints +++
Constraints (definition, clauses and storage)
·
Primary keys
·
Unique keys
·
Foreign keys(including external FKs, views
FKs+++)
Procedures
·
Java/C Methods Calls +
·
Invokers Right +
Functions
Support
YES
YES
YES
YES
NO
YES
YES
YES
YES
YES
YES
YES
YES
YES
NO
NO
NO
YES
YES
YES
YES
YES
YES
YES
·
Java/C Methods Calls +
·
Invokers Right +
Packages
·
Header
·
Body
·
Invokers Right +
Indexes
·
Standard
·
Bitmap
·
Bitmap Join Index +++
·
Descending ++
·
Reverse key +
·
Partitioned +
·
Global +
·
Local +
·
Non-prefixed +
·
Pre-fixed +
·
Function-based ++
Materialized views ++
·
Index-Organized Materialized Views +++
·
Indexes on Materialized Views +++
·
XML, LOB, nested table, varray type columns
YES
YES
YES
YES
YES
YES
YES
YES
NO
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
+++
Materialized view Logs ++
Snapshots (Oracle 7.3.4 up to Oracle 8.0.x Only)
·
Simple and complex
·
Registered
·
Read-only and updateable
·
Complete, ROWID and primary key fast
refreshes
Snapshot logs (Oracle 7.3.4 up to Oracle 8.0.x only)
·
Record with Object ID or Sequence +++
Refresh groups ++
Datatypes
Built-in Datatypes
Character
CHAR
NCHAR+
VARCHAR2
NVARCHAR2+
LONG
CLOB+
NCLOB+
Number
Date types
DATE
TIMESTAMP +++
TIMESTAMP WITH TIME ZONE +++
TIMESTAMP WITH LOCAL TIME ZONE+++
INTERVAL YEAR TO MONTH +++
INTERVAL DAY TO SECOND+++
Binary data types
RAW
LONG RAW
BLOB
NO
NO
NO
NO
NO
NO
NO
NO
NO
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
YES
BFILE +
Binary_Float ++++
Binary_Double ++++
Ids
ROWID
UROWID +
ANSI DB2, SQL/DS datatypes
User defined data types+
Collection Types +
Object Types +
Oracle Supplied types+
"Any" Types +++
XML Types +++
Spatial Types +
Media Types ++
Context Text Types +
Operators
·
User defined ++
·
Ancillary ++
Triggers
·
Standard
·
Instead-of +
·
Database-event +
·
Nested-table view triggers ++
Clusters
·
Non-hash
·
Hash
·
Row level dependency tracking +++
Collections
·
Nested tables +
·
VARRAYs +
Java support
·
JDBC code +
·
SQLJ code +
·
JAVA SOURCE +
·
JAVA CLASS +
·
JAVA RESOURCE +
Database links
PFILE, SPFILE +++
Libraries +
Synonym
Sequence
Dimensions ++
Directories +
Indextypes ++
Jobs
Outlines ++
Policies ++
Histograms
Sum Deltas ++
Object support +
·
Types
·
Attributes
·
Methods
·
REF support(columns and attributes)
YES
YES
YES
YES
YES
YES
YES
YES
NO
YES
NO
NO
NO
NO
NO
NO
YES
YES
YES
YES
YES
YES
YES
NO
YES
YES
YES
NO
NO
YES
YES
YES
YES
NO
YES
YES
YES
YES
YES
YES
YES
NO
NO
NO
NO
YES
YES
YES
YES
·
Inheritance
·
Substitutability
·
Polymorphism
User defined statistics ++
Context Namespaces +
Audit options +
Profiles +
Roles
Privileges
Resources +
·
Resource plans
·
Consumer groups
·
Plan Directives
·
Allocation method
·
Alter Resource Cost dynamically +++
Rulesets ++
External objects ++
Tablespaces
·
Standard
·
Temporary
·
Read-only
·
Locally managed ++
·
Transportable +
·
Undo Tablespace+++
Partition manipulation +
PL/SQL server pages ++
Fine grained access control +
Application contexts +
Labels (Trusted Oracle)
National Language Support
NO
NO
NO
NO
NO
NO
YES
YES
YES
NO
NO
NO
NO
NO
NO
NO
YES
YES
YES
YES
YES
NO
YES
NO
NO
NO
NO
NO
Legend:
+
++
+++
++++
YES
NO
-
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
Supported fully or partially
Not Supported
Not relevant to this product
Further information . . .
Contacting Quest Software
Feel free to contact Quest Software for product information.
Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
Tel:
Internet:
+1 949 754 8000
http://www.quest.com
Email:
mailto:[email protected]
Please refer to our Web site for regional and international office information.
Technical Support
If you have questions about using a Quest Software product, please contact our technical
support staff. To create a Technical Support bundle and send it to Quest Technical
Support, choose Submit Feedback from the Help menu.
To register for online technical support: http://www.quest.com/support