Results for “export_all”

6 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OLAPSYS.CWM$EXPORT package is an Oracle-supplied PL/SQL package owned by the OLAPSYS schema. It belongs to the Oracle OLAP metadata infrastructure that underlies the Common Warehouse Metamodel (CWM) repository used by Oracle's analytical workspace and OLAP option. Its business function is to generate a portable script of API calls that can recreate the contents of an OLAP repository or an individual OLAP catalog. Because OLAP analytic workspaces, dimensions, cubes, and measures are defined as metadata rather than as flat relational rows, the ability to emit that metadata as a replayable script is essential for migration, cloning, backup, and promotion of analytic definitions between environments.

Within the Oracle E-Business Suite 12.1.1 and 12.2.2 context, this package is not part of the EBS application schema proper. It is an Oracle database component referenced through the APPS synonym layer and is listed under the "OTHER" API classification in the ETRM registry. It is relevant to EBS installations that have deployed the OLAP option or analytical workspace features, particularly where DBA_OLAP_* views are exposed.

Key Procedures and Functions

The ETRM metadata documents two procedures for this package:

  • EXPORT_ALL — Generates a script of API calls intended to recreate the entire contents of the repository. It writes the resulting script into a handle to a database CLOB, making the output streamable and storable without an operating-system file dependency.
  • EXPORT_CATALOG — Generates a script of API calls to recreate the contents of a single catalog. It accepts a catalog identifier and, like the sibling procedure, emits the generated script to a CLOB handle. This allows selective export rather than a full repository dump.

Both procedures are procedural only; no functions are documented. The design pattern is consistent with a metadata "script generator" utility: the caller supplies an output container, and the package populates it with the ordered API invocations needed to rebuild the definitions.

Tables Accessed

The package reads from the OLAP repository dictionary views rather than from EBS transactional tables. The documented set includes DBA_OLAP_CATALOGS and DBA_OLAP_CATALOG_ENTITY_USES for catalog-level structure; DBA_OLAP_CUBES, DBA_OLAP_CUBE_DIM_USES, DBA_OLAP_CUBE_MEASURES, DBA_OLAP_CUBE_MEASURE_DIM_USES, and DBA_OLAP_CUBE_MEASURE_MAPS for cube, measure, and measure-mapping metadata; and DBA_OLAP_DIMENSIONS, DBA_OLAP_DIM_ATTRIBUTES, DBA_OLAP_DIM_ATTR_USES, DBA_OLAP_DIM_HIERARCHIES, and DBA_OLAP_DIM_LEVELS for dimension, hierarchy, level, and attribute definitions. Finally, DBA_OLAP_DESCRIPTORS, DBA_OLAP_DESCRIPTOR_TYPES, and DBA_OLAP_ENTITY_DESC_USES capture descriptive and type metadata attached to entities.

Access to these views is documented via APPS synonyms, confirming that the package operates in a shared dictionary model where the exporting session must hold privileges on the underlying OLAP views. The wide view coverage explains why the package can faithfully reconstruct a complete analytical environment: it traverses the full dependency graph of catalog, cube, measure, dimension, and descriptor objects.

Usage Notes

CWM$EXPORT is normally invoked programmatically rather than from an EBS form. Typical call sites include custom migration or cloning scripts, concurrent programs built to snapshot OLAP metadata, and higher-level OLAP administration utilities — one other package is documented as referencing it. A common usage pattern is to declare a local CLOB variable, call EXPORT_CATALOG or EXPORT_ALL, and then persist or spool the returned script for execution in a target environment. Because the package is owned by OLAPSYS, direct execution is generally restricted to privileged accounts; DBAs and EBS technical consultants should invoke it through the owning schema or via an appropriately granted synonym. The export_catalog search term corresponds directly to the documented EXPORT_CATALOG procedure, which is the targeted entry point for exporting a single named catalog.