Search Results gen_ind_sizing




Overview
Explore in AI Chat

Overview

FND_TS_SIZE is an Oracle E-Business Suite database package owned by the APPS schema that supports tablespace sizing analysis within the Applications DBA (AD) and System Administration infrastructure. Its business function is to compute and record storage-sizing recommendations for database objects—tables, indexes, LOB segments, and related structures—based on the physical characteristics of the existing database and user-defined sizing parameters. The package writes its output into the FND_TS_SIZING table, which acts as the repository of sizing recommendations consumed by Oracle's tablespace management and capacity planning utilities.

The package is classified as OTHER in the ETRM 12.2.2 metadata, indicating it is not a formal public API but rather an internal utility invoked by Oracle's own concurrent programs and administrative routines. The header comment survives from an early Applications release (120.1, dated 2005), underscoring that the interface has remained stable across 12.1.1 and 12.2.2.

Key Procedures and Functions

Four procedures are documented, organized along two axes: object type (table versus index) and scope (single application versus all applications).

  • GEN_TAB_SIZING — Generates sizing recommendations for tables belonging to a single specified application, honoring the caller-supplied uniform extent size, allocation type, and creation date.
  • GEN_IND_SIZING — Performs the equivalent sizing analysis for indexes of a single application.
  • GEN_ALL_TAB_SIZING — Extends table sizing across all registered applications in the instance, taking the uniform extent size, allocation type, and creation date as inputs.
  • GEN_ALL_IND_SIZING — Extends index sizing across all applications.

The uniform-extent parameter allows the caller to model storage under a locally managed, uniform-allocation tablespace policy, while the creation-date parameter restricts the population of segments considered. All four procedures are declared AUTHID CURRENT_USER, meaning they execute with the privileges of the invoking session rather than the definer—an important characteristic for a utility that queries DBA_ views.

Tables Accessed

The package reads extensively from the data dictionary through APPS synonyms, including DBA_TABLES, DBA_INDEXES, DBA_SEGMENTS, DBA_TAB_PARTITIONS, DBA_IND_PARTITIONS, DBA_LOBS, DBA_LOB_PARTITIONS, DBA_QUEUE_TABLES, DBA_EXTERNAL_TABLES, DBA_SNAPSHOTS, and DBA_SNAPSHOT_LOGS. These views supply the current physical attributes—segment sizes, partition structure, and object existence—that drive the sizing calculation.

Application-layer metadata is drawn from FND_TABLESPACES, FND_OBJECT_TABLESPACES, and FND_ORACLE_USERID, which define the valid tablespaces and Oracle schema owners registered in the instance. The computed results are persisted to FND_TS_SIZING, the target table for all four procedures.

Usage Notes

FND_TS_SIZE is an internal engine rather than a directly callable public API. ETRM records zero packages referencing it, confirming that Oracle invokes it from its own administrative code—typically concurrent programs associated with the AD Tablespace Management and "Monitor Tablespace Sizing" functionality in 12.1.1 and 12.2.2. It is not exposed through any standard Oracle Forms interface.

Because all four procedures require SELECT privileges on DBA_ views, callers must connect as a user with the APPS schema's dictionary access, normally via the Applications DBA responsibility. Custom code should treat the package as unsupported and avoid direct invocation; customers requiring tablespace sizing data should query FND_TS_SIZING after Oracle's own concurrent programs have populated it.