Chat now with support
Chat with Support

SQL Navigator for Oracle 7.4 - User Guide

Quick Overview Working With SQL Navigator Navigation Oracle Logon Code Editor Visual Object Editors Team Coding and Version Control Systems Modules, Windows And Dialogs
Analyze Tool Auto Describe Tool Benchmark Factory Bookmarks Dialog Capture Web Output Change Logon Password Dialog Code Analysis Code Assistant Code Road Map Code Templates Code Test Database Source Code Search Dialog DB Navigator Describe Difference Viewer Edit Data ER Diagram Explain Plan Tool Export Table Find and Replace Dialog Find objects Dialog Find Recycle Bin Objects Dialog Formatting Options HTML Viewer Import HTML as PL/SQL Import Table Java Manager Job Scheduler Locate In Tree Output Window PL/SQL Profiler Profile Manager Project Manager Publish Java to PL/SQL Quick Browse Rename Object Search Knowledge Xpert Select DB Object Dialog Server Output Server Side Installation Wizard Session Browser Source Preview SQL Modeler SQL Optimizer Task Manager Web Support Configuration Dialog Wrap Code
View | Preferences About Us


Code Editor

SQL Development

The Code Editor opens ready to edit SQL code.

More Information Brief Description
Code Editor SQL The Code Editor toolbar in SQL development.
Edit, Compile And Execute Write SQL code. Compile the code.
SQL Query Results Data Grid Browse the results of executed SQL queries.
SQL Query Log (The Spool Tab) View a log of executed SQL statements. Retrieve executed SQL statements.

PL/SQL Development

The Code Editor layout for PL/SQL development is used when a stored object is opened or is being created.

More Information Brief Description
Code Editor PL/SQL The Code Editor toolbar in PL/SQL development.
Edit, Compile And Execute Write PL/SQL code. Compile the code.
PL/SQL Execution Console Set input parameters. Run the PL/SQL program.
Icon More Information Brief Description
Code Explorer Show a hierarchical view the code.
Outline Show the syntax tree of the current source.
DB Explorer Find and open database objects.
Describe Show the data structure for tables, indexes, views and synonyms.
History Show the most recent successfully executed SELECT, UPDATE, DELETE commands and PL/SQL blocks in the current session.
Dependencies Show the Dependants and Depends On objects of the current script.
Columns Show/hide columns of the retrieved table in the data grid.

PL/SQL Debugger

Tools and features for debugging stored programs.

Show/Hide the PL/SQL Debugger in the Toolbox from the Code Editor toolbar.


  • Align the Toolbox left or right of the Code Editor (Right Click on the Toolbox).
  • Pin/Unpin the Toolbox to allow more editing space.

PL/SQL Debugger

Code Editor > Toolbox > PL/SQL Debugger

Note: Show/Hide PL/SQL Debugger in the Toolbox from the Code Editor toolbar.

All the tools and features for debugging stored programs can be found inside the PL/SQL Debugger window.

Use the debugger to perform the following functions:

  • Run to the end or to the next breakpoint.
  • Step over code.
  • Step into code, when other procedures are called from the current line.
  • Display the execution stack.
  • View and modify any variable value.
  • Set watch variables.
  • Set and remove breakpoint on the fly as the code is executing, except in an anonymous block.
  • Stop a running procedure.
  • Set an option to either stop execution if an exception occurs, or ignore exceptions.


Area Requirement

Oracle server connection

Debugging is functional only when you are connected to an Oracle server via a SQL*Net connection. If you are using a local database, such as Personal Oracle, use the loopback SQL*Net connection to perform interactive debugging.

Oracle Permissions

create session

alter session

Debug on/off

To watch, evaluate, or modify variables of a stored program:

Compile the program with debug information: Session Menu | Include Debug Info.

Successful compile

If the procedure fails to compile, it is displayed in red in DB Navigator. It cannot be debugged.



Feature Description

Locals tab

Use the Locals tab to test the effect of different variable values in your procedure.

Example Scenario: Your procedure performs a computation. Start the procedure, enter a starting value and watch how the procedure handles the result. If you want to see a "what if" computation, enter a new value for the variable in the Locals tab and repeat the procedure.


  • If you see an error such as "Not compiled with debug info" instead of the variable value, you need to recompile the procedure with the Debug information and re-execute it in the debugger to see the value of variables. See Session Menu | Include Debug Info for more information.
  • The values in the Locals tab are only populated when the code is running.
  • The values of the input parameters cannot be modified in the Locals tab.
  • When you evaluate a variable in a current breakpoint, remember that the current breakpoint has not yet been executed.

REF CURSOR type variables

When evaluating/watching a variable of REF CURSOR type, its value is displayed in the following format:

flags:FFF, rowcount:RRR.

RRR determines the number of records fetched so far by the examined cursor.

FFF is a combination of cursor status flags:




If the user enters the watched variable names as C1%NOTFOUND, C1%FOUND, C1%ISOPEN, C1%ROWCOUNT, the displayed value is the same as would result from watching the cursor itself. (C1 is the name of the cursor)

Watches and Breakpoints

You can set breakpoints and watches at any time before or during a debug session. You do not have to recompile your program after you set breakpoints or watches.

Add/remove breakpoints by clicking in the gutter margin left of the code. For more information, see Edit, Compile And Execute. There is also an icon on the toolbar to toggle on/off breakpoints. For more information, see Code Editor PL/SQL.

When execution of a procedure is paused at a breakpoint, you can evaluate or modify any scalar variable within procedure code. If you change the value of a variable, you can confirm the new value of the scalar variable by evaluating the variable again.


  • You can open multiple editors and set breakpoints in several stored programs simultaneously.
  • When you evaluate a variable in a current breakpoint, remember that the current breakpoint has not yet been executed.
  • Variable values in the "watch" window are updated only at the breakpoint, so strategically place breakpoints after the watch variable.
  • Increasing the number of variables in the watch list may result in slower debugger performance.

Code Explorer

Code Editor > Toolbox > Code Explorer

Make your work with packages, procedures, and functions more efficient and error-free.


Code Explorer:

  • Is based on an advanced parsing technique that understands PL/SQL syntax.
  • Displays detailed information about a package’s components, such as variables and parameters, their types, structure and cursors.
  • Highlights the packaged procedure you are currently in.
  • Supports drag-and-drop into the editor.
  • Combines information from the specification and body.
  • Distinguishes non-published procedures and functions (by icon).

Working with packages

Work with packages is fast and easy in the Code Editor with the integrated Code Explorer.

The Code Explorer graphically displays a tree-structure view of the package currently in the editor. It shows variables, parameters, record structures, types, cursors, and so on.

The tree-view is synchronized with the editing cursor in the code-editing window, so when you click any package component in the tree-view, you can see the corresponding PL/SQL code in the editing window. Likewise, as you move the cursor in the editing window, the tree-view changes to show the object corresponding to the PL/SQL code at the cursor location.

Auto Reparse

PL/SQL parsing occurs when the editor first loads objects, and in the background as the user edits the code. You can also manually trigger a full reparsing (updating of the internal symbol table) at any time by right-click and select Auto Reparse from the shortcut menu. However, when loading a really large script having this option on will slow down SQL Navigator. Hence, to avoid wasting CPU resources, you should turn this option off when editing large scripts.


Code Editor > Toolbox > Outline

A graphic representation of the syntax tree of the current source.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating