Search Results fnd_ts_mig_util




Overview
Explore in AI Chat

Overview

FND_TS_MIG_UTIL is a utility package body owned by the APPS schema in Oracle E-Business Suite. Its name reflects its role in the tablespace migration and object storage management infrastructure provided by the Oracle Applications Technology layer. The package sits at the intersection of database administration metadata and EBS application configuration, providing programmatic support for translating Oracle Applications object definitions into physical database storage decisions. In release 12.1.1 and 12.2.2, this functionality is relevant to the Online Patching and Editioning architecture introduced in 12.2, where tablespace management and default storage parameters must be maintained consistently across the APPLSYS and APPS schemas.

The package is classified as a UTIL API, meaning it is intended for internal invocation by other EBS technology components rather than as a public end-user interface. The ETRM dependency record confirms that FND_TS_MIG_UTIL is referenced by two other database objects, indicating it functions as a shared service within the FND technology stack.

Key Procedures and Functions

The package exposes thirteen documented procedures and functions. Their purposes are as follows:

  • GET_DB_VERSION — Retrieves the current database version, allowing migration logic to branch based on the underlying RDBMS release.
  • UPD_GL_STORAGE_PARAM — Updates General Ledger storage parameters, aligning GL storage definitions with the target tablespace configuration.
  • MIGRATE_TSP_TO_LOCAL — Migrates a tablespace to locally managed extent allocation, a primary administrative objective of the package.
  • GET_TABLESPACE_NAME — Resolves the tablespace name associated with a given application object or schema.
  • GET_TABLESPACE_UES — Returns tablespace usage statistics, supporting capacity and space analysis.
  • CHK_NEW_TABLESPACES — Validates newly created tablespaces against expected naming and configuration rules.
  • CHK_NEW_TABLES — Checks newly created tables for storage attribute compliance.
  • CHK_PRODUCT_DEFAULTS — Verifies that product-level default tablespace settings are consistent.
  • CRT_STORAGE_PREF — Creates storage preferences for a given object or schema.
  • UPD_FOT_USERNAME — Updates the username recorded in FND_OBJECT_TABLESPACES.
  • PROCESS_RULES — Applies migration rules defined in FND_TS_MIG_RULES to drive object relocation.
  • SET_DEFAULTS — Establishes default storage and tablespace values for processing.
  • CRT_TXN_IND_PREF — Creates transaction index preferences as part of storage configuration.

Tables Accessed

The package reads and writes application metadata through APPS synonyms and inspects the data dictionary directly. Core EBS tables include FND_TABLESPACES, FND_OBJECT_TABLESPACES, FND_TS_MIG_RULES, FND_ORACLE_USERID, FND_PRODUCT_GROUPS, FND_PRODUCT_INSTALLATIONS, and GL_STORAGE_PARAMETERS. These supply the product registration, schema-to-user mapping, and migration rule definitions that drive processing. Data dictionary views DBA_TABLESPACES, DBA_TABLES, DBA_USERS, DBA_TS_QUOTAS, DBA_SNAPSHOTS, DBA_SNAPSHOT_LOGS, and DBA_QUEUE_TABLES provide physical storage and object inventory. Oracle Text objects CTX_DDL and CTX_USER_PREFERENCES are referenced for context index preference management. DBMS_SPACE_ADMIN is invoked for tablespace administration operations.

Usage Notes

FND_TS_MIG_UTIL is a server-side utility invoked by other EBS technology packages rather than directly by end users. It is typically driven by concurrent programs and administrative scripts supporting tablespace migration initiatives, particularly the transition from dictionary-managed to locally managed tablespaces and the establishment of consistent product default storage. Because it is a package body with no direct form bindings, customizations should call it only through supported wrapper interfaces. Direct invocation in a patched 12.2 environment should account for editioning and the AD/TXK utilities, and any modification to APPS-owned code is unsupported and lost on application of patches.