To step through the code:
Before proceeding, you must already have set
a debug action such as a breakpoint, and run your program unit at
the PL/SQL Interpreter PL/SQL>
prompt
to suspend execution.
To step to the next line of the suspended program unit:
If the next executable line is a call to a nested subprogram (a program unit that is called from within another program unit), Step Into halts execution at the first line of the nested subprogram.
To step over a nested subprogram call in the suspended program unit:
Step Over executes any calls to nested subprograms and then halts execution at the next executable line of the current program unit.
To step out of a nested subprogram and return to the outer program unit:
If you previously used Step In to descend into a nested subprogram, Step Out completes execution of the nested subprogram and returns to the next line of the original program unit.
To resume program unit execution:
Execution of the program unit continues until the program unit execution has finished, or until interrupted again by another debug action.
Note that if your debug action is located in a PL/SQL LOOP, using Go will cycle through the loop.
To exit suspended execution at the current debug level:
Control is returned to the Interpreter, or to an outer debug level (if any exist).
Next step
Examining or changing local variables
Inserting a Navigator pane in the PL/SQL Interpreter
Copyright © 1984, 2005, Oracle. All rights reserved.