Search Results create_object_tablespaces




Overview
Explore in AI Chat

Overview

FND_OBJECT_TABLESPACES_PUB is a public PL/SQL package body in the APPS schema that supports Oracle E-Business Suite's Tablespace Management feature. Its business function is to manage the association between registered EBS objects—applications, Oracle users (schemas), and product installations—and the database tablespaces in which their underlying segments reside. This information is persisted in the FND_OBJECT_TABLESPACES table and drives the Oracle Applications Tablespace Migration utilities, which relocate objects between tablespaces during capacity planning, storage consolidation, or platform migration efforts.

The package exposes a deliberately narrow public interface of three procedures while delegating the substantive work to the private package FND_OBJECT_TABLESPACES_PKG. This separation keeps the public contract stable across releases while permitting internal implementation changes. The package is classified VALID in the ETRM metadata and conforms to the standard EBS API conventions established by FND_API, including message-stack handling through FND_MSG_PUB and FND_MESSAGE.

Key Procedures and Functions

  • CREATE_OBJECT_TABLESPACES — Registers new mappings between EBS objects and tablespaces. It inserts the corresponding rows into FND_OBJECT_TABLESPACES, validating inputs against FND_APPLICATION, FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS, and FND_TABLESPACES before the canonical values are stored.
  • UPDATE_OBJECT_TABLESPACES — Modifies existing object-to-tablespace associations, for example when an object has been migrated to a new tablespace or when the recorded association must be corrected. It operates on rows already present in FND_OBJECT_TABLESPACES.
  • VALIDATE_OBJECT_TABLESPACES — Verifies that the object-to-tablespace assignments recorded in the repository are internally consistent and that the referenced tablespaces exist and are usable. This is the diagnostic entry point used before or after a migration activity.

No parameter lists are documented in the ETRM metadata; callers should consult the package specification for the authoritative signatures.

Tables Accessed

The package references a mixture of EBS repository tables and data dictionary views.

  • FND_OBJECT_TABLESPACES — the primary repository of object-to-tablespace mappings maintained by this package, supported by the private package FND_OBJECT_TABLESPACES_PKG.
  • FND_APPLICATION, FND_ORACLE_USERID, FND_PRODUCT_INSTALLATIONS, and FND_TABLESPACES — used to resolve and validate the application, schema, installation, and tablespace identifiers that participate in the mapping.
  • DBA_TABLES, ALL_QUEUE_TABLES, ALL_SNAPSHOTS, and ALL_SNAPSHOT_LOGS — data dictionary views queried to determine the actual physical placement of table, advanced queue, materialized view, and materialized view log segments. The ALL_SNAPSHOTS and ALL_SNAPSHOT_LOGS views are legacy synonyms for ALL_MVIEWS and ALL_MVIEW_LOGS respectively, and remain referenced here for backward compatibility.
  • AS_UTILITY_PVT — utilities from the Applications DBA (AD) product used for low-level segment and storage operations.

Usage Notes

FND_OBJECT_TABLESPACES_PUB is not referenced by any other database object, so invocation is external. It is normally called from Oracle Application Manager and the Tablespace Management web pages (OAM/AD utilities), from the concurrent programs associated with the Tablespace Migration feature, and from DBA-driven maintenance scripts that register or reconcile object placements. Custom code should invoke these procedures only through the public package rather than touching FND_OBJECT_TABLESPACES directly. Callers must initialize the FND message stack (via FND_GLOBAL and FND_MSG_PUB) before invocation and inspect the returned API status afterward, following the standard FND_API error-handling pattern.