Search Results fnd_ts_sizing_p1

Overview

FND_TS_SIZING is a table owned by the APPLSYS schema in Oracle E-Business Suite, residing in the FND (Application Object Library) product family. It is documented and valid in both EBS 12.1.1 and 12.2.2. The table stores sizing estimates for database objects and schemas, providing the underlying data used by Oracle's tablespace sizing and space management utilities. Records describe how much storage a given object requires, including current extent consumption, free space, and projected requirements for a target tablespace.

The ETRM metadata classifies this object heuristically as standalone, with no foreign-key relationships to other tables. In data-vault modeling terms, this suggests treating FND_TS_SIZING as an independent hub-like structure keyed on its natural composite identifiers rather than as a link or satellite attached to a parent entity. Its role is administrative rather than transactional: it is populated by sizing and diagnostic routines rather than by end-user application activity, and is therefore primarily consumed by DBAs and space-management processes.

Key Information Stored

The primary key, FND_TS_SIZING_P1, is a composite of three business-key columns: OWNER, OBJECT_NAME, and OBJECT_TYPE. Together these uniquely identify each sizing estimate entry, distinguishing the schema that owns the object, the object's name, and its type (for example table, index, or partition). There is no separate single-column surrogate key.

The most significant remaining columns capture the measurements and instructions associated with each object:

• NEW_TABLESPACE and OLD_TABLESPACE — the source and destination tablespaces involved in a sizing or relocation estimate.
• PARENT_OBJECT_NAME — the parent object, used to relate partitions or dependent segments to their base object.
• CURRENT_EXTENTS, CURRENT_BYTES, FREE_BYTES, and USED_BYTES — the present allocation and utilisation footprint of the object.
• UNIFORM_EXTENT_SIZE and NUMBER_OF_EXTENTS — extent geometry used to project growth.
• TOTAL_BYTES_REQUIRED — the computed target size for the object.
• SIZING_ERROR_STATUS and ERROR_CODE — outcome of the sizing computation, including any failure diagnostics.
• CLASSIFIED, PARTITIONED, and ALLOCATION_TYPE — classification attributes describing the object's structure and storage behaviour.
• CREATION_DATE — when the sizing record was generated.

Common Use Cases and Queries

The table supports capacity planning, tablespace migration, and storage-reclamation analysis. A typical query lists target objects and their projected requirements:

SELECT owner, object_name, object_type,
       current_bytes, total_bytes_required,
       new_tablespace
FROM   applsys.fnd_ts_sizing
WHERE  sizing_error_status IS NULL
ORDER  BY total_bytes_required DESC;

DBAs use it to identify objects still pending relocation or resizing, and to filter records with errors for remediation. Reports commonly aggregate CURRENT_BYTES and TOTAL_BYTES_REQUIRED by table or schema to forecast growth.

Related Objects

As the metadata records no foreign keys, FND_TS_SIZING is functionally independent. Its relationships are conceptual rather than enforced. The most significant associated objects are DBA_TABLES, DBA_INDEXES, DBA_SEGMENTS, and DBA_TABLESPACES, which supply the physical facts the sizing rows describe, and FND_TABLES and FND_OBJECTS, which catalog application-level object definitions. Join columns follow the natural key: OWNER maps to the schema name, OBJECT_NAME to the segment name, and OBJECT_TYPE identifies the segment type. Because no RI constraints exist, any joins are performed at query time on these column pairs rather than through declared relationships.