Quarterly E-Business Suite Upgrade Recommendations: May 2012 Edition

I've previously published advice on the general priorities for applying EBS updates.  But what are your top priorities for major upgrades to EBS and its technology stack components?

Here is a summary of our latest upgrade recommendations for E-Business Suite updates and technology stack components.  These quarterly recommendations are based upon the latest updates to Oracle's product strategies, support deadlines, and newly-certified releases. 

Upgrade Recommendations for May 2012

  1. EBS 11i users should upgrade to 12.1.3, or -- if staying on 11i -- should be on the minimum 11i patching baseline,

  2. EBS 12.0 users should upgrade to 12.1.3, or -- if staying on 12.0 -- should be on the minimum 12.0 patching baseline,

  3. EBS 12.1 users should upgrade to 12.1.3.

  4. Oracle Database 10gR2 and 11gR1 users should upgrade to 11gR2

  5. EBS 12 users of Oracle Single Sign-On 10g users should migrate to Oracle Access Manager 11g

  6. EBS 11i users of  Oracle Single Sign-On 10g users should migrate to Oracle Access Manager 10g

  7. Oracle Internet Directory 10g users should upgrade to Oracle Internet Directory 11g

  8. Oracle Discoverer users should migrate to Oracle Business Intelligence Enterprise Edition (OBIEE), Oracle Business Intelligence Applications (OBIA), or Discoverer 11g

  9. Oracle Portal 10g users should migrate to Oracle WebCenter 11g or upgrade to Portal 11g

  10. All Windows desktop users should migrate from JInitiator and older Java releases to JRE 1.6.0_32 or later 1.6 updates.

  11. All Firefox users should upgrade to Firefox Extended Support Release 10.

Related Articles



We are in the process of upgrading from 11i to 12.1.3.
We are using OATM already where tablespaces are locally managed with a uniform extent size of 128k.

The database has grown over the years and we have now very large table/indexes, we are considering reorganizing at least the tablespace for indexes (APPS_TS_TX_IDX) to use extent management local set to autoallocate, since there is a big difference in size between small and large indexes.

Reorganizing a tablespace is not a small task in EBS. I used OEM (version 11G) to create a script to help with this process. OEM has a section that allows you to change the properties of a tablespace via a script it creates after analyzing the database.

This is what the script basically does:
1) Alter index rebuild/ alter table move to move these objects to a scratch tablespace
2) Drops APPS_TS_TX_IDX and recreates it using autoallocate
3) Moves back indexes/tables.
Yes, there are tables in APPS_TS_TX_IDX; mostly IOT‘s and tables with LOB’s.

The OEM script is quite large (2,345,427 lines) and can be executed from SqlPlus. It is mostly “Execute immediate” statements with “alter’s” in it, wrapped around with PlSql statements.

We tried the script once in test (no errors) and then we ran the upgrade from 11i to 12.1.3 with no issues related to the reorganization.

Can you see anything wrong with this process? Is there a better way?
Another reason for doing this is to recoup the space freed up by advanced compression which we are evaluating for tables plus regular compression on indexes.

Your feedback would be appreciated.


Posted by Peter on July 13, 2012 at 10:48 AM PDT #

Hi, Peter,

I don't have sufficient personal experience in this area to comment. I've asked one of my staff to look into this but her review is still pending. It's important to note that we will not be able to validate your approach empirically, i.e. through actual testing.

Stay tuned.


Posted by Steven Chan on July 24, 2012 at 11:37 AM PDT #


Thank you for your inquiry.

Using Enterprise Manager Grid Control to assist with rebuilding tablespaces is a pratcial approach to performing tablespace reorgnaizations. Once you have converted to a locally managed tablspace with autoallocated extents, there should not be a need to perform reorganizations in the future. This is one of the great things about locally managed tablespaces.

Your plan for performing the reorganization seems sound; however, please note that each environment is different and there is now way for me to determine via this format if additional steps are required. If you continue to have questions about your deployment strategy, you may contact your Oracle Account Manager who connect you with an Oracle consulting specialist.

Good luck!


Posted by Elke Phelps (Oracle Development) on August 01, 2012 at 04:19 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed


« July 2016