X

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

Should EBS Customers Use Database 12.1.0.2 or 12.1.01?

Steven Chan
Senior Director

E-Business Suite customers must ensure that their database remains on a level that is covered by Error Correction Support (ECS) -- i.e. a level where you can get new patches, Critical Patch Updates (CPU), and Patch Set Updates (PSU).  We've covered this in detail here:

The following Note lists Error Correction Support dates for all database patchsets for all database releases:

That Note shows that patching ends for the 12.1.0.1 Database patchset on August 31, 2016.  All EBS customers should upgrade to a later patchset or database release before then.

Even though Database 12.1.0.1 is still under Error Correction Support, we recommend that all EBS customers currently running Database 12c 12.1.0.1 upgrade to the Database 12.1.0.2 patch set.

Why upgrade?

Better end-user experience.  Database 12.1.0.2 contains important updates for security, stability, and performance.  These updates improve the experience of your end-users.

Easier for system administrators.  We have been working closely with many EBS 12.2 customers.  We have found that the Database 12.1.0.2 patch set streamlines upgrades to EBS 12.2 by reducing the number of additional interoperability patches are required.  Fewer patches mean that upgrades take less time, are less-complex, and less risky.

Minimum baseline for future EBS+Database 12c Certifications.  It is very complex to keep multiple EBS codelines compatible with multiple database releases.  All future EBS 12.2 patches will certified against Database 12.1.0.2 rather than Database 12.1.0.1.  This includes updates to the core AD and TXK system administration tools. 

Faster resolution for database issues. You can still request patches for Database 12.1.0.1 until August 31, 2016, but they will not be produced proactively, so there might be a
delay in getting them to you.

Related Articles

Join the discussion

Comments ( 4 )
  • Paul Tuesday, October 20, 2015

    Steven,

    Are there any recommendations with using OPTIMIZER_ADAPTIVE_FEATURES? I had a client with some significant performance issues from this feature with some processes, while other processes ran better.


  • Steven Chan Tuesday, October 20, 2015

    Hi, Paul,

    Unfortunately, there are some potential issues in certain circumstances with this set to true. We are investigating those issues right now.

    In the meantime, we are tracking -- via an internal bug -- the overall requirement to review EBS recommendations for the use of the optimizer_adaptive_features. You can’t see the contents of that bug, unfortunately, but if you mention bug 21825454 to Support, they can abstract its progress for you.

    Regards,

    Steven


  • Ketan Shah Thursday, November 12, 2015

    Steven,

    We had a long project to upgrade to 12.1.0.1 from 11gR1 on EBS 11i. When we started the project 12.1.0.2 was not certified with 11i. After the upgrade, we ran into multiple performance issues. We have been fixing those by doing one of the following:

    1. Run SQL Tuning advisor on the long running queries and accept a better execution plan if it suggests one.

    2. Move execution plan from 11g instance to 12c instance.

    Would you recommend updating optimizer_features_enable back to 11.1.0.6 or set optimizer_adaptive_features to false?

    Ketan Shah


  • Steven Chan Friday, November 13, 2015

    Ketan,

    We recommend leaving the optimizer feature off for the time being. We're working with the database team right now to ensure that that feature is tuned for the high-performance requirements of the E-Business Suite.

    I don't have the right expertise to comment on what you're doing today. I can engage our Performance team on this. Can you provide your Service Requests?

    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.