Search Results gl_storage_parameters




Overview
Explore in AI Chat

Overview

GL_STORAGE_PARAMETERS is a General Ledger configuration table owned by the GL schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description identifies it as holding "interim table storage parameters," meaning it stores the physical storage attributes assigned to interim GL objects such as interface, consolidation, and journal import staging tables. These parameters govern how Oracle allocates extents for interim tables during high-volume journal processing and period-end close activities, making the table a control point for database-level performance tuning rather than a repository of transactional accounting data.

The ETRM metadata classifies the object heuristically as standalone within a Data Vault modeling scheme. This suggests it functions most naturally as a reference or configuration hub, since it carries no documented foreign key relationships to other GL entities and is referenced purely by its own business key. Modeling it as an independent reference table rather than a link or satellite reflects its self-contained nature.

Key Information Stored

The table's documented physical schema contains fifteen columns. The most significant include:

  • OBJECT_NAME — the business identifier naming the interim database object whose storage is being defined. This column anchors the primary key.
  • OBJECT_TYPE — the category of the governed object, distinguishing interim table types.
  • TABLESPACE_NAME — the tablespace into which the interim object's segments are placed, a primary lever for I/O distribution.
  • INITIAL_EXTENT_SIZE_KB and NEXT_EXTENT_SIZE_KB — the initial and subsequent extent allocation sizes, which determine how quickly large interim loads consume space.
  • MAX_EXTENTS, PCT_INCREASE, and PCT_FREE — classic storage-clause controls limiting growth, governing extent growth percentage, and reserving block space respectively.
  • DESCRIPTION — free-text annotation for the parameter set.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — the standard EBS "WHO" audit columns.
  • ZD_EDITION_NAME — the editioning column supporting Oracle EBS 12.2 online patching, enabling edition-specific rows.

The surrogate or composite primary key is GL_STORAGE_PARAMETERS_PK, defined on OBJECT_NAME. A unique index, GL_STORAGE_PARAMETERS_U1, is documented on the combination of OBJECT_NAME and ZD_EDITION_NAME, making that pair the effective business-key candidate under the 12.2 editioning model.

Common Use Cases and Queries

DBAs and GL administrators consult this table when troubleshooting interim table performance, reallocating tablespaces, or reviewing extent sizing before period-end processing. A typical diagnostic query lists parameter sets by object and tablespace:

  • SELECT object_name, object_type, tablespace_name, initial_extent_size_kb, next_extent_size_kb FROM gl_storage_parameters WHERE object_type = :type;
  • Filtering by tablespace to assess consolidation of interim segments: SELECT object_name, description FROM gl_storage_parameters WHERE tablespace_name = :ts;
  • Auditing recent changes: SELECT object_name, last_updated_by, last_update_date FROM gl_storage_parameters ORDER BY last_update_date DESC;

Reporting use cases include capacity planning for large journal import runs, verifying that interim tables are not sized with excessive MAX_EXTENTS, and confirming edition-specific rows after an online patching cycle.

Related Objects

The metadata documents this object as standalone, with no foreign keys to or from other tables. Consequently, relationships are functional rather than referential and should be understood through shared GL interim processing rather than enforced constraints:

Because the documented schema exposes only a self-referencing primary key and a unique business-key index, joins to these objects are conventionally performed on name or context columns rather than on declared foreign keys.