A script-enabled browser is required for this page to function properly.

Debugging a report

To debug a report:

  1. Run the report in debug mode to check for logical errors in the report, and displays these as warnings at runtime, before displaying the report output. Running a report in debug mode is not the same as debugging a report using the PL/SQL Interpreter.

  1. After identifying a problem area, choose Toolsright arrowPL/SQL Interpreter to display the PL/SQL Interpreter, and create the desired debug actions (breakpoints and debug triggers) to isolate the failing code to a specific region of number of statement.

  2. Close the PL/SQL Interpreter to run your report.

  3. Browse your debug actions and evaluate application information.

  4. After narrowing the failing code to a specific region, use the PL/SQL Interpreter to implement and test possible code fixes.

Usage notes

When debugging a JSP-based Web report in Oracle JDeveloper, you must disable any breakpoints that are not of source type. If these breakpoints are not disabled, a deadlock is detected. You can disable breakpoints that are not of source type in the Breakpoints window.

See also

About the debugging process

About debug actions

About debug commands in the PL/SQL Interpreter