Summary of Subprograms

Table 8-1 DBMS_DEBUG Package Subprograms

PROBE_VERSION Procedure

SELF_CHECK Procedure

SET_TIMEOUT Function

INITIALIZE Function

DEBUG_ON Procedure

DEBUG_OFF Procedure

ATTACH_SESSION Procedure

SYNCHRONIZE Function

SHOW_SOURCE Procedure

PRINT_BACKTRACE 
Procedure

CONTINUE Function

SET_BREAKPOINT Function

DELETE_BREAKPOINT 
Function

DISABLE_BREAKPOINT 
Function

ENABLE_BREAKPOINT 
Function

SHOW_BREAKPOINTS 
Procedure

GET_VALUE Function

SET_VALUE Function

DETACH_SESSION Procedure

GET_RUNTIME_INFO 
Function

GET_INDEXES Function

EXECUTE Procedure

Common Section

These following subprograms may be called in either the target or the debug session:

• PROBE_VERSION Procedure

• SELF_CHECK Procedure

• SET_TIMEOUT Function

PROBE_VERSION Procedure

This procedure returns the version number of DBMS_DEBUG on the server.

Syntax

DBMS_DEBUG.PROBE_VERSION (
   major out BINARY_INTEGER,
   minor out BINARY_INTEGER); 

Parameters

Table 8-2 PROBE_VERSION Procedure Parameters

major

minor

SELF_CHECK Procedure

This procedure performs an internal consistency check. SELF_CHECK also runs a communications test to ensure that the Probe processes are able to communicate.

If SELF_CHECK does not return successfully, then an incorrect version of DBMS_DEBUG was probably installed on this server. The solution is to install the correct version (pbload.sql loads DBMS_DEBUG and the other relevant packages).

Syntax

DBMS_DEBUG.SELF_CHECK (
   timeout IN binary_integer := 60);

Parameters

Table 8-3 SELF_CHECK Procedure Parameters

timeout

Exceptions

Table 8-4 SELF_CHECK Procedure Exceptions

OER-6516

pipe_creation_failure

pipe_send_failure

pipe_receive_failure

pipe_datatype_mismatch

pipe_data_error

All of these exceptions are fatal. They indicate a serious problem with Probe that prevents it from working correctly.

SET_TIMEOUT Function

This function sets the timeout value and returns the new timeout value.

Syntax

DBMS_DEBUG.SET_TIMEOUT (
   timeout BINARY_INTEGER) 
  RETURN BINARY_INTEGER;

Parameters

Table 8-5 SET_TIMEOUT Function Parameters

timeout

TARGET SESSION Section

The following subprograms are run in the target session (the session that is to be debugged):

• INITIALIZE Function

• DEBUG_ON Procedure

• DEBUG_OFF Procedure

INITIALIZE Function

This function initializes the target session for debugging.

Syntax

DBMS_DEBUG.INITIALIZE (
   debug_session_id  IN VARCHAR2       := NULL, 
   diagnostics       IN BINARY_INTEGER := 0)
  RETURN VARCHAR2; 

Parameters

Table 8-6 INITIALIZE Function Parameters

debug_session_id

diagnostics

Returns

The newly-registered debug session ID (debugID)

DEBUG_ON Procedure

This procedure marks the target session so that all PL/SQL is run in debug mode. This must be done before any debugging can take place.

Syntax

DBMS_DEBUG.DEBUG_ON (
   no_client_side_plsql_engine BOOLEAN := TRUE,
   immediate                   BOOLEAN := FALSE); 

Parameters

Table 8-7 DEBUG_ON Procedure Parameters

no_client_side_plsql_
engine

immediate

DEBUG_OFF Procedure

This procedure notifies the target session that debugging should no longer take place in that session. It is not necessary to call this function before ending the session.

Syntax

DBMS_DEBUG.DEBUG_OFF;

Parameters

None.

Usage Notes

The server does not handle this entrypoint specially. Therefore, it attempts to debug this entrypoint.

Debug Session Section

The following subprograms should be run in the debug session only:

• ATTACH_SESSION Procedure

• SYNCHRONIZE Function

• SHOW_SOURCE Procedure

• PRINT_BACKTRACE Procedure

• CONTINUE Function

• SET_BREAKPOINT Function

• DELETE_BREAKPOINT Function

• DISABLE_BREAKPOINT Function

• ENABLE_BREAKPOINT Function

• SHOW_BREAKPOINTS Procedure

• GET_VALUE Function

• SET_VALUE Function

• DETACH_SESSION Procedure

• GET_RUNTIME_INFO Function

• GET_INDEXES Function

• EXECUTE Procedure

ATTACH_SESSION Procedure

This procedure notifies the debug session about the target program.

Syntax

DBMS_DEBUG.ATTACH_SESSION (
   debug_session_id  IN VARCHAR2,
   diagnostics       IN BINARY_INTEGER := 0); 

Parameters

Table 8-8 ATTACH_SESSION Procedure Parameters

debug_session_id

diagnostics

SYNCHRONIZE Function

This function waits until the target program signals an event. If info_requested is not NULL, then it calls GET_RUNTIME_INFO.

Syntax

DBMS_DEBUG.SYNCHRONIZE (
   run_info       OUT  runtime_info,
   info_requested IN   BINARY_INTEGER := NULL)
  RETURN BINARY_INTEGER;

Parameters

Table 8-9 SYNCHRONIZE Function Parameters

run_info

info_requested

Returns

Table 8-10 SYNCHRONIZE Function Returns

success

error_timeout

error_communication

SHOW_SOURCE Procedure

The best way to get the source code (for a program that is being run) is to use SQL. For example:

DECLARE
	   info DBMS_DEBUG.runtime_info;
BEGIN
   -- call DBMS_DEBUG.SYNCHRONIZE, CONTINUE,
   -- or GET_RUNTIME_INFO to fill in 'info'
   SELECT text INTO <buffer> FROM all_source
   WHERE owner = info.Program.Owner
     AND name  = info.Program.Name
     AND line  = info.Line#;
END;

However, this does not work for non-persistent programs (for example, anonymous blocks and trigger invocation blocks). For non-persistent programs, call SHOW_SOURCE. There are two flavors: one returns an indexed table of source lines, and the other returns a packed (and formatted) buffer.

There are two overloaded SHOW_SOURCE procedures.

Syntax

DBMS_DEBUG.SHOW_SOURCE (
   first_line  IN   BINARY_INTEGER,
   last_line   IN   BINARY_INTEGER,
   source      OUT  vc2_table);

Parameters

Table 8-11 SHOW_SOURCE Procedure Parameters

first_line

last_line

source

Returns

An indexed table of source-lines. The source lines are stored starting at first_line. If any error occurs, then the table is empty.

Usage Notes

This second overloading of SHOW_SOURCE returns the source in a formatted buffer, complete with line-numbers. It is faster than the indexed table version, but it does not guarantee to fetch all the source.

If the source does not fit in bufferlength (buflen), then additional pieces can be retrieved using the GET_MORE_SOURCE procedure (pieces returns the number of additional pieces that need to be retrieved).

Syntax

DBMS_DEBUG.SHOW_SOURCE (
   first_line   IN     BINARY_INTEGER,
   last_line    IN     BINARY_INTEGER,
   window       IN     BINARY_INTEGER,
   print_arrow  IN     BINARY_INTEGER,
   buffer       IN OUT VARCHAR2,
   buflen       IN     BINARY_INTEGER,
   pieces       OUT    BINARY_INTEGER);  

Parameters

Table 8-12 SHOW_SOURCE Procedure Parameters

first_line

last_line

window

print_arrow

buffer

buflen

pieces

PRINT_BACKTRACE Procedure

This procedure prints a backtrace listing of the current execution stack. This should only be called if a program is currently running.

There are two overloaded PRINT_BACKTRACE procedures.

Syntax

DBMS_DEBUG.PRINT_BACKTRACE (
  listing IN OUT VARCHAR2); 

Parameters

Table 8-13 PRINT_BACKTRACE Procedure Parameters

listing

Syntax

DBMS_DEBUG.PRINT_BACKTRACE (
   backtrace OUT backtrace_table); 

Parameters

Table 8-14 PRINT_BACKTRACE Procedure Parameters

backtrace

CONTINUE Function

This function passes the given breakflags (a mask of the events that are of interest) to Probe in the target process. It tells Probe to continue execution of the target process, and it waits until the target process runs to completion or signals an event.

If info_requested is not NULL, then calls GET_RUNTIME_INFO.

Syntax

DBMS_DEBUG.CONTINUE (
   run_info       IN OUT runtime_info,
   breakflags     IN     BINARY_INTEGER,
   info_requested IN     BINARY_INTEGER := NULL)
  RETURN BINARY_INTEGER;

Parameters

Table 8-15 CONTINUE Function Parameters

run_info

breakflags

info_requested

Returns

Table 8-16 CONTINUE Function Returns

success

error_timeout

error_communication

SET_BREAKPOINT Function

This function sets a breakpoint in a program unit, which persists for the current session. Execution pauses if the target program reaches the breakpoint.

Syntax

DBMS_DEBUG.SET_BREAKPOINT (
   program     IN  program_info,
   line#       IN  BINARY_INTEGER,
   breakpoint# OUT BINARY_INTEGER,
   fuzzy       IN  BINARY_INTEGER := 0,
   iterations  IN  BINARY_INTEGER := 0)
  RETURN BINARY_INTEGER;

Parameters

Table 8-17 SET_BREAKPOINT Function Parameters

program

line#

breakpoint#

fuzzy

iterations

Returns

Table 8-18 SET_BREAKPOINT Function Returns

success

error_illegal_line

error_bad_handle

DELETE_BREAKPOINT Function

This function deletes a breakpoint.

Syntax

DBMS_DEBUG.DELETE_BREAKPOINT (
   breakpoint IN BINARY_INTEGER)
  RETURN BINARY_INTEGER;

Parameters

Table 8-19 DELETE_BREAKPOINT Function Parameters

breakpoint

Returns

Table 8-20 DELETE_BREAKPOINT Function Returns

success

error_no_such_breakpt

error_idle_breakpt

error_stale_breakpt

DISABLE_BREAKPOINT Function

This function makes an existing breakpoint inactive, but it leaves it in place.

Syntax

DBMS_DEBUG.DISABLE_BREAKPOINT (
   breakpoint IN BINARY_INTEGER)
  RETURN BINARY_INTEGER; 

Parameters

Table 8-21 DISABLE_BREAKPOINT Function Parameters

breakpoint

Returns

Table 8-22 DISABLE_BREAKPOINT Function Returns

success

error_no_such_breakpt

error_idle_breakpt

ENABLE_BREAKPOINT Function

This function is the reverse of disabling. This enables a previously disabled breakpoint.

Syntax

DBMS_DEBUG.ENABLE_BREAKPOINT (
   breakpoint IN BINARY_INTEGER)
  RETURN BINARY_INTEGER;

Parameters

Table 8-23 ENABLE_BREAKPOINT Function Parameters

breakpoint

Returns

Table 8-24 ENABLE_BREAKPOINT Function Returns

success

error_no_such_breakpt

error_idle_breakpt

SHOW_BREAKPOINTS Procedure

This procedure returns a listing of the current breakpoints. There are two overloaded SHOW_BREAKPOINTS procedures.

Syntax

DBMS_DEBUG.SHOW_BREAKPOINTS (
   listing    IN OUT VARCHAR2);

Parameters

Table 8-25 SHOW_BREAKPOINTS Procedure Parameters

listing

Syntax

DBMS_DEBUG.SHOW_BREAKPOINTS (
   listing  OUT breakpoint_table);

Parameters

Table 8-26 SHOW_BREAKPOINTS Procedure Parameters

listing

GET_VALUE Function

This function gets a value from the currently-running program. There are two overloaded GET_VALUE functions.

Syntax

DBMS_DEBUG.GET_VALUE (
   variable_name  IN  VARCHAR2,
   frame#         IN  BINARY_INTEGER,
   scalar_value   OUT VARCHAR2,
   format         IN  VARCHAR2 := NULL)
  RETURN BINARY_INTEGER;

Parameters

Table 8-27 GET_VALUE Function Parameters

variable_name

frame#

scalar_value

format

Returns

Table 8-28 GET_VALUE Function Returns

success

error_bogus_frame

error_no_debug_info

error_no_such_object

error_unknown_type

error_nullvalue

error_indexed_table

This form of GET_VALUE is for fetching package variables. Instead of a frame#, it takes a handle, which describes the package containing the variable.

Syntax

DBMS_DEBUG.GET_VALUE (
   variable_name  IN  VARCHAR2,
   handle         IN  program_info,
   scalar_value   OUT VARCHAR2,
   format         IN  VARCHAR2 := NULL)
  RETURN BINARY_INTEGER;

Parameters

Table 8-29 GET_VALUE Function Parameters

variable_name

handle

scalar_value

format

Returns

Table 8-30 GET_VALUE Function Returns

error_no_such_object

error_indexed_table

Example

This example illustrates how to get the value with a given package PACK in schema SCOTT, containing variable VAR:

DECLARE
   handle     dbms_debug.program_info;
   resultbuf  VARCHAR2(500);
   retval     BINARY_INTEGER;
BEGIN
   handle.Owner     := 'SCOTT';
   handle.Name      := 'PACK';
   handle.namespace := dbms_debug.namespace_pkgspec_or_toplevel;
   retval           := dbms_debug.get_value('VAR', handle, resultbuf, NULL);
END;

SET_VALUE Function

This function sets a value in the currently-running program. There are two overloaded SET_VALUE functions.

Syntax

DBMS_DEBUG.SET_VALUE (
   frame#               IN binary_integer,
   assignment_statement IN varchar2) 
  RETURN BINARY_INTEGER;

Parameters

Table 8-31 SET_VALUE Function Parameters

frame#

assignment_statement

Returns

Table 8-32 SET_VALUE Function Returns

success

error_illegal_value

error_illegal_null

error_value_malformed

error_name_incomplete

This form of SET_VALUE sets the value of a package variable.

Syntax

DBMS_DEBUG.SET_VALUE (
   handle               IN program_info,
   assignment_statement IN VARCHAR2) 
  RETURN BINARY_INTEGER;  

Parameters

Table 8-33 SET_VALUE Function Parameters

handle

assignment_statement

Table 8-34 SET_VALUE Function Returns

error_no_such_object

In some cases, the PL/SQL compiler uses temporaries to access package variables, and Probe does not guarantee to update such temporaries. It is possible, although unlikely, that modification to a package variable using SET_VALUE might not take effect for a line or two.

Example

To set the value of SCOTT.PACK.var to 6:

DECLARE
   handle  dbms_debug.program_info;
   retval  BINARY_INTEGER;
BEGIN
   handle.Owner     := 'SCOTT';
   handle.Name      := 'PACK';
   handle.namespace := dbms_debug.namespace_pkgspec_or_toplevel;
   retval           := dbms_debug.set_value(handle, 'var := 6;');
END;

DETACH_SESSION Procedure

This procedure stops debugging the target program. This procedure may be called at any time, but it does not notify the target session that the debug session is detaching itself, and it does not abort execution of the target session. Therefore, care should be taken to ensure that the target session does not hang itself.

Syntax

DBMS_DEBUG.DETACH_SESSION;  

Parameters

None.

GET_RUNTIME_INFO Function

This function returns information about the current program. It is only needed if the info_requested parameter to SYNCHRONIZE or CONTINUE was set to 0.

Syntax

DBMS_DEBUG.GET_RUNTIME_INFO (
   info_requested  IN  BINARY_INTEGER,
   run_info        OUT runtime_info)
  RETURN BINARY_INTEGER; 

Parameters

Table 8-35 GET_RUNTIME_INFO Function Parameters

info_requested

run_info

GET_INDEXES Function

Given a name of a variable or parameter, this function returns the set of its indexes, if it is an indexed table. An error is returned if it is not an indexed table.

Syntax

DBMS_DEBUG.GET_INDEXES (
   varname   IN  VARCHAR2,
   frame#    IN  BINARY_INTEGER,
   handle    IN  program_info,
   entries   OUT index_table) 
  RETURN BINARY_INTEGER;

Parameters

Table 8-36 GET_INDEXES Function Parameters

varname

frame#

handle

entries

Returns

Table 8-37 GET_INDEXES Function Returns

error_no_such_object

EXECUTE Procedure

This procedure executes SQL or PL/SQL code in the target session. The target session is assumed to be waiting at a breakpoint (or other event). The call to DBMS_DEBUG.EXECUTE occurs in the debug session, which then asks the target session to execute the code.

Syntax

DBMS_DEBUG.EXECUTE (
   what         IN VARCHAR2,
   frame#       IN BINARY_INTEGER,
   bind_results IN BINARY_INTEGER,
   results      IN OUT NOCOPY dbms_debug_vc2coll,
   errm         IN OUT NOCOPY VARCHAR2);

Parameters

Table 8-38 EXECUTE Procedure Parameters

what

frame#

bind_results

results

errm

Example 1

This example executes a SQL statement. It returns no results.

DECLARE
   coll sys.dbms_debug_vc2coll; -- results (unused)
   errm VARCHAR2(100);          
BEGIN
   dbms_debug.execute('insert into emp(ename,empno,deptno) ' ||
                      'values(''LJE'', 1, 1)',
                      -1, 0, coll, errm);
END;

Example 2

This example executes a PL/SQL block, and it returns no results. The block is an autonomous transaction, which means that the value inserted into the table becomes visible in the debug session.

DECLARE
   coll sys.dbms_debug_vc2coll;
   errm VARCHAR2(100);
BEGIN
   dbms_debug.execute(
       'DECLARE PRAGMA autonomous_transaction; ' ||
       'BEGIN ' ||
       '   insert into emp(ename, empno, deptno) ' ||
       '   values(''LJE'', 1, 1); ' ||
       ' COMMIT; ' ||
       'END;',
       -1, 0, coll, errm);
END;

Example 3

This example executes a PL/SQL block, and it returns some results.

DECLARE
   coll sys.dbms_debug_vc2coll;
   errm VARCHAR2(100);
BEGIN
   dbms_debug.execute(
      'DECLARE ' ||
      '   pp SYS.dbms_debug_vc2coll := SYS.dbms_debug_vc2coll(); ' ||
      '   x  PLS_INTEGER; ' ||
      '   i  PLS_INTEGER := 1; ' ||
      'BEGIN ' ||
      '   SELECT COUNT(*) INTO x FROM emp; ' ||
      '   pp.EXTEND(x * 6); ' ||
      '   FOR c IN (SELECT * FROM emp) LOOP ' ||
      '      pp(i) := ''Ename: '' || c.ename; i := i+1; ' ||
      '      pp(i) := ''Empno: '' || c.empno; i := i+1; ' ||
      '      pp(i) := ''Job:   '' || c.job;   i := i+1; ' ||
      '      pp(i) := ''Mgr:   '' || c.mgr;   i := i+1; ' ||
      '      pp(i) := ''Sal:   '' || c.sal;   i := i+1; ' ||
      '      pp(i) := null;                   i := i+1; ' ||
      '   END LOOP; ' ||
      '   :1 := pp;' ||
      'END;',
       -1, 1, coll, errm);
   each := coll.FIRST;
   WHILE (each IS NOT NULL) LOOP
      dosomething(coll(each));
      each := coll.NEXT(each);
   END LOOP;
END;

PRINT_INSTANTIATIONS Procedure

This procedure returns a list of the packages that have been instantiated in the current session.

PARAMETERS

• pkgs the instantiated packages (OUT)

• flags - bitmask of options:
  • 1 - show specs

  • 2 - show bodies

  • 4 - show local instantiations

  • 8 - show remote instantiations (NYI)

  • 16 - do a fast job. The routine does not test whether debug information exists or whether the libunit is shrink-wrapped.

EXCEPTIONS

no_target_program - target session is not currently executing

NOTES

On return, "pkgs" contains a program_info for each instantiation. The valid fields are: Namespace, Name, Owner, and LibunitType.

In addition, Line# contains a bitmask of:

• 1 - the libunit contains debug info

• 2 - the libunit is shrink-wrapped

PROCEDURE print_instantiations (pkgs IN OUT NOCOPY backtrace_table, flags IN BINARY_INTEGER);

TARGET_PROGRAM_RUNNING Procedure

Return TRUE if the target session is currently executing a stored procedure, or FALSE if it is not.

FUNCTION target_program_running RETURN BOOLEAN;

PING Procedure

Ping the target session, to prevent it from timing out. Use this procedure when execution is suspended in the target session, for example at a breakpoint.

If the timeout_behavior is set to retry_on_timeout then this procedure is not necessary.

EXCEPTIONS

Oracle will display the no_target_program exception if there is no target program or if the target session is not currently waiting for input from the debug session.

PROCEDURE ping;

TIMEOUT OPTIONS

Timeout options for the target session are registered with the target session by calling set_timeout_behavior.

• retry_on_timeout - Retry. Timeout has no effect. This is like setting the timeout to an infinitely large value.

• continue_on_timeout - Continue execution, using same event flags.

• nodebug_on_timeout - Turn debug-mode OFF (in other words, call debug_off) and then continue execution. No more events will be generated by this target session unless it is re-initialized by calling debug_on.

• abort_on_timeout - Continue execution, using the abort_execution flag, which should cause the program to abort immediately. The session remains in debug-mode.

retry_on_timeout CONSTANT BINARY_INTEGER:= 0;

continue_on_timeout CONSTANT BINARY_INTEGER:= 1;

nodebug_on_timeout CONSTANT BINARY_INTEGER:= 2;

abort_on_timeout CONSTANT BINARY_INTEGER:= 3;

SET_TIMEOUT_BEHAVIOUR Procedure

This procedure tells Probe what to do with the target session when a timeout occurs. [This call is made in the target session.]

PARAMETERS

• behavior - one of the following (see descriptions above):

• retry_on_timeout

• continue_on_timeout

• nodebug_on_timeout

• abort_on_timeout

EXCEPTIONS

unimplemented - the requested behavior is not recognized

NOTES

The default behavior (if this procedure is not called) is continue_on_timeout, since it allows a debugger client to re-establish control (at the next event) but does not cause the target session to hang indefinitely.

PROCEDURE set_timeout_behavior (behavior IN PLS_INTEGER);

GET_TIMEOUT_BEHAVIOUR - Returns the current timeout behavior. [This call is made in the target session.]

FUNCTION get_timeout_behavior RETURN BINARY_INTEGER;

OER Breakpoints

Exceptions that are declared in PL/SQL programs are known as user-defined exceptions. In addition, there are Oracle Errors (OERs) that are returned from the Oracle kernel. To tie the two mechanisms together, PL/SQL provides the "exception_init" pragma that turns a user-defined exception into an OER, so that a PL/SQL handler may be used for it, and so that the PL/SQL engine can return OERs to the Oracle kernel. As of the current release, the only information available about an OER is its number. If two user-defined exceptions are exception_init'd to the same OER, they are indistinguishable.

INFORMATION FLAGS

info_getOerInfo CONSTANT PLS_INTEGER:= 32;

REASONS

reason_oer_breakpoint CONSTANT BINARY_INTEGER:= 26;

RUNTIME_INFO

Runtime_info gives context information about the running program.

Probe v2.4:

Added OER. It gets set if info_getOerInfo is set. The OER is a positive number. It can be translated into SQLCODE by translating 1403 to 100, 6510 to 1, and negating any other value.

TYPE runtime_info IS RECORD 
   ( 
       Line#            BINARY_INTEGER,   (duplicate of program.line#) 
       Terminated       BINARY_INTEGER,   has the program terminated? 
       Breakpoint       BINARY_INTEGER,   breakpoint number 
       StackDepth       BINARY_INTEGER,   number of frames on the stack 
       InterpreterDepth BINARY_INTEGER,   <reserved field> 
       Reason           BINARY_INTEGER,   reason for suspension 
       Program          program_info,     source location 
Following fields were added in Probe v2.4 oer              PLS_INTEGER       OER 
(exception), if any 
   ); 

oer_table

Used by show_breakpoints

TYPE oer_table IS TABLE OF BINARY_INTEGER INDEX BY BINARY_INTEGER;

- SET_OER_BREAKPOINT

Set a breakpoint on an OER. The breakpoint persists for the session (or until deleted), as with code breakpoints.

PARAMETERS

oer - the OER (a 4-byte positive number)

RETURNS

success

NOTES

Less functionality is supported on OER breakpoints than on code breakpoints. In particular, note that:

• No "breakpoint number" is returned - the number of the OER is used instead. Thus it is impossible to set duplicate breakpoints on a given OER (it is a no-op).

• It is not possible to disable an OER breakpoint (although clients are free to simulate this by deleting it).

• OER breakpoints are deleted via delete_oer_breakpoint.

FUNCTION set_oer_breakpoint(oer IN PLS_INTEGER) RETURN PLS_INTEGER;

DELETE_OER_BREAKPOINT

Delete an OER breakpoint.

PARAMETERS

oer - the OER (positive 4-byte number) to delete

RETURNS

success

error_no_such_breakpt - no such OER breakpoint exists

FUNCTION delete_oer_breakpoint(oer IN PLS_INTEGER) RETURN PLS_INTEGER;

SHOW_BREAKPOINTS

PARAMETERS

• code_breakpoints - indexed table of breakpoint entries, indexed by breakpoint number.

• oer_breakpoints - indexed table of OER breakpoints, indexed by OER.

• PROCEDURE show_breakpoints (code_breakpoints OUT breakpoint_table, oer_breakpoints OUT oer_table);