Results for “delete_cube”

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

Overview

OLAPSYS.CWM2_OLAP_DELETE is an Oracle-supplied PL/SQL package that belongs to the OLAPSYS schema, the repository owner for Oracle's OLAP metadata infrastructure. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this package provides a controlled, programmatic means of removing OLAP metadata objects from the CWM2 (Common Warehouse Metamodel, version 2) repository. The package encapsulates deletion logic so that dependent metadata structures — dimensions, cubes, measure catalogs, and OLAP catalogs — can be retired cleanly rather than through ad hoc DML against repository tables.

In EBS deployments the package supports upstream analytical features that historically relied on Oracle OLAP components, including the database-side generation of analytic workspaces and dimension objects surfaced to reporting and business intelligence tools. Its API classification in the ETRM documentation is "OTHER," reflecting that it is a database-tier utility rather than an EBS application API exposed through standard product interfaces. The central business concern it addresses is maintaining referential consistency of OLAP metadata when analytical objects are reorganized, migrated, or retired.

Key Procedures and Functions

The documented package exposes four procedures. Each is invoked with identifiers for the target object along with controlling arguments such as a report indicator and a delete flag; no parameter lists are reproduced here.

• DELETE_DIMENSION — Removes a dimension definition from the OLAP metadata repository. The procedure accepts a dimension owner and dimension name, and includes a flag governing whether the corresponding CWM1-level dimension definition is also removed, along with reporting and execution controls. This is the procedure most commonly associated with the "delete_dimension" search term.
• DELETE_CUBE — Deletes a cube object identified by its owner and name, subject to the same report and delete control arguments used across the package.
• DELETE_MEASURE_CATALOG — Removes a measure catalog, the metadata container that groups measures associated with analytical structures, identified by catalog name.
• DELETE_OLAP_CATALOG — Deletes an OLAP catalog, with an argument determining whether the underlying CWM1 dimension metadata is removed as part of the operation.

Collectively these procedures provide the sanctioned deletion path for the principal object classes in the CWM2 OLAP model, ordered from the granular dimension and cube level up to catalog-level containers.

Tables Accessed

The package operates against repository tables referenced in EBS through APPS synonyms. Documented references include CWM_OLAP_CUBE, which stores cube metadata and is therefore the primary target of cube deletion activity; CWM_CLASSIFY, which holds classification relationships that must be considered when objects are removed; and CWM_UTILITY, a helper package or table used for internal repository operations. The package also references DBMS_ASSERT, the Oracle-supplied assertion utility used to validate schema and object name inputs, which reduces the risk of SQL injection through dynamically constructed identifiers. Deletion operations inherently modify or clear rows in these repository structures and may cascade to dependent metadata rows that reference the removed object.

Usage Notes

CWM2_OLAP_DELETE is a database-tier utility rather than a directly invoked EBS form function. It is typically called from custom PL/SQL scripts, administrative routines, or Oracle-supplied maintenance code when OLAP metadata must be retired — for example, during cleanup of obsolete analytical definitions, before re-creating a dimension or cube, or as part of environment refresh procedures. In EBS 12.1.1 and 12.2.2 it should be invoked as the OLAPSYS owner or by a user with equivalent privileges, since the underlying objects reside in that schema. Because the package performs destructive metadata operations, deletions should be preceded by a validated backup or export of the affected repository objects, and the report parameter should be used first to preview the intended action where supported. The metadata indicates the package is referenced by zero other packages, confirming that it is a terminal utility with no internal EBS dependencies and that callers must manage invocation, error handling, and transactional control themselves.