Search Results purge_data

Overview

APPS.FND_TRACE_UTILS is a utility package in Oracle E-Business Suite that supports the collection, reporting, and management of PL/SQL profiler data generated during runtime diagnostics. Its principal role is to surface the results captured by the PL/SQL hierarchical profiler and present them in a structured report, while optionally clearing historical profiler data so that the underlying repository does not grow without bound. In EBS 12.1.1 and 12.2.2 the package remains an internal, non-shipped (noship) utility, indicated by its header revision ($Header: AFPMUTLS.pls 120.2 2005/11/03). It is not exposed as an end-user API and is not referenced by any other packaged code, confirming its status as a diagnostic helper invoked directly by administrators or Oracle Support during performance investigations.

Key Procedures and Functions

The ETRM metadata documents a single procedure name, PLSQL_PROF_RPT, exposed through two overloads:

• PLSQL_PROF_RPT (concurrent program form) — Includes the standard concurrent program OUT parameters (errbuf and retcode) alongside the run identifiers, the PURGE_DATA flag, and the CUTOFF_PCT threshold. This form is designed to be registered and executed as a concurrent program so results are delivered through the standard concurrent manager reporting mechanism.
• PLSQL_PROF_RPT (direct call form) — Omits errbuf and retcode but otherwise accepts the same run identifiers, PURGE_DATA, and CUTOFF_PCT arguments, allowing the procedure to be called directly from PL/SQL for ad hoc reporting.

Both overloads accept RUN_ID and RELATED_RUN to identify the profiling run(s) to report on, PURGE_DATA to control whether profiler data is deleted after reporting, and CUTOFF_PCT to limit output to entries above a percentage threshold. The "purge_data" search term maps directly to the PURGE_DATA parameter, which defaults to 'Y'.

Tables Accessed

The package reads from the following dictionary views via APPS synonyms:

• ALL_OBJECTS — resolves the object identity (name, type, owner) associated with profiled code units.
• ALL_TABLES — identifies table-level metadata relevant to the reporting scope.
• DUAL — used for single-row computations and default evaluations.
• V$INSTANCE — supplies instance-level context, distinguishing which instance produced the profiler data in multi-instance (RAC) deployments.

Writes to the PL/SQL profiler repository are implied by the PURGE_DATA behavior, though the profiler tables themselves are not enumerated in the documented metadata.

Usage Notes

FND_TRACE_UTILS is typically invoked during performance troubleshooting. The concurrent program form is submitted through the Concurrent Programs window when a DBA or developer needs a formatted profiler report delivered as a concurrent request output; the PL/SQL form is used for interactive or scripted analysis. Because PURGE_DATA defaults to 'Y', repeated diagnostic runs will delete previously captured profiler data unless the flag is explicitly set to 'N', and CUTOFF_PCT allows suppression of low-impact entries to keep reports focused. Administrators should exercise care when enabling purging in environments where historical profiling evidence must be preserved.