X

The Latest Oracle E-Business Suite Technology News direct from
Oracle E-Business Suite Development & Product Management

Last Stop For Oracle Applications Tablespace Migration

Steven Chan
Senior Director

The Oracle Applications Tablespace Model (OATM) -- sometimes also called the Oracle E-Business Suite Tablespace Model) -- organizes the EBS database by object type rather than by products.  Prior to OATM, the EBS database had two tablespaces for each product, resulting in hundreds of tablespaces.  OATM contains only twelve locally-managed tablespaces.  This simplifies management and requires fewer operating system files.

Whether you're already using the Oracle Applications Tablespace Model depends on which version of the E-Business Suite you initially installed. If you started on an older EBS release, you have the option of migrating to the Oracle Applications Tablespace Model.

Is OATM mandatory?

No, it's optional, but we recommend that you use OATM.  It's more-efficient and easier to manage.  You can use the OATM Tablespace Migration Utility to migrate to the new model.

Can I use OATM with EBS 12.2?

The OATM Tablespace Migration Utility cannot be used after you enable Online Patching in EBS 12.2.  If you wish to migrate to OATM, you must do so before you enable Online Patching.

If you do not migrate to OATM, you must continue to manage your tablespaces separately after enabling Online Patching.

References

 

 

Join the discussion

Comments ( 2 )
  • guest Tuesday, December 9, 2014

    Hi Steven,

    Hope you are doing good and wish you Happy Holidays.

    I believe OATM using locally managed uniform extent sizes while creating tablespaces. How is this more efficient over system managed extents and what type of EBS system favor system and uniform extents .

    Current Scenario:

    During upgrade from R11.5.10.2 to R12.2 we are observing H/W(High WaterMark ) wait events for upgrade driver and one of fix suggested was to move to large extents which can reduce this wait event and it did actually even though there are other waits that occurred newly , What is impact in long term and which one benefits more in long run.

    Thanks,

    Vamshi .D


  • Steven Chan Tuesday, December 9, 2014

    Hi, Vamshi,

    OATM places objects into tablespaces by their storage and access properties rather than product affiliation. Properties of the tablespace and underlying storage can then be tuned to best serve the types of objects stored in that tablespace.

    I'm sorry that you're encountering issues with your EBS 12.2 upgrade. Can you provide your Service Request number for this? I'd like to have one of our performance engineers look into it for you.

    Regards,

    Steven


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.