Search Results dbg_stop_debugging

Overview

OWAPUB.DEBUG_CARTX is a PL/SQL package that implements server-side debugging for PL/SQL cartridges using Oracle Procedure Builder. It belongs to the OWAPUB schema, the public schema associated with Oracle Web Application Server/WebDB components embedded in the E-Business Suite technology stack. The package specification carries a copyright notice dated 1991–1998, and its header comments state that it is compatible with Oracle Database 7.3.4 and 8.0.4 or above, Oracle Procedure Builder 6.1 or above, and depends on WebDB 2.1 or above or OAS 4.0.8 or above. In the EBS 12.1.1 and 12.2.2 environments, this object persists as legacy infrastructure inherited from the Oracle Application Server/WebDB generation of the application server tier.

The package coordinates two sides of a debug session: a target connection running the cartridge under test, and a separate debugger or third connection that monitors and controls that session. It manages session state, transports execution results over database pipes, and cleans up global state when debugging terminates. The user of the package must hold Execute permission on the procedure being debugged. The internal package state is represented by a set of status constants, including DEBUG_CARTX_SUCCESS, DEBUG_CARTX_QUIT, DEBUG_CARTX_ABORT, DEBUG_CARTX_SUSPEND, and a series of error codes such as DEBUG_CARTX_ERR_INIT, DEBUG_CARTX_ERR_RDSRC, DEBUG_CARTX_ERR_CRTPROC, and DEBUG_CARTX_ERR_PROC_EXISTS. A dbg_stack collection type of varchar2(2000) indexed by binary_integer supports the debugging call stack.

Key Procedures and Functions

The ETRM metadata documents fourteen procedures and functions. Their documented purposes are as follows:

• RESETDEBUGSESSION — Executed by the target connection; shuts down the debug session and cleans up the pipes and the global area.
• CLEANUPDEBUGSESSION — Executed by a third (debugger or supervisory) connection, typically when errors or hangs occur; shuts down the specified debug session and cleans up pipes and global area.
• GETDEBUGSESSIONID — Returns the identifier for the current or specified debug session.
• GETDEBUGSESSION — Retrieves the state or handle of an active debug session.
• TGT_FETCH_RESULTS — Target-side procedure that fetches results produced by the debugged block.
• TGT_EXEC_BLOCK — Target-side procedure that executes the PL/SQL block under debug.
• DBG_INIT_CGI_ENV — Initializes the CGI environment on the debugger side of the session.
• DBG_SEND_RESULTS — Sends debugger-side results back across the session channel.
• DBG_GET_EXEC_BLOCK — Retrieves the execution block to be run by the target connection.
• DBG_STOP_DEBUGGING — Terminates the debugging activity from the debugger side.
• MISC_GETARGTYPE — Returns the data type of a supplied argument, used in constructing debug calls.
• DBG_GET_SCHEMA_NAME — Returns the schema name associated with the debugging context.
• TGT_INIT_CGI_ENV — Initializes the CGI environment on the target side of the session.

Tables Accessed

The package references no application tables. Its documented database dependencies are the built-in packages DBMS_OUTPUT and DBMS_SQL, reached through APPS synonyms. DBMS_OUTPUT is used to emit diagnostic text from the debugged code, while DBMS_SQL supports dynamic execution of the debug blocks and argument handling assembled at run time. Inter-process communication relies on database pipes rather than on persistent tables, so session state lives in package globals until it is explicitly cleaned up.

Usage Notes

DEBUG_CARTX is invoked programmatically during development and diagnostic troubleshooting of PL/SQL cartridge code, not from standard EBS forms or concurrent programs. A developer establishes a target connection (the session that will run the cartridge) and one or more additional connections that act as debugger or supervisory clients. The target connection initializes the CGI environment via TGT_INIT_CGI_ENV, executes the block through TGT_EXEC_BLOCK, and recovers results with TGT_FETCH_RESULTS. The supervisory connection initializes its own environment with DBG_INIT_CGI_ENV, obtains the block definition through DBG_GET_EXEC_BLOCK, and forwards results with DBG_SEND_RESULTS. Termination is performed by DBG_STOP_DEBUGGING, RESETDEBUGSESSION from the target connection, or CLEANUPDEBUGSESSION from a third connection.

The package is referenced by zero other packages, confirming that it is a standalone utility rather than a dependency of the EBS application code. Because it targets the Oracle Web Application Server/WebDB runtime and Procedure Builder, its operational relevance in EBS 12.1.1 and 12.2.2 is confined to legacy cartridge debugging; general EBS debugging in these releases uses the FND Debug/Diagnostics framework and OAF or Forms-level logging instead.