Locally Debugging PL/SQL Programs

When locally debugging PL/SQL programs, the call to initiate debugging is made directly from within JDeveloper. JDeveloper automatically launches the program you want to debug, also referred to as the debuggee process, and then attaches the debugger to that program.

See About Debugging PL/SQL Programs and Java Stored Procedures for information about how to use the debugger with PL/SQL programs and Java stored procedures in the Oracle database. Also, make sure that you've completed the documented prerequisites.

To locally debug a PL/SQL program in JDeveloper:

If not already done, create a database connection using the Database Wizard.
In the Navigator, expand the Database node to display the specific database user name and schema name.
Expand the Schema node.
Expand the the appropriate node depending on what you are debugging: Procedure, Function, or Package Body.
Select the procedure, function, or package that you want to debug and double-click to open it in the Code Editor.
Set a breakpoint in the PL/SQL code by left-clicking in the margin.
Note: The breakpoint must be set on an executable line of code. If the debugger does not stop, the breakpoint may have not been set on an executable line of code (check that the breakpoint was verified). Also, verify that the debugging PL/SQL prerequisites were met. In particular, make sure that the PL/SQL program is compiled in INTERPRETED mode.
Make sure that the PL/SQL program unit you want to debug is currently selected in the Navigator.
Click the Debug toolbar button.
JDeveloper halts the execution at the first breakpoint (providing that this was set in the Start Debugging Option in the Project Properties dialog) and displays the state in the debugger windows.
Look at the debug information displayed in the JDeveloper debugger windows. See Moving Through Code While Debugging.
Resume debugging the PL/SQL program until you are satisfied.