Search Results fnd_debug_util




Overview
Explore in AI Chat

Overview

FND_DEBUG_UTIL is a utility package in the Oracle E-Business Suite Applications (APPS) schema that supports diagnostic and debugging activities for PL/SQL code executing within an EBS environment. Its central purpose is to expose session-level runtime diagnostic information—specifically, the identity and location of the Oracle trace file associated with the current database session—and to provide controlled control over PL/SQL profiling and logging. The package is declared with AUTHID CURRENT_USER, meaning its procedures and functions execute with the privileges of the invoking user rather than the package owner, which allows it to be called safely from a variety of session contexts across the EBS application tier.

The package is largely oriented toward developers and support personnel who need to capture and analyze trace output. By returning the trace file name and the node on which the trace file is created, it enables callers to locate diagnostic artifacts without manually querying dynamic performance views. Its profiling and logging entry points allow trace and log activity to be started and stopped programmatically, which is useful when debugging concurrent programs, forms-based transactions, or batch processes.

Key Procedures and Functions

  • get_trace_file_name — Returns the fully qualified trace file name for the current database session, including the directory path (for example, $ORACLE_HOME/log/udump/ora_8085.trc). It resolves the session's trace location so callers can report or retrieve the file for analysis.
  • get_trace_file_node — Returns the name of the node (machine) on which the trace file for the current session is generated. This is important in multi-node (RAC or multi-tier) deployments where the trace file may reside on a different application or database server than the one the user is connected through.
  • stop_plsql_profiler — Stops the PL/SQL profiler by calling FND_TRACE and submits a concurrent request to generate the profiler output. It updates the request identifier in FND_DEBUG_RULE_EXECUTIONS as log_request_id, tying the profiling run to its output request.
  • enable_logging — Enables logging at a specified log level, allowing the caller to control the verbosity of diagnostic output for the session.

Tables Accessed

The package references several objects, primarily through APPS synonyms. FND_DEBUG_RULE_EXECUTIONS is read and written; it stores debugging rule execution metadata, and stop_plsql_profiler updates its log_request_id column to associate a profiling run with the concurrent request that produces the profiler output. Dynamic performance views—V$INSTANCE, V$PARAMETER, V$PROCESS, and V$SESSION—are queried to derive session and instance context, including trace file location and node information. DUAL and DBMS_UTILITY are used for standard PL/SQL utility operations and single-row queries. Because trace file details depend on database-side parameters and session state, these views are essential to the package's diagnostic functions.

Usage Notes

FND_DEBUG_UTIL is typically invoked from custom PL/SQL code, concurrent program logic, or diagnostic scripts rather than being driven directly by a standard EBS form. Developers embed calls to get_trace_file_name and get_trace_file_node when they need to capture the trace artifact path for a running session—for example, to write it to a log table or display it during troubleshooting. stop_plsql_profiler is used at the end of a profiling cycle to halt collection and submit the concurrent request that materializes the profiler report, while enable_logging sets the session's logging verbosity. Because the package is not referenced by other documented packages, it functions as a leaf-level utility intended for direct invocation by application code or support tooling. In RAC or multi-node environments, callers should retrieve both the trace file name and node name to reliably locate the file.