Search Results resource_mapping_priority




Overview
Explore in AI Chat

Overview

SYS.DBMS_PRVTRMIE is an Oracle-supplied internal package body that belongs to the Database Resource Manager infrastructure shipped with the Oracle database kernel. In the context of Oracle E-Business Suite 12.1.1 and 12.2.2, the package is part of the SYS schema and exposes private helper logic consumed by the public DBMS_RESOURCE_MANAGER API. The name DBMS_PRVTRMIE denotes a "private" (PRVT) internal implementation companion to the documented resource manager package. It is not an E-Business Suite application object; it is a database component that EBS inherits because the EBS database tier runs on the Oracle RDBMS.

Its business role within EBS is indirect but significant. E-Business Suite deployments frequently use the Database Resource Manager to isolate and prioritize workloads — separating online ATG/OLTP sessions, concurrent manager batch jobs, and reporting or ad-hoc users. The resource plans, consumer groups, and consumer group mappings configured for these purposes are persisted in the data dictionary and manipulated through DBMS_RESOURCE_MANAGER, whose internal implementation delegates to packages such as DBMS_PRVTRMIE. The object's ETRM status is VALID, indicating it is a functioning, dependency-resolved component of the database dictionary.

Key Procedures and Functions

The ETRM documentation records no publicly documented procedures or functions for this package body; it is classified as API type OTHER and is intended for internal use only. Oracle does not publish a callable specification for DBMS_PRVTRMIE, and it should not be invoked directly from EBS forms, concurrent programs, or custom PL/SQL. All functional access to resource manager behavior is performed through the supported public interfaces: DBMS_RESOURCE_MANAGER, DBMS_RESOURCE_MANAGER_PRIVS, and DBMS_RMGR_LIB.

Based on its declared dependencies, the package body provides the private plumbing that supports operations such as staging and validating resource plan and directive definitions, resolving consumer group mappings, and enforcing mapping priority rules before the public APIs commit those definitions to the dictionary. These internal routines are not exposed as a defined API surface.

Tables Accessed

The dependency list identifies the dictionary tables the package body references. These include RESOURCE_PLAN$, which stores resource plan definitions; RESOURCE_PLAN_DIRECTIVE$, which holds the per-plan directives that allocate CPU and degree of parallelism among consumer groups; RESOURCE_CONSUMER_GROUP$, which stores consumer group definitions; RESOURCE_GROUP_MAPPING$, which maps sessions to consumer groups according to session attributes; and RESOURCE_MAPPING_PRIORITY$, which governs the order in which competing mappings are evaluated. All are accessed under the SYS schema as part of resource manager configuration management. In EBS terms, these are the tables that determine how the database arbitrates resources between the EBS application tier, the concurrent processing tier, and any other classified workload.

Usage Notes

DBMS_PRVTRMIE is never invoked directly by EBS application code. It is called internally by DBMS_RESOURCE_MANAGER and related packages when a DBA or an EBS administrator creates, modifies, validates, or deletes resource plans, consumer groups, and mappings. Typical invocation scenarios in an EBS environment include:

  • DBA execution of DBMS_RESOURCE_MANAGER.CREATE_PLAN, CREATE_CONSUMER_GROUP, CREATE_PLAN_DIRECTIVE, and SET_CONSUMER_GROUP_MAPPING during performance tuning of a 12.1.1 or 12.2.2 instance.
  • Implementation of workload separation strategies that segregate concurrent manager sessions from interactive EBS users, a common practice in large-scale or consolidated deployments.
  • Database-level support activities such as upgrade or patching, where the resource manager configuration is validated or rebuilt.

Because the package is owned by SYS and is not referenced by any database object outside its own dependency chain, EBS developers and administrators should treat it as read-only infrastructure. Custom code should always target the documented DBMS_RESOURCE_MANAGER API. Any modification, wrapping, or direct call of DBMS_PRVTRMIE is unsupported and may compromise dictionary integrity or be invalidated during database upgrades and EBS patch application.