You can temporarily disable breakpoints and enable them later, in the same Builder session. Disabling and enabling breakpoints help you to identify the specific region of code where a runtime error could be located.
Suppose you have set breakpoints at lines 10 and 50 to debug code within that region. To further define the scope, you can disable the breakpoint at line 10 and set a breakpoint at line 20 to debug code between lines 20 and 50. If the error is not located in the new region, you would then enable the breakpoint at line 10 to debug code between lines 10 and 20 instead.
To disable or enable a breakpoint:
A breakpoint is identified by a source unit name and a line number at which it is set.
Or,
To enable a breakpoint, select the checkbox next to the name.
Disabled and enabled breakpoints in the PL/SQL Editor are identified by different colored icons (for Windows). A grey ball indicates that the breakpoint is disabled; a red ball indicates that the breakpoint is enabled.
When you disable and enable breakpoints using the Breakpoints window, the colored breakpoint icons change accordingly in the editor.