Search Results alter_lob_size

Overview

SYS.DBMS_AW_EXP is an Oracle-supplied PL/SQL package that resides in the SYS schema and holds VALID status across Oracle E-Business Suite 12.1.1 and 12.2.2. The name follows Oracle's convention for the Analytic Workspace (AW) export/import utility family: the DBMS_AW prefix denotes packages that operate on OLAP analytic workspaces and dimension objects, while the _EXP suffix denotes the export and transport side of that toolkit. In this capacity the package provides the low-level engine used to copy, migrate, and stage analytic workspace data between databases or between schemas within the same database.

Within Oracle EBS the package is not part of the core financials, supply chain, or HR application logic. It belongs to the optional OLAP and business-intelligence infrastructure inherited from the Oracle database server. It is classified as OTHER in the ETRM metadata, indicating it is a database-tier utility rather than a documented EBS application API. The package is owned by SYS, exposed to the schema through a PUBLIC synonym of the same name, and depends directly on STANDARD. It contains both a specification and a body and is listed with 29 documented procedures and functions, most of which are version-specific entry points used to import and transform analytic workspace content.

Key Procedures and Functions

The documented API is organized into versioned import, transaction, and utility groupings. The import routines follow a consistent begin/chunk/finish pattern so that large analytic workspace payloads can be streamed in manageable units:

• IMPORT_BEGIN120, IMPORT_CHUNK120, IMPORT_FINISH120 — the 12.x import sequence.
• IMPORT_BEGIN112, IMPORT_CHUNK112, IMPORT_FINISH112 — the 11.2 import sequence.
• IMPORT_BEGIN100, IMPORT_CHUNK100, IMPORT_FINISH100 — the 10.0 import sequence.
• IMPORT_BEGIN92, IMPORT_CHUNK92, IMPORT_FINISH92 — the 9.2 import sequence.
• TRANS_BEGIN102, TRANS_CHUNK102 — deprecated transaction entry points retained for backward compatibility.
• TRANS_FINISH102, TRANS_FINISH112 — transaction finalization routines for the same legacy versions.
• SCHEMA_INFO_EXP — reports schema and workspace export metadata.
• SCHEMA_CALLOUT — invokes the schema-level callout logic used during exported workspace processing.
• IMPORT_CALLOUT120 — the 12.x callout invoked during import processing.
• ALTER_LOB_SIZE — adjusts the LOB storage or chunk size used when handling exported analytic workspace data.

Tables Accessed

The ETRM metadata for this object records no APPS-synonym table dependencies. This is consistent with a database-tier utility: DBMS_AW_EXP operates on the underlying analytic workspace repository and on the standard package library rather than on EBS application tables. Its only listed dependency is STANDARD, and it is referenced from the PUBLIC and SYS schemas and by SYS.DBMS_CUBE_EXP, which delegates export work to it.

Usage Notes

DBMS_AW_EXP is ordinarily invoked indirectly, not through EBS forms or concurrent programs. It is the export half of the analytic workspace transport pair, paired with DBMS_AW import routines, and is exercised by DBMS_CUBE_EXP and by database export/import utilities when OLAP objects are moved between environments. Typical invocation scenarios include transporting analytic workspaces during a database upgrade, cloning a database that contains OLAP content, or moving workspace definitions between development, test, and production instances.

Because the package is owned by SYS and published through a PUBLIC synonym, it is callable from any schema with the required privileges. Custom code should treat each procedure as an internal, version-specific interface: callers should select the BEGIN/CHUNK/FINISH group that matches the target release and should not assume that an entry point named for one version will behave identically under another. Direct calls are rare; most EBS administrators encounter the package only through Oracle-supplied export and transport jobs, where it remains a valid, dependency-tracked component of the EBS 12.1.1 and 12.2.2 database tier.