Search Results dump_profiler_data




Overview
Explore in AI Chat

Overview

XLA_UTILITY_PROFILER_PKG is a utility package in the APPS schema of Oracle E-Business Suite, residing within the Subledger Accounting (XLA) product family. Its business function is diagnostic rather than transactional: it provides a thin, EBS-owned wrapper around the Oracle database built-in DBMS_PROFILER facility so that Subledger Accounting developers and support engineers can measure the runtime performance of PL/SQL code executed under the XLA architecture. Subledger Accounting processes — including journal creation, accounting program execution, and the Create Accounting engine — are among the most performance-sensitive components of the EBS financials suite, and this package supplies the instrumentation hooks needed to capture line-level execution statistics for that code.

The ETRM metadata classifies the package with an API classification of OTHER and a status of VALID in both 12.1.1 and 12.2.2, indicating that it is a supported, compiled, non-public interface rather than a formally published integration API. It is a dependency of XLA_UTILITY_PKG, which places it on a shared utility layer used across the XLA product rather than within a single functional flow.

Key Procedures and Functions

The package exposes three documented procedures:

  • START_PROFILER — Initialises and begins a profiling session. It is the entry point that activates the DBMS_PROFILER collection mechanism for the calling session so that subsequent PL/SQL execution is instrumented.
  • STOP_PROFILER — Terminates the active profiling session and flushes the collected run data. It is the counterpart to START_PROFILER and is expected to be invoked once the code region of interest has completed.
  • DUMP_PROFILER_DATA — Writes or reports the accumulated profiler results, allowing the captured execution statistics to be retrieved and analysed after a run has been stopped.

The three procedures form a conventional start/stop/report triad. Because the ETRM record does not document parameter lists, no argument signatures are asserted here; callers should inspect the package specification in the target environment before invoking it.

Tables Accessed

No base application tables are referenced directly by XLA_UTILITY_PROFILER_PKG. The ETRM dependency section explicitly states that the package does not reference any database object, and the documented table-level dependencies resolve through APPS synonyms to the database-supplied packages DBMS_PROFILER and DBMS_SQL. DBMS_PROFILER supplies the instrumentation engine and the underlying profiler repository tables, while DBMS_SQL is used for dynamic SQL handling associated with the profiling session. Consequently, the package performs no DML against Subledger Accounting or general ledger data; its persisted output resides in the standard DBMS_PROFILER tables.

Usage Notes

This package is a developer and support utility, not an end-user or scheduled concurrent program component. It is normally invoked from custom PL/SQL test harnesses, SQL*Plus scripts, or debug builds written by Oracle development and advanced support personnel investigating Subledger Accounting performance issues. Typical usage is to wrap a call to the target XLA routine between START_PROFILER and STOP_PROFILER, then invoke DUMP_PROFILER_DATA and query the profiler repository for hot spots. It should never be enabled in a production run of the accounting engine, because profiling imposes significant overhead and writes to shared profiler tables. Because it is referenced by XLA_UTILITY_PKG, customisations that already depend on the XLA utility layer may transitively inherit this package, and any such dependency should be treated as a diagnostic-only coupling.