Search Results set_debug_level




Overview
Explore in AI Chat

Overview

OTA_OM_DEBUG is a lightweight PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, with source traceable to the Oracle Learning Management (OTA) module family (the header identifier ottomdbg.pkb and version stamp 120.0 confirm a 12.1.x lineage carried forward unchanged into 12.1.1 and 12.2.2). Its sole business function is to manipulate a single global diagnostic switch, OE_DEBUG_PUB.G_DEBUG_LEVEL, which is exposed by the Oracle Order Management debug publication package. Rather than implementing business logic, OTA_OM_DEBUG acts as a thin, module-scoped wrapper that lets OTA (or any dependent) code raise, lower, or clear the debug verbosity level of the OE_DEBUG_PUB infrastructure without referencing that package directly. It is classified in ETRM as OTHER rather than as a public API, reflecting its internal, non-transactional nature.

Key Procedures and Functions

ETRM documents two procedures, both parameterless in effect and both trivial assignments to the shared global:

  • SET_DEBUG_LEVEL — Accepts a numeric debug level and assigns it to OE_DEBUG_PUB.G_DEBUG_LEVEL. This is the procedure most commonly associated with the search term "set_debug_level." Invoking it raises or lowers the verbosity of downstream OE debug output for the duration of the session.
  • RESET_DEBUG_LEVEL — Provides a deterministic way to return the debug level to zero, effectively disabling debug output. It performs a hard-coded assignment of 0 to the same global.

No functions, exceptions, or additional overloads are documented. Both procedures are declared in the package specification and implemented in the body shown in the ETRM excerpt.

Tables Accessed

No tables are referenced. The package performs no DML or DDL and reads no application data; it manipulates only a package-level PL/SQL variable in memory. Consequently, it has no dependency on APPS synonyms, no row-level locking implications, and no transaction footprint. Any diagnostic output it enables is produced by other packages that honor the OE_DEBUG_PUB global.

Usage Notes

Because OTA_OM_DEBUG is a session-scoped state setter, it is typically invoked manually by developers, support analysts, or DBAs during troubleshooting, for example:

  • From SQL*Plus or another client, calling APPS.OTA_OM_DEBUG.SET_DEBUG_LEVEL(n) to enable tracing, running the suspect transaction, then calling APPS.OTA_OM_DEBUG.RESET_DEBUG_LEVEL to restore normal operation.
  • From custom or extension code that needs to toggle OE debug output programmatically.

It is not a concurrent program and is not called from standard Oracle Forms in delivered flows. The debug level persists for the life of the database session, so sessions should be reset or terminated after diagnosis. ETRM records that the package is referenced by zero other packages, confirming it is a leaf utility with no inbound dependencies. Standard change-control and testing practices apply before use in production.