Search Results prvt_awr_data




Overview
Explore in AI Chat

Overview

SYS.PRVT_AWR_DATA is a private package body in the SYS schema that forms part of the Oracle Automatic Workload Repository (AWR) infrastructure shipped with the Oracle Database. It is not an Oracle E-Business Suite application object. In EBS 12.1.1 and 12.2.2 the database always runs on a certified Oracle Database release (11gR2 or 12c/19c), and AWR is the mandatory performance-diagnostics subsystem of that database. PRVT_AWR_DATA is therefore present in every EBS instance even though it belongs to the database tier rather than to the APPS schema.

Its business function is to provide the internal data-management layer for AWR repository content. Where the public DBMS_WORKLOAD_REPOSITORY package exposes administrative APIs to DBAs, PRVT_AWR_DATA supplies the private helper routines that interpret, aggregate, and return the underlying data stored in the WRH$ and WRI$ family of tables. The AWR report and Active Session History (ASH) reporting engines call into this layer to construct the data structures consumed by the report generators. In ETRM it is classified with API classification OTHER; it is a supporting engine rather than a documented public interface.

Key Procedures and Functions

The ETRM 12.2.2 record documents status VALID with zero published procedures or functions. This is expected: PRVT_AWR_DATA is a private package, and Oracle does not document its internal subprogram interfaces. The documented dependency list nonetheless indicates the functional areas the body covers.

  • DBMS_ASH_INTERNAL — the body relies on the internal ASH engine to obtain Active Session History samples used for session-level and SQL-level drill-down.
  • PRVT_AWR_PERIOD — dependency confirms period and snapshot-range resolution logic, establishing the begin and end snapshot boundaries for a reporting interval.
  • PRVT_AWR_INST_META and PRVT_AWR_INST_META_TAB — dependencies confirming internal handling of instance metadata and collections of instance attribute records across RAC configurations.
  • PRVT_AWR_NUMTAB — a numeric collection type used to marshal arrays of values through the private interfaces.
  • PLITBLM — a PL/SQL index-by table type used as a generic in-memory record container.
  • XMLTYPE — indicating that portions of the data path accept or emit XML, consistent with AWR's use of XML for report data transfer.

Per ETRM policy, no parameter lists are asserted for these private routines; only their existence and purpose are documented.

Tables Accessed

No APPS-synonym tables are documented against this object, which is consistent with a SYS-owned database-tier package. The body reads and writes AWR repository tables directly, principally the WRH$ workload-history tables (such as WRH$_ACTIVE_SESSION_HISTORY, WRH$_SQLSTAT, and WRH$_SYSTEM_EVENT) and the snapshot definition tables WRM$_SNAPSHOT and WRM$_DATABASE_INSTANCE. It also reads DUAL, which appears explicitly in the dependency list. These tables hold the sampled performance statistics that AWR reports aggregate, and access to them must pass through the private layer so that retention, baseline, and privilege rules are enforced consistently.

Usage Notes

PRVT_AWR_DATA is never invoked directly. In an EBS environment it is reached indirectly through the standard database-side entry points:

  • DBMS_WORKLOAD_REPOSITORY public APIs, including AWR_REPORT_HTML, AWR_REPORT_TEXT, and the ASH report variants, used by DBAs for EBS database performance diagnosis.
  • Oracle Enterprise Manager and the Automatic Diagnostic Repository tooling, which call the AWR reporting layer rather than the private package.
  • Scheduled snapshot collection driven by the MMON and MMNL background processes, and by DBMS_WORKLOAD_REPOSITORY.MODIFY_SNAPSHOT_SETTINGS.

The documented dependency list records that SYS.PRVT_AWR_DATA is referenced by one other package and is not referenced by any other database object, confirming its position as a leaf-side internal dependency invoked by higher AWR packaging. Because it is a private, SYS-owned body, it must not be modified, wrapped, or invoked from EBS custom code; any customization or direct call risks invalidating the AWR infrastructure and is unsupported. Application code in the APPS schema should interact only with the supported DBMS_WORKLOAD_REPOSITORY interface.