To set a debug trigger:
If the PL/SQL Interpreter is not already displayed, choose ToolsPL/SQL
Interpreter.
In the Object Navigator, single-click a compiled program unit node to display the program unit in the Interpreter source pane. Note: Uncompiled program units are indicated by an asterisk (*) after their name.
In the Source pane, select the line where you want to create
the debug trigger, then choose ProgramDebugging Triggers
(or right-click in the Source pane and choose Trigger).
Tip: You cannot place a debug trigger on a BEGIN, END, or NULL statement, or on a comment.
In the PL/SQL Trigger dialog box, define the trigger:
If you want the trigger to fire at different location than the current program unit, select a location from the Location list list.
Type the debug trigger in the Trigger Body text box.
For example, to create a debug trigger that interrupts program execution if the local NUMBER variable my_sal exceeds 5000, enter the following as the trigger body:
IF Debug.Getn('my_sal') > 5000 THEN
raise Debug.Suspend;
END IF;
Note: To create a debug trigger that contains multiple lines of text, include a BEGIN and an END statement around the code.
You must raise the DEBUG.SUSPEND exception from the DEBUG package if you want the PL/SQL Interpreter to appear when this line is executed. Otherwise, Reports Builder executes the code silently and the PL/SQL Interpreter does not appear.
Click OK to create a debug trigger for the selected line.
Tip: You can also create a debug trigger by entering commands in the PL/SQL Interpreter pane.
About debug commands in the PL/SQL Interpreter
Copyright © 1984, 2005, Oracle. All rights reserved.