Results for “min_extents”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_INDEXES is an Application Object Library (FND) repository table in the APPLSYS schema that records the unique and non-unique database indexes registered with Oracle Application Object Library. In Oracle EBS 12.1.1 and 12.2.2, it serves as the metadata catalog describing how physical indexes are defined against the tables registered in FND_TABLES, which is the companion table that registers the EBS database tables themselves. Together, FND_TABLES, FND_INDEXES, and FND_INDEX_COLUMNS form the AOL schema definition layer used by the Oracle EBS installation and patching utilities.

From a data vault modeling perspective, the ETRM metadata heuristically classifies FND_INDEXES as satellite-leaning. This is a modeling suggestion rather than a definitive classification: the table functions as descriptive metadata that qualifies an index entity. Its primary key depends on APPLICATION_ID and TABLE_ID, indicating it is keyed partly by its parent table's identity rather than being a standalone hub.

Key Information Stored

The table contains 21 documented columns. The most operationally significant are:

• APPLICATION_ID — identifies the EBS application to which the registered index belongs.
• TABLE_ID — the surrogate identifier of the parent table registered in FND_TABLES.
• INDEX_ID — the surrogate identifier for the index record itself.
• INDEX_NAME — the physical database index name as it appears in the data dictionary.
• UNIQUENESS — indicates whether the index is unique or non-unique.
• DESCRIPTION — free-text commentary describing the index purpose.
• AUTO_SIZE, INI_TRANS, MAX_TRANS — Oracle storage and transaction-entry parameters.
• INITIAL_EXTENT, NEXT_EXTENT, MIN_EXTENTS, MAX_EXTENTS, PCT_FREE, PCT_INCREASE — extent and space-management attributes for the index segment.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard AOL audit columns.
• ZD_EDITION_NAME — the editioning qualifier relevant in the 12.2.2 Edition-Based Redefinition (EBR) model.

The surrogate primary key is FND_INDEXES_PK (APPLICATION_ID, TABLE_ID, INDEX_ID). Two unique business-key candidates are documented as FND_INDEXES_U1 (APPLICATION_ID, TABLE_ID, INDEX_ID, ZD_EDITION_NAME) and FND_INDEXES_U2 (INDEX_NAME, APPLICATION_ID, TABLE_ID, ZD_EDITION_NAME), which guarantee uniqueness of the index name within a table and edition.

Common Use Cases and Queries

A primary use case is auditing the indexes registered against a given EBS table, which supports performance tuning and schema validation during upgrades or patch application.

• List indexes for a table: SELECT INDEX_ID, INDEX_NAME, UNIQUENESS, DESCRIPTION FROM APPLSYS.FND_INDEXES WHERE APPLICATION_ID = :app_id AND TABLE_ID = :table_id ORDER BY INDEX_ID;
• Find unique indexes: SELECT INDEX_NAME, TABLE_ID FROM APPLSYS.FND_INDEXES WHERE UNIQUENESS = 'UNIQUE';
• Join to parent table names: SELECT i.INDEX_NAME, t.TABLE_NAME FROM APPLSYS.FND_INDEXES i, APPLSYS.FND_TABLES t WHERE i.APPLICATION_ID = t.APPLICATION_ID AND i.TABLE_ID = t.TABLE_ID;
• Reconcile with the data dictionary: compare FND_INDEXES rows against DBA_INDEXES to detect drift between registered and physically present indexes.

These queries are commonly used before and after upgrades, during ADLDT and schema migration work, and when diagnosing missing or duplicate index registrations.

Related Objects

The most significant related objects, derived from the documented foreign key relationships, include:

• FND_TABLES — parent table referenced via FND_INDEXES.APPLICATION_ID and FND_INDEXES.TABLE_ID; supplies the table metadata that each index qualifies.
• FND_INDEX_COLUMNS — child table that references FND_INDEXES via APPLICATION_ID, TABLE_ID, and INDEX_ID; holds the ordered columns comprising each index.

Together with the AOL schema utilities and installation drivers that populate them, these objects constitute the registration model used by AD Utils and related Oracle EBS maintenance processes to keep database metadata synchronized with the application definition.