To debug a report:
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.
After identifying a problem area, choose ToolsPL/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.
Close the PL/SQL Interpreter to run your report.
Browse your debug actions and evaluate application information.
After narrowing the failing code to a specific region, use the PL/SQL Interpreter to implement and test possible code fixes.
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.
About debug commands in the PL/SQL Interpreter
Copyright © 1984, 2005, Oracle. All rights reserved.