Search Results dbms_aw_lib




Overview

SYS.DBMS_CUBE_LOG is a server-side PL/SQL package body owned by the SYS schema and shipped as part of the Oracle Database server itself, not as an E-Business Suite product schema object. In the context of Oracle EBS 12.1.1 and 12.2.2, it provides the internal logging and tracing infrastructure used by Oracle's OLAP and analytical workspace components, principally DBMS_AW (Analytical Workspace) and DBMS_CUBE. These components are invoked during EBS operations that touch OLAP-based summarization, dimension hierarchies, and analytical workspace objects — most notably within reporting and planning flows that leverage the database OLAP option.

The object is reported as VALID in ETRM and is classified as API type OTHER, indicating that it is not an end-user application API but rather a supporting framework package. It is documented with 36 procedures and functions, exposing a logging API that other SYS-owned analytical packages call internally when they execute cube builds, dimension compiles, and query operations.

Key Procedures and Functions

The documented API centers on log lifecycle and configuration:

  • ENABLE / DISABLE — Turn logging on or off for the analytical session. Control procedures that gate whether subsequent write operations are persisted.
  • DEFAULT_NAME — Returns the default logical name for a log context, used when callers do not supply an explicit identifier.
  • GET_LOG / GET_LOG_SPEC / SET_LOG_SPEC — Retrieve the active log, read the current logging specification, and define the specification (destinations, verbosity, targets) governing log output.
  • SET_PARAMETER / GET_PARAMETER — Set and read individual logging configuration parameters.
  • FLUSH — Force buffered log records to be written to their destinations.
  • SET_QUERY_ENV — Establish the query execution environment associated with a log context.
  • TABLE_CREATE — Create the backing repository objects that hold log records.
  • WRITE_TO_OPLOG / START_OPLOG / COMPLETE_OPLOG — Record operation-level log entries: begin an oplog entry, append to it, and mark it complete.
  • VERSION — Return the package version identifier.
  • TYPE_ operations, TYPE_REJECTED_RECORDS, TYPE_DIMENSION_COMPILE, TYPE_BUILD, TARGET_TABLE — Standardized log-type and target designations used to categorize entries emitted during dimension compilation, cube builds, and rejected-record processing.

Tables Accessed

The package body references the data dictionary views ALL_TABLES and ALL_TAB_COLUMNS, which it uses for metadata introspection — verifying the existence and column structure of its own log repository tables and of target analytical objects before writing. It depends on DBMS_AW, DBMS_AW_LIB, DBMS_LOB, DBMS_OUTPUT, DBMS_ASSERT, DBMS_UTILITY, PLITBLM, and STANDARD. ETRM records no application-schema tables accessed via APPS synonyms, and the object is reported as not referenced by any other database object, confirming its role as a leaf-level utility within the SYS analytical stack rather than a dependency of EBS product code.

Usage Notes

DBMS_CUBE_LOG is not invoked directly from EBS forms, concurrent programs, or standard application APIs. It is called internally by DBMS_AW and DBMS_CUBE when analytical workspace operations and cube builds execute, and it writes diagnostic output that DBAs review when troubleshooting OLAP-related failures in 12.1.1 and 12.2.2 environments. Custom code should not depend on this package, as it is undocumented, SYS-owned, and subject to change across database releases. Administrators investigating analytical workspace or cube errors should use this package's existence only as a diagnostic signal — the appropriate vendor-supported path is Oracle Support or the DBMS_AW / DBMS_CUBE documentation.