Search Results enable_hierarchy

Overview

XDB.DBMS_XDBZ is the Oracle XML DB repository configuration and access control package. In Oracle E-Business Suite 12.1.1 and 12.2.2, the database is provisioned with Oracle XML DB, and the repository under /sys/... and application-specific folders stores XML content, resource metadata, and hierarchy information used by several EBS technology components. DBMS_XDBZ is the API through which the repository hierarchy is enabled for a given XMLType table or view, and through which ACL-based security principals are managed.

The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema rather than the XDB owner. This is significant in EBS, where APPS and product schemas invoke the package under their own context. Its overriding business purpose is to bind application data stored in XMLType columns to the hierarchical, folder-structured model of the XML DB repository, so that resource metadata, versioning, and link semantics are applied consistently and secured through ACLs.

Key Procedures and Functions

Fourteen documented entry points support hierarchy configuration and ACL principal administration.

• ENABLE_HIERARCHY — Enables XML DB hierarchy for a specified XMLType table or view. Parameters include object schema and object name, plus a hierarchy type assembled from the constants ENABLE_CONTENTS, ENABLE_RESMETADATA, ENABLE_VERSION, and ENABLE_LINKS. ENABLE_CONTENTS and ENABLE_RESMETADATA are mutually exclusive, and ENABLE_VERSION must be combined with one of them.
• DISABLE_HIERARCHY — Removes hierarchy enablement, using DISABLE_VERSION or DISABLE_ALL.
• IS_HIERARCHY_ENABLED — Reports whether contents, resource metadata, or versioning are currently enabled.
• GET_ACLOID — Resolves the object identifier of an ACL used by the repository security model.
• GET_USERID — Returns the repository user identifier for a principal.
• VALIDATEACL and VALIDATEFUSIONACL — Validate ACL definitions, including the Fusion-style ACL variant.
• ADD_APPLICATION_PRINCIPAL, SET_APPLICATION_PRINCIPAL, RESET_APPLICATION_PRINCIPAL, DELETE_APPLICATION_PRINCIPAL — Manage application-level ACL principals.
• CHANGE_APPLICATION_MEMBERSHIP — Adds or deletes principal membership using MODE_MEMBERSHIP_ADD or MODE_MEMBERSHIP_DELETE.
• PURGELDAPCACHE and PURGEAPPLICATIONCACHE — Clear cached LDAP and application principal data after directory or ACL changes.

Tables Accessed

Within the documented ETRM metadata, the only referenced object is DUAL, accessed through an APPS synonym. This reflects the package's use of DUAL for constant evaluation and simple resolution queries exposed through its function interfaces, rather than direct DML against application tables. The substantive repository state — resources, ACLs, and hierarchy configuration — resides in the XML DB dictionary tables owned by XDB, which are manipulated internally rather than referenced explicitly through EBS synonyms.

Usage Notes

DBMS_XDBZ is an infrastructure-level package rather than a business-facing API. It is normally invoked during repository configuration, patching, or upgrade operations that must bind an XMLType table to the repository hierarchy, or when ACL principals and memberships must be provisioned or refreshed. In EBS 12.1.1 and 12.2.2, such calls originate from technology stack setup scripts, Oracle XML DB configuration routines, and occasionally from custom code that stores documents in repository-enabled XMLType columns. The documentation identifies three other packages that reference this package, confirming its role as a dependency for higher-level repository utilities. The purge routines should be called after LDAP or application principal changes so that stale cached entries do not produce authorization anomalies. Direct invocation should be restricted to schemas with the necessary XML DB privileges, and hierarchy changes should be treated as structural operations requiring appropriate change control.