Oracle OATM

Oracle Applications has become a massive product that performs virtually every possible area of managing a business. When ERP products get huge, standardization becomes important, and the new Oracle Applications Tablespace Model (OATM) has a tablespace migration utility in R12 as well as instructions as noted in MOSC patch number 3942506. OATM does tablespace consolidation with an eye towards maintaining a uniform logical storage layer for the application: Move data files to from UNIX File System files (UFS) to raw devices to allow RAC to read the files. Standardizes tablespaces to allow for uniform file striping via ASM. Consolidates tablespaces from 382 tablespaces down to only 9 standard tablespaces. Creates only one locally managed tablespace for all transaction tables and another LMT for transaction indexes. OATM has these system management tablespaces: undo tablespace - Undo data temp tablespace - Temporary data. Global Temporary tables system tablespace - system tablespace. Holds data dictionary OATM also creates these new application tablespaces: apps_ts_tx_data tablespace – OATM tablespace for transaction tables apps_ts_tx_idx tablespace - OATM tablespace for transaction Indexes apps_ts_seed tablespace - OATM tablespace for FND objects (reference and setup data) plus indexes. apps_ts_interface tablespace - OATM tablespace for Interface and temporary objects (temp data and indexes). apps_ts_summary tablespace – OATM tablespace for “summary management” objects, a.k.a. materialized views. apps_ts_nologging tablespace – This OATM tablespace is reserved for materialized views that are dro[pped and re-created in nologging mode. apps_ts_queues tablespace - This is the OATM tablespace for advanced queuing objects apps_ts_media tablespace - Multimedia objects apps_ts_archive tablespace - Archive purge related objects In sum, OATM is a new unified way of managing the complexity of over 380 tablespaces by moving them into only 9 applications tablespaces, all utilizing identical features.