Search Results rollup_run

Overview

SYS.DBMS_PROFILER is the Oracle-supplied PL/SQL profiler package that provides a server-side instrumentation and performance diagnostic interface for PL/SQL code. Within the Oracle E-Business Suite environment—whether running on the 12.1.1 or 12.2.2 technology stack—it is a database kernel component shipped with the RDBMS rather than an EBS application object. It resides in the SYS schema with a status of VALID and is classified under the ETRM as an OTHER API.

The package allows developers and DBAs to measure where execution time is consumed inside PL/SQL programs. It records execution statistics for individual program units, including lines of source code, and stores them in repository tables for later reporting. Because EBS business logic is implemented heavily in PL/SQL packages, APIs, and concurrent program libraries, DBMS_PROFILER is a primary tool for diagnosing performance problems in customized and seeded code.

Key Procedures and Functions

The ETRM metadata documents sixteen procedures and functions. The principal entry points are:

• START_PROFILER — Begins a profiling session, initializing collection of execution statistics.
• STOP_PROFILER — Terminates the profiling session and ceases data collection.
• PAUSE_PROFILER — Temporarily suspends profiling without ending the session.
• RESUME_PROFILER — Restarts collection after PAUSE_PROFILER, allowing selective instrumentation.
• FLUSH_DATA — Forces buffered profiler data to be written to the repository tables.
• GET_VERSION — Returns the version of the profiler package.
• INTERNAL_VERSION_CHECK — Performs an internal version validation, typically invoked to confirm compatibility between the package and its repository tables.
• ROLLUP_UNIT — Aggregates statistics at the program-unit level.
• ROLLUP_RUN — Aggregates statistics for a complete profiling run.

The rollup routines, along with supporting internal procedures, consolidate raw execution data into summary form suitable for reporting.

Tables Accessed

The ETRM record does not enumerate specific base tables; DBMS_PROFILER writes to the PLSQL_PROFILER_DATA, PLSQL_PROFILER_RUNS, and PLSQL_PROFILER_UNITS repository tables created by the appropriate profiling script (for example, profload.sql). The package references SYS and STANDARD, and it is referenced by the APPS and PUBLIC synonyms and by the SYS-owned package body. Within EBS, the APPS synonym permits callers connected to the APPS schema to invoke the profiler without full schema qualification.

Usage Notes

DBMS_PROFILER is generally not invoked from standard EBS forms, concurrent programs, or seeded application flows. It is a development and tuning utility, executed manually from SQL*Plus, SQL Developer, or custom diagnostic code, usually during controlled troubleshooting rather than normal production operation. A typical sequence is START_PROFILER, execution of the suspect EBS package or API, then STOP_PROFILER and FLUSH_DATA, followed by queries against the profiler tables and rollup routines. Because collection imposes overhead and writes to shared repository tables, profiling should be restricted to non-peak windows or test instances. ETRM documents that no other packages reference DBMS_PROFILER, confirming its role as a standalone diagnostic facility rather than an integrated component of EBS application logic.