Oracle Applications Tablespace Model FAQs [ID 269293.

1] Modified 16-JAN-2011 Type FAQ Status PUBLISHED Oracle Applications Tablespace Model (OATM) FAQ Checked for relevance on 16-JAN-2011 Is the new Oracle Applications Tablespace Model (OATM) mandatory ? OATM is currently optional for customers and not mandatory. Customers who wish to migrate to OATM, should run the OATM Migration utility available as a standalone ARU (currently 3381489) and also as part of 11.5.10. What are the consequences of not migrating to the new model? There are no dire consequences of not migration to OATM, but users will lack the maintenance benefits and potential space-savings from OATM. Is migrating to OATM a manual process or does it involve the use of scripts? The OATM migration Utility is a simple, easy-to-use interactive commandline perl-based menu that walks users through the migration process. Is there any OATM documentation/collateral such as white papers or a user guide available on Metalink? Metalink contains the following OATM documents: Oracle Applications Tablespace Model Release 11i - Tablespace Migration Utility white paper Note 248857.1 on OracleMetaLink How many tablespaces are introduced in OATM? ? OATM contains twelve consolidated tablespaces for all products, including temporary tablespace, system tablespace, and undo segments: Tablespace Type Tablespace Name Contents Tables that contain transaction data.

Transaction Tables Transaction Indexes Reference Interface Summary

APPS_TS_TX_DATA APPS_TS_TX_IDX APPS_TS_SEED

Indexes on transaction tables.

Nologging

Reference and set-up data and indexes. APPS_TS_INTERFACE Interface and temporary data and indexes. APPS_TS_SUMMARY Summary management objects, such as materialized views, and other objects that record summary information. APPS_TS_NOLOGGING Materialized views not used for

Tablespace Type

Tablespace Name

Contents

Advanced Queuing/AQ Media

APPS_TS_QUEUES APPS_TS_MEDIA

Archive Undo

APPS_TS_ARCHIVE UNDO

Temp

TEMP

System

SYSTEM

summary management and temporary objects. Advanced Queuing and dependent tables and indexes. Multimedia objects, such as text, video, sound, graphics, and spatial data. Archive-purge-related objects Automatic Undo Management (AUM) tablespace. UNDO segments are identical to ROLLBACK segments when AUM is enabled. Temporary tablespace for global temporary table, sorts, and hash joins. System tablespace.

How are objects classified in OATM?

What object typesare implicitly classified in OATM? OATM classifes the following object types:
Object type Index Organized Tables Global Temporary Tables Advanced Queuing tables Materialized View Materialized View Logs Domain Indexes Indexes Tablespace Type Transaction_tables

The database automatically always creates these objects in the TEMP tablespace.
Advanced Queuing/AQ Summary Transaction_tables Transaction_indexes With the exception of indexes on Tables classified as 'Transaction_Tables', all indexes will share the same tablespace type as the base object (table/mv).

What object types must be explicitly classified? All tables (with the exception of Global temporary Tables, Index organized Tables) require to be explicitly classified. Where are the explicit classifications recorded?

Explicit classifications provided by internal development teams are defined in FND_OBJECT_TABLESPACES. The mapping between actual tablespaces and the tablespace-types in the new Oracle Applications Tablespace Model (OATM) is defined in FND_TABLESPACES. What is the minimum database version required by the Oracle Applications Tablespace Migration utility? The new Oracle Applications Tablespace Model (OATM) Migration utility currently requires a minimum database version of v9.2.0.4. There are performance enhancements available with the 10G jdbc driver -- Is this compatible for use with the new Oracle Applications Tablespace Model (OATM) Migration utility? The 10g jdbc driver can be used with the OATM Migration Utility. This improves the migration of tables with Long for which a Java program is being used. What is the minimum Oracle eBusiness Suite Applications version required by the Oracle Applications Tablespace Migration utility? The OATM Migration Utility is available standalone and as part of release 11.5.10 to aid customers with previous releases of Oracle Applications (11i/10.7), to migrate to the Oracle Applications Tablespace Model (OATM). Does the new OATM Migration Utility migrate 3rd Party schemas? By default, the OATM Migration Utility does not migrate 3rd party or custom schemas, however this can be done by registering the 3rd party schema with Oracle Applications and setting the relevant privilege. How to have certain 3rd Party or custom schemas be considered by the OATM Migration Utility ? Login to Oracle Applications (Forms) using the System Administrator reponsibility ->Security -> ORACLE -> Register -> Register the external schema(s), if they are not already registered. Set Privilege to 'Enabled'. How to have certain schemas not be considered by the OATM Migration Utility ? By default, the OATM Migration Utility does not migrate 3rd party schemas Login to Oracle Applications (Forms) using the System Administrator reponsibility -> Security -> ORACLE -> Register -> Set Privilege to either 'External' or 'Disabled' accordingly. How can OATM be customized? Although Oracle recommends following the native OATM, this model also enables the creation of custom tablespaces and also allows the overriding of tablespace classifications defined by Oracle Applications. Currently there are APIs available to i)

register custom tablespaces & map them to tablespace types in FND_TABLESPACES ii) register new custom classifications & customize existing classifications. We are working on making available in the Migration Utility an option to help register custom tablespaces. Additionally, there will also be another option available to customize explicit tablespace classifications that are recorded in FND_OBJECT_TABLESPACES. Can I run Generation of migration commands (Option 3 in OATM Migration Utility) while Migration is in progress? Generation of migration commands should not be run after the migration process has already started. Please ensure that Migration is not in progress, if you want to generate migration commands. We do not recommend that the table FND_TS_MIG_CMDS be updated manually, especially while Migration/Generation of commands in in progress, as that could cause undesirable effects. When should the old tablespaces be dropped after migrating to OATM? The old tablespaces can be dropped after ensuring that all the objects residing in them have been migrated successfully to OATM. This is not an action performed automatically by the Migration Utility and has to be initiated by the Administrator using the Migration Utility. Alternately, the OATM migration Utility also provides options to reduce the size of the old tablespaces. This option queries the data dictionary for all data files of the previous tablespaces to determine the level at which they can be re-sized, and generates the resize commands in a script resizdb.sql. This script is then executed to resize the data files. Do statistics need to be gathered after migrating using OATM Migration utility? No, based on bug 2849701: Provide preserve stats OPTION AND ITL INVARIANT FOR ALTER TABLE MOVE, has been fixed in 9.2.0.4. The OATM Migration Uitlity sets event 14526 before the migration, thereby preserving statistics after migration.
Make sure to start the queue SYSTEM.TBLMIG_MESSAGEQUE by issuing the following commands before attempting to run migration again -begin dbms_aqadm.start_queue('SYSTEM.TBLMIG_MESSAGEQUE'); end;

Related Products Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library Keywords MODEL

Back to top Rate this document

Article Rating Rate this document Excellent Good Poor Did this document help you? Yes No Just browsing How easy was it to find this document? Very easy Somewhat easy Not easy Cancel Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support. Comments

Provide feedback for this article. Please use 'Contact Us' for other feedba