Search Results equals_path




Overview
Explore in AI Chat

Overview

DBMS_CUBE_EXP is a SYS-owned PL/SQL package body that forms part of Oracle's server-side Analytic Workspace (AW) and OLAP infrastructure. In an Oracle E-Business Suite 12.1.1 or 12.2.2 environment, this package provides the export and transport utilities used to move OLAP analytic workspaces, cubes, and related metadata between database instances and file system or XML DB (XDB) repository locations. Because it is shipped as part of the core RDBMS component (SYS schema) rather than as an EBS product schema object, it is available to EBS whether or not the optional OLAP or Demand Planning options are licensed, but it becomes functionally significant only when OLAP features are exercised.

The package is essentially the public entry point for cube export operations. Internally it coordinates lower-level components such as DBMS_AW, DBMS_AW_EXP, DBMS_CUBE, DBMS_DATAPUMP, and DBMS_OLAPI_LIB to build an export definition, identify the objects to be written, and stream the resulting XML or binary artifacts to a designated destination. Its status is VALID in the ETRM inventory, confirming that the compiled body is present and usable in the documented release.

Key Procedures and Functions

The ETRM metadata for this object documents no individually named procedures or functions; the documented API surface is presented only at the package-body level, and the procedure list is empty in the supplied excerpt. This is consistent with DBMS_CUBE_EXP being treated as an internal or restricted-usage package whose entry points are normally reached indirectly through DBMS_CUBE, DBMS_AW_EXP, or Enterprise Manager-driven OLAP export workflows rather than being called by name from EBS application code. Consultants should therefore treat any direct invocation of its subprograms as unsupported unless explicitly documented by Oracle for the target release.

The substantive relationships captured in the metadata are dependencies rather than procedure signatures. The package body resolves calls into PUBLIC synonyms and XDB objects (DBMS_XDB, EQUALS_PATH, RESOURCE_VIEW, UNDER_PATH), into SYS dictionary and OLAP packages (ALL_AWS, ALL_OBJECTS, ALL_TABLES, DBMS_AW, DBMS_AW_EXP, DBMS_CUBE_EXP itself for internal recursion, DBMS_DATAPUMP, DBMS_LOB, DBMS_OLAPI_LIB, DBMS_ZHELP, PLITBLM, STANDARD, TABLE_PRIVILEGE_MAP, XMLTYPE, XDB), and into DBMS_ASSERT for identifier validation. No database object in the EBS schema set is documented as referencing DBMS_CUBE_EXP, which reinforces its role as a leaf-level infrastructure package.

Tables Accessed

According to the documented dependency list, the package reads from data dictionary views rather than from application tables. ALL_AWS enumerates the analytic workspaces visible to the current user, while ALL_OBJECTS and ALL_TABLES are used to resolve the underlying relational objects that back those workspaces and to verify their existence and ownership. TABLE_PRIVILEGE_MAP supplies privilege code translations used during authorization checks. DBMS_OLAPI_LIB provides the OLAP API library interface, and DBMS_ASSERT is used to validate schema and object name inputs before they are interpolated into dynamic SQL. No EBS product tables (for example, in the GL, INV, or MRP schemas) are documented as being read or written by this package, confirming that it operates entirely within the OLAP/XDB domain.

Usage Notes

In EBS 12.1.1 and 12.2.2 the package is not invoked from standard concurrent programs or Oracle Forms. It is reached when an administrator exports an analytic workspace, typically through DBMS_AW_EXP, Oracle Enterprise Manager, or OLAP worksheet commands, or when a custom integration script performs a cube transport. Because the metadata shows no inbound references from application packages, customizations must not assume the package is the supported integration point. The user search term "equals_path" corresponds to the XDB SQL operator EQUALS_PATH, which this package body references as part of its repository path handling, not as a callable subprogram; the same applies to UNDER_PATH and RESOURCE_VIEW. Any change to XDB configuration, repository permissions, or the OLAP option availability can therefore affect the package's behavior even though it is VALID.