Wednesday Jul 03, 2013

Microsoft Ending Support for Windows XP and Office 2003 in April 2014

Microsoft LogoMicrosoft is ending support for Windows XP and Office 2003 on April 8, 2014.  The official announcement is published here:

These products are certified for desktop clients accessing the E-Business Suite today.  Our general policy is that we support certified third-party products as long as the third-party vendor supports them.  When the third-party vendor retires a product, we consider that to be an historical certification for EBS.

What can EBS customers expect after April 2014?

After Microsoft desupports WinXP and Office 2003 in April 2014:

  • Oracle Support will continue to assist, where possible, in investigating issues that involve Windows XP clients or Office 2003.
  • Oracle's ability to assist may be limited due to limited access to PCs running WinXP or Office 2003.
  • Oracle will continue to provide access to existing EBS patches for WinXP or Office 2003 issues.
  • Oracle will provide new EBS patches only for issues that can be reproduced on later operating system configurations that Microsoft is actively supporting (e.g. Windows 7, Office 2010)

What should EBS customers do?

Oracle strongly recommends that E-Business Suite customers upgrade their desktops from Windows XP and Office 2003 to the latest certified equivalents.  As of today, those are Windows 7 and Office 2010. 

Certifications for Windows 8 and Office 2013 are still underway; you can monitor this blog for updates on those pending certifications.  EBS customers should avoid deploying Win8 or Office 2013 to end-users who depend on the E-Business Suite until these certifications are announced.

Related Articles

Friday Feb 01, 2013

Grace Period Increased for Applying (some) Database Patchsets

It's crucial to maintain the database in your E-Business Suite environments by applying the latest database patchsets.  Database patchsets contain important security, performance, and stability updates. As of today, the latest database patchset certified with EBS is 11.2.0.3. We strongly recommend that all EBS customers should be running this patchset now.

Oracle Database release roadmap

Until now, whenever a new database patchset was released, you had up to 12 months to apply it.  This is called the grace period.  No new patches for the previous patchset would be released after that 12 month grace period.

Oracle's Server Technologies group has just increased the grace period for the second and later patchsets to two years.

This is easier to understand with an example:

  • 11.2.0.1 was the major release for the 11gR2 codeline.
  • 11.2.0.2 was the first patchset.  You had 12 months to apply that patchset once it was released.
  • 11.2.0.3 was the second patchset.  You now have 24 months to apply that patchset after its release.

For more information about these database support policies, see:

Related Articles

Friday Dec 30, 2011

Limited Extended Support Available for Oracle Single Sign-On through 2012

Premier Support for Oracle Single Sign-On 10gR3 ends on December 31, 2011.  This was originally slated to be the end of error correction support for Oracle Single Sign-On 10gR3. 

Our Oracle Identity Management team has just revised that policy.  If you have an existing support contract, you will now be able to receive limited Extended Support for Oracle Single Sign-On from January 2012 through December 2012.  Only Severity 1 fixes for Oracle Single Sign-On will be released during the limited Extended Support period.  Critical Patch Updates (CPUs) for Oracle Single Sign-On will not be released during the limited Extended Support period. 

These changes are published in:

This is good news for those of you that have not been able to migrate to a single sign-on solution utilizing Oracle Access Manager and Oracle E-Business Suite Access Gate.  Keep in mind though, the clock is ticking and limited extended support will end in a mere 12 months.  It is strongly recommended that you use this additional time to integrate your single sign-on deployment with Oracle Access Manager and Oracle E-Business Suite Access Gate.  


Our recommendations

EBS 12 customers should move to a single sign-on solution using Oracle Access Manager 11g

EBS 11i customers first upgrade to EBS Release 12.1.3, then integrate with Oracle Access Manager 11g.  If an R12 upgrade is not possible, then R11i customers are encouraged to migrate their single sign-on solution to Oracle Access Manager 10gR3

EBS customers looking to deploy a single sign-on solution for the first time are strongly encouraged to deploy a solution using Oracle Access Manager 11g.

References

Related Articles

Friday Oct 28, 2011

Premier Support ends December 2011 for Discoverer 10g, Portal 10g, Single Sign-On 10g, and others

All Oracle E-Business Suite system administrators should check the Lifetime Support dates for their technology stack components regularly.  If you need a primer on how support policies for Fusion Middleware and Server Technologies components interact with E-Business Suite support dates, see:

Table showing Fusion Middleware support timelines

December 2011 is a critical threshold for several products used by Oracle E-Business Suite customers.  Premier Support ends on December 31st, 2011 for:

  1. Discoverer 10g
  2. Portal 10g
  3. Oracle Internet Directory 10g
  4. Single Sign-On 10g
  5. BPEL 10g
  6. Business Activity Monitoring 10g
  7. Business Intelligence Enterprise Edition 10.1.3.x
  8. WebCenter Suite 10.1.3.x
  9. Oracle Identity Manager 9.0.x

Extended Support is not available for many these products -- check the Lifetime Support Policy for Oracle Fusion Middleware (PDF) for details.  All customers using these products should upgrade to the 11g equivalents as soon as possible.

E-Business Suite 11i users running Oracle Single Sign-On 10g users should upgrade to Oracle Access Manager 10g.  Oracle E-Business Suite Release 12 users running Oracle Single Sign-On should upgrade to Oracle Access Manager 11g.

Related Articles


Friday Jul 22, 2011

Reminder: Database 11.1.0.7 Premier Support ends August 2012

It's deja vu all over again.  Since I covered the Error Correction Support (ECS) dates for the 11gR2 Database a few days ago, it's also worth reminding you of an important support milestone for the 11gR2 Database codeline.

Premier Support for Oracle Database 11gR1 (11.1) ends on August 31, 2012.  Extended Support for 11.1 continues to the end of August 2015. These support timelines are covered in the Lifetime Support Policy for Oracle Technology Products.

The 11.1.0.7 patchset is the terminal patchset for the 11gR1 database codeline.  If you're still on the 11.1.0.6 patchset, you should note that Error Correction Support for that ended on September 18, 2009, as detailed here:

If you're not already on 11.2.0.2, we recommend that all Apps customers make plans for a database upgrade soon.

No support exceptions for EBS users

Remember that all Oracle Database support timelines apply to E-Business Suite environments.  There are no special support exemptions for EBS environments.  For an in-depth discussion about how database support timelines affect EBS customers, see:

Related Articles

Tuesday Jul 19, 2011

Reminder: Database 11.2.0.1 Error Correction Support ends Sept. 2011

The Server Technologies division supports the previous release for 12 months after the release of the latest patchset.  The 11.2.0.2 Database patchset was released in Sept 2010.  This means that 11gR2 Database patches produced after September 13, 2011 will require the 11.2.0.2 patchset as a prerequisite.  For more details about patching timelines for individual database patchsets, see:
If you're not already on 11.2.0.2, we recommend that all Apps customers make plans for a database upgrade soon.

No support exceptions for EBS users

Remember that all Oracle Database support timelines apply to E-Business Suite environments.  There are no special support exemptions for EBS environments.  For an in-depth discussion about how database support timelines affect EBS customers, see:
Related Articles

Thursday Feb 24, 2011

New Oracle E-Business Suite R12 OS and Tools Requirements on IBM AIX on Power Systems

logo_ibm.jpgIBM has announced May 1st, 2011 as the end of Support for Version 8 of the IBM XL C/C++ compiler currently used for Release 12 builds and patching. The target date of the switchover -- May 1st 2011 -- corresponds to when this older compiler will no longer be supported by IBM.

Beginning on May 1st 2011, Oracle E-Business Suite patches for Release 12 (12.0, 12.1) on the IBM AIX on Power Systems platform will be built with Version 9 of the IBM XL C/C++ compiler. 

Customers who plan to patch or upgrade their E-Business Suite R12 environments after May 1st, 2011 must meet all the new requirements prior to applying new patches or upgrades.

Please review the documents below for all new requirements pertaining to the new runtime and utilities packages on IBM AIX on Power Systems.

Where can I find more information?
Related Articles

Thursday Jan 20, 2011

Reminder: Error Correction Support for DB 10gR2 10.2.0.4 Ends April 30, 2011

Experienced Apps DBAs know that they need to monitor database support windows for their E-Business Suite environments.  For an in-depth discussion about how database support policies affect E-Business Suite users, see:
An important deadline is approaching if you're still running any E-Business Suite release on the 10gR2 10.2.0.4 database.  New 10gR2 patches produced after April 30, 2011 will require 10.2.0.5.  No new patches will be produced for 10.2.0.4 after that date. 

This is covered, along with other useful topics, in the following 10gR2 Support FAQ from my colleagues in the Server Technologies division:

Another important point from that FAQ:
8. Will I get more time to install 10.2.0.5 if it is released on my platform close to April 30, 2011?

Yes.  We will always support the previous patch set for at least 3 months, even if it is released after the one year to install the new patch set is up.  For example, patching for 10.2.0.4 generally expires on April 30, 2011.  If you are running 10.2.0.4 on the Commodore 64 platform and Oracle releases it after April 30, 2011, we will still patch 10.2.0.4 for you for 3 months following the 10.2.0.5 release on your platform.
Advice for EBS sysadmins

If you're still running your EBS environment on the 10.2.0.4 database, here are your options (in order of greatest bang-for-your-upgrade-buck):
  1. Upgrade to 11.2.0.2.  It's the latest 11gR2 database version certified with the E-Business Suite. Upgrading to this level will buy you the longest period before you're forced to do another database upgrade.
  2. Upgrade to 11.1.0.7.  It's the latest 11gR1 database version certified with the E-Business Suite.  Looking at this pragmatically, though, I don't see much value in upgrading to 11gR1.  If you're going to go to the trouble of upgrading from 10gR2 10.2.0.4 to a newer major database release, you might as well do it right and upgrade to 11.2.0.2.
  3. Upgrade to 10.2.0.5.  If you're planning on staying on 10gR2 for a while, you should be on a release for which you can get new patches and security fixes.
Related Articles

Wednesday Nov 03, 2010

OAUG Surveying Your Readiness for EBS 11i Extended Support

oaug_logo.png
Premier Support Oracle E-Business Suite Release 11i ends on November 30, 2010.  Extended Support begins on December 1, 2010.  EBS 11i environments must have a certain minimum level of patches to be eligible for Extended Support.

The Oracle Applications User Group (OAUG) has been working with us to get the word out to our E-Business Suite community for some time now, highlighting this via conferences, workshops, blogs, newsletters, and the like.

As part of their efforts to represent the E-Business Suite community, they have posted a survey that's intended to get a snapshot of your readiness for this cutover from Premier Support to Extended Support.  The survey closes on November 30, 2010.  If you're interested in sharing your status with them, the OAUG survey is posted here:
This independent survey is being conducted by the Oracle Applications User Group, not Oracle.  Please contact a member of the OAUG Board of Directors directly if you have any questions about this survey.

Related Articles

Tuesday Aug 10, 2010

Reminder: Use Java 6 for EBS on Sun, Windows, Linux Platforms

Several threads have crossed my inbox lately about Java 5 (a.k.a. JDK 1.5).  If you're running your E-Business Suite servers on on Linux, Windows, or Sun operating system platforms, you should be reminded that the End of Service Life for Java 5.0 was on October 30, 2009. 

SunJavaSEdownloadpagescreen2.jpg
That End of Service Life (EOSL) date for Java 5 applies to Java Standard Edition (Java SE) release families.  You have the option of migrating to Java Standard Edition for Business, which offers longer End of Service Life windows for different Java releases -- for example, up to June 2019 for Java 5.  I am not a Java licencing specialist, but my understanding is that Java Standard Edition for Business comes at an additional cost. For information about Java licencing, I would recommend contacting your Oracle account manager. 

For more details about the support-related differences between Java SE and Java for Business, see:
Does this affect your environments?

If all of the following apply to your environment:
  1. Your servers are running on Linux, Sun, or Windows operating systems
  2. Your servers are running either Java Standard Edition 4 (1.4) or 5 (1.5)
Then you must do one of the following:
  1. Migrate to the Java Standard Edition for Business release of your choice
  2. Upgrade to Java Standard Edition 6 (1.6)
For details about upgrading E-Business Suite environments to Java 6, see:
What about other server operating systems?

If you're running either HP-UX or IBM AIX, your Java release on those operating system platforms is supported by Hewlett-Packard and IBM, respectively.  You should check with those vendors for their End of Service Life dates for Java.

What are the support implications if I don't upgrade?

Here's a hypothetical situation: let's say that you haven't migrated to Java SE for Business or upgraded to Java SE 6.  You report an E-Business Suite issue that turns out to be related to either Java 1.5 or 1.5.  What are the support implications?

EBS Support will attempt to reproduce the issue on an Oracle Support environment.  Chances are high that that environment will already be upgraded to Java 6. 

If the issue cannot be reproduced on an environment running Java 6, it is likely that Oracle Support will recommend that you upgrade your environment to Java 6 before proceeding with further diagnostics or analysis.

Generally speaking, EBS Development will provide Java-related patches for Sun, Linux, and Windows-based issues that can be reproduced on Java 6.

Related Articles

Tuesday May 25, 2010

Reminder: Premier Support for EBS 11i ends November 2010

Apps sysadmins are going to have a busy year.  If you're still running your E-Business Suite environment on the 10gR2 database, I hope that you're aware that Premier Support for 10.2 ends in July 2010.  But if you're still on Oracle E-Business Suite Release 11i version 11.5.10, the impending end of Premier Support this year on November 30, 2010 is even more important. 

Support windows for Oracle E-Business Suite are listed here:
Premier Support runs for five years from a product's first release.  In the case of Oracle E-Business Suite Release 11.5.10, that window was increased to six years in recognition of the challenges that some of you face in justifying major upgrades in today's economy.

Here's a graphical summary of the EBS 11.5.10's support stages:

Graphical summary of E-Business Suite 11i support stages Premier Extended Sustaining
First year of Extended Support fees for EBS 11.5.10 waived

Regular readers may recall that fees for the first year of Extended Support for EBS 11.5.10 are waived.  There is nothing that customers need to do to remain fully supported other than keep your support contracts current.  Higher fees for Extended Support will start December 1, 2011 for most platforms.  This is formally documented here:
What are the differences between Premier, Extended, and Sustaining Support?

The differences between Premier and Extended Support coverage are summarized here (see the Lifetime Support Policy document for the product of your choice for a more detailed discussion of these coverages):


This table shows that when a product goes into Extended Support, Oracle no longer has the obligation to certify it with "most new third-party products/versions." 

From an E-Business Suite perspective, third-party products include:

  • Microsoft Windows operating systems for end-user desktops
  • Mac OS X operating systems for end-user desktops
  • Internet Explorer, Firefox, Safari browsers for end-user desktops
  • Microsoft Office releases for end-user desktops
  • Server-based operating systems for application-tier and database-tier servers, including Microsoft Windows Server, IBM AIX, HP-UX, RedHat Linux, Novell SUSE, and others
What are the Extended Support implications for third-party certifications?

An illustrative example may be useful:  As a strictly fictitious example, let's consider a case where Microsoft releases a new version of Internet Explorer in, say, February 2011.  I need to emphasize that this is strictly a hypothetical example; I am not privy to IE release dates and would not be permitted to speculate about them here.

Extended Support for Oracle E-Business Suite Release 11i began on December 1, 2010.  Therefore, Oracle has no formal obligation to certify Oracle E-Business Suite Release 11i with this February 2011 version of IE.  For the sake of this hypothetical example, let's assume that we have not made any plans for certifying this new IE version with Apps 11i.

Taking this example one step further, let's assume that you choose to deploy this latest IE version to your end-user desktops, disregarding the risk that it hasn't been formally certified with Apps 11i.  Your early tests look promising, so you roll it out.

You then encounter a critical issue with EBS, that new IE release and, say, the latest JRE release.  If you report that issue, we will (in all likelihood) attempt to investigate and resolve the issue.  However, if it turns out that the fix would require broad or deep changes to EBS 11i, Oracle has the option of suggesting that you roll back to a previously-certified browser such as IE 8.

Let me stress that this is an hypothetical example only, one designed to illustrate the possible risks associated with Extended Support.  We haven't made any concrete plans for certifying -- or not certifying -- EBS 11i with new browser versions yet.  But this example serves to underline that Oracle has no formal obligations to release new third-party certifications once EBS 11i moves into Extended Support status.

What should EBS 11i users do?

We now have three major EBS codelines:  Release 11.5.10, Release 12.0, and Release 12.1.  Here's a graphical summary of the support windows for these three releases (drawn from the Lifetime Support Policy above):

Graphical 
summary of Premier and Extended support stages for E-Business Suite 
release 11i 12-0 and 12-1
Remember that the Extended Support window is intended to give you some breathing room to upgrade to the next release covered by Premier Support.  So, you should consider your entire E-Business Suite 11.5.10 environment to be frozen after December 1, 2010, the start of Extended Support. 

Planning for the worst-case scenario where we don't release any new third-party certifications for Apps 11.5.10 at all, "frozen" means that you shouldn't expect to be able to upgrade anything on your EBS 11.5.10 desktop clients, application tier servers, or database tier servers. 

There's no justifiable business case for EBS 11i users to upgrade to EBS 12.0 at this point.  All E-Business Suite 11.5.10 users should plan on upgrading to the EBS 12.1 codeline. 

What about the minimum baseline for EBS 11.5.10 Extended Support?

A new set of minimum technical requirements for Apps 11i goes into effect when Extended Support begins in November 2010.  These new minimum baseline patch requirements are listed here:
As always, Oracle Support will assist with diagnosis, triage, and debugging of any issues that you report for your E-Business Suite environment.  You will continue to have access to any existing online support tools, knowledge base documentation, and pre-existing fixes.

If you report a new issue that requires a new bug fix, you should be aware that new patches will be released only for the new baseline patches listed in the Minimum Baseline Patch Requirements Note.  You should plan to apply the baseline patches (at minimum) listed in Note 883202.1 by November 2010 in order to receive any new bug fixes.

For a more detailed discussion about the new 11.5.10 patching baseline, see this article
Spotlight on Oracle E-Business Suite Release 12 upgrades at OpenWorld 2010

This is the year when upgrade fever begins to glow red-hot.  OAUG/Collaborate 2010 sessions last month that covered EBS 12 upgrades were filled to ballroom capacities.  Naturally, Oracle E-Business Suite Release 12 upgrades will be heavily covered at OpenWorld 2010 this year, too.  I expect that this year's conference will have a large number of customer case studies about R12 upgrades and reimplementations, R12 upgrade panels, and lots of sessions with practical tips for upgrading.

One more critical resource:  R12 Upgrade Forum


There are many resources to support your upgrade to R12 (see the Related Articles section below), but don't forget that we have an Oracle-sponsored R12 upgrade forum on the Oracle Technology Network:
This forum has thousands of practical tips and advice from Apps DBAs who have gone before you in implementing Oracle E-Business Suite Release 12. 

The discussions in this forum run around the clock, notably led by Hussein Sawwan, one of the EBS community's most-prolific Oracle ACEs.  Apparently, Hussein never sleeps.  But Hussein's not alone:  a core team of Oracle engineers and some of the most-experienced Apps DBAs in our EBS community hang out there.  They collectively provide amazing advice about R12 to novices and veterans alike.  Some questions are answered in minutes, much faster than most Service Requests logged via Oracle Support.

Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.

Monday May 24, 2010

Reminder: Premier Support for 10gR2 10.2.0.4 Database ends July 2010

[May 24, 2010 update: added additional information to the Extended Support section, and corrected the implications for patch requests for 10.2.0.4]

Regular readers know that Premier Support for the Oracle 10gR2 Database ends in July 2010, a scant few months from now.  What does that mean for E-Business Suite environments running on this database?

The Oracle E-Business Suite is comprised of products like Financials, Supply Chain, Procurement, and so on.  Support windows for the E-Business Suite and these associated applications products are listed here:
The Oracle E-Business Suite can run on a variety of database releases, including 10gR2, 11gR1, and 11gR2.  Support windows for database releases are listed here:
Looking at those two documents together, you'll see that:
  • Premier Support for Oracle E-Business Suite Release 11i ends on November 30, 2010
  • Premier Support for Oracle E-Business Suite Release 12 ends on January 31, 2012
  • Premier Support for Oracle E-Business Suite Release 12.1 ends on May 31, 2014
  • Premier Support for Oracle Database 10.2 (a.k.a. 10gR2) ends on July 31, 2010
[Note: These are the Premier Support dates as of today.  If you've arrived at this article in the future via a search engine, you must check the latest dates in the Lifetime Support Policy documents above; these dates are subject to change.]

It's a bit hard to read, thanks to the layout restrictions of this blog, but the following diagram shows the Premier and Extended Support windows for the last four major database releases certified with Apps 11i:

database-support-windows.png
Do the EBS Premier Support dates trump the 10gR2 DB date?

No.  Each of the support policies apply individually to your combined EBS + DB configuration.  The support dates for a given EBS release don't override the Database support policy.

It might be useful for me to break an example down in more detail: your E-Business Suite Release 11i environment will be eligible for Premier Support up to November 30, 2010, but your 10gR2 database will be eligible for Premier Support only up to July 31, 2010. 

Therefore, let's assume that you're still running Apps 11i on 10.2.0.4 DB on August 1st, 2010.  On that date, your Apps 11i code will be covered by Premier Support.  Your 10.2.0.4 DB will be covered by Extended Support.

The differences between Premier and Extended Support coverage are summarized here (see the Lifetime Support Policy document for the product of your choice for a more detailed discussion of these coverages):



First year of Extended Support fees for 10gR2 waived

Regular readers may recall that fees for the first year of Extended Support for the 10gR2 database are waived.  There is nothing that customers need to do to remain fully supported other than keep your support contracts current.  Higher fees for Extended Support will start August 1, 2011 for most platforms.  This is formally documented in two different places, for those of you who appreciate convergent validation:
There is an effort underway to lobby the Server Technologies group to update their Lifetime Support Policy document with that information, too.

What should EBS customers running 10gR2 do?

Given that the clock for Premier Support is running out on both EBS 11i and the 10gR2 database this year, I'd recommend that EBS 11i customers start planning upgrades to Oracle E-Business Suite Release 12 immediately.  If you're in that boat, as part of that upgrade, you should also consider whether you wish to upgrade your database to either 11gR1 or 11gR2. 

If your Oracle E-Business Suite Release 12 environment is running on the 10gR2 database, you should start planning to upgrade your database either to 11gR1 or 11gR2 immediately.

11gR2 will give you the longest support window, but has relatively fewer EBS customers on it than 11gR1.  If you opt for 11gR1, plan to use 11.1.0.7, since 11.1.0.6 is no longer eligible for Premier Support under the Server Technologies Group's support policies for previous patchsets.

Here's a summary of our EBS database certification roadmap from my EBS Certifications snapshot from April 2010 (which you should review, if you haven't already done so):

E-Business Suite database 
certification roadmap as of April 2010
Where can I find EBS database upgrade information?
DB 10.2.0.5 certification for EBS underway

As you can see in the roadmap diagram above, the terminal release for the 10gR2 database line is expected to be the 10.2.0.5 patchset.  It's expected that you will need to be on this patchset level to request 10gR2 fixes during the Extended Support support window.

Customers running 10.2.0.4 will be able to request patches for that patchset for one year from the April 30, 2010 release of the 10.2.0.5 patchset.  Customers running 10.2.0.4 can continue to do so without any disruption until May 1, 2011.

Our certification of 10.2.0.5 with the E-Business Suite is underway now.  Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates, which I'll post as soon as soon as they're available.   

DB 11.2.0.2 certification for EBS underway

To head off the inevitable follow-up questions:  the latest 11gR2 database release certified with the E-Business Suite is 11.2.0.1 today.  We're working on our certification with 11.2.0.2 right now. 

As for dates, the same disclaimer above applies here; I can't share any projected certification dates for 11.2.0.2, either.  Stay tuned to this blog for updates.

Related Articles
The preceding is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.

Thursday Apr 08, 2010

Premier Support Date Changed for Oracle Application Server 10gR2

Our Fusion Middleware team has changed the Premier Support dates for Oracle Application Server 10gR2 (10.1.2.x).  The new dates are published here:
Premier Support for Oracle Application Server 10gR2 was originally slated to end in December 2010.  We discussed the implications for E-Business Suite Release 11i and 12 environments in this article:



Naturally, you're welcome to post comments about these updates here, but my ability to discuss these changes will be extremely constrained.  Any comments that you post here will be forwarded verbatim to the Fusion Middleware group.

If you have any questions about the new Premier Support dates for Oracle Application Server 10gR2 (10.1.2.x), your best bet would be to log a formal Service Request via My Oracle Support (formerly Metalink) to get one of our Fusion Middleware Support specialists engaged. 

Related Articles

Monday Feb 08, 2010

Premier Support for Oracle Application Server 10g ends December 2010

[April 8, 2010 Update:  The Oracle Application Server 10gR2 10.1.2 dates have changed.  The dates in this article are no longer accurate but are preserved here for archival purposes.  See the current Lifetime Support Policy for Fusion Middleware document for more details.]

All E-Business Suite systems administrators should review the Oracle Lifetime Support brochures on the Oracle Lifetime Support website regularly.  In particular, EBS sysadmins should monitor changes to the following documents:
  1. Lifetime Support Policy: Oracle Technology Products (PDF, 389 K)
  2. Lifetime Support Policy: Oracle Fusion Middleware Products (PDF, 315 K)
  3. Lifetime Support Policy: Oracle Applications (PDF, 709 K)
As you can see from the second document, Premier Support for Oracle Application Server 10g versions 10gR2 10.1.2 and 10gR3 versions 10.1.3 ends in December 2010.  It's important to understand how this will affect support for your E-Business Suite environments.

Implications for E-Business Suite Release 11i environments

You may have integrated your EBS 11i environment with a number of external Oracle Application Server 10g components, including:
  • Oracle Single Sign-On and Oracle Internet Directory 10g
  • Oracle Discoverer 10g
  • Oracle Web Cache 10g
  • Oracle Portal 10g
Premier Support for these externally-integrated Oracle Application Server 10g components will end in December 2010.  You should plan on upgrading these components to their Fusion Middleware 11g equivalents before December 2010. 

Implications for E-Business Suite Release 12 environments

There are two different types of considerations for Oracle E-Business Suite Release 12 environments:
  1. Support implications for internal EBS 12 technology stack components
  2. Support implications for externally-integrated OracleAS 10g components
1. Support implications for internal EBS 12 technology stack components
The Oracle E-Business Suite Release 12 technology stack includes Oracle Application Server 10gR2 10.1.2 components for Forms and Oracle Application Server 10gR3 10.1.3 components for OC4J.  These components are part of the internal E-Business Suite technology stack, i.e., they are installed by the E-Business Suite Rapid Install.  Updates to these internal technology stack components are also delivered by the E-Business Suite division through our regular updates such as E-Business Suite 12.1.1.

Your internal E-Business Suite Release 12 technology stack components built on Oracle Fusion Middleware 10gR2 and 10gR3 will remain supported for the duration of the support lifetime for Oracle E-Business Suite 12.  The December 2010 Premier Support end date for Oracle Application Server 10g does not apply to the internal Oracle E-Business Suite Release 12 technology stack components

In other words, you will receive Premier Support for these internal Apps 12 technology stack components as long as the Apps 12 release is covered by Premier Support.

2. Support implications for externally-integrated OracleAS 10g components

You may have integrated your EBS 12 environment with a number of external Oracle Application Server 10g components, including:
  • Oracle Single Sign-On and Oracle Internet Directory 10g
  • Oracle Discoverer 10g
  • Oracle Web Cache 10g
  • Oracle Portal 10g
  • Oracle Web Center 10g
Premier Support for these externally-integrated Oracle Application Server 10g components will end in December 2010.  You should plan on upgrading these components to their Fusion Middleware 11g equivalents before December 2010.
Which Fusion Middleware 11g components are certified?

You can upgrade your external integrations to the following Fusion Middleware 11 components immediately:
  • Oracle Internet Directory 11g
  • Oracle SOA Suite 11g
We're still working on the following Fusion Middleware 11g external certifications:
  • Oracle Discoverer 11g
  • Oracle Web Cache 11g
  • Oracle Portal 11g
  • Oracle Web Center 11g
  • Prepackaged Oracle integrations for Oracle BPEL 11g
Oracle's Revenue Recognition rules prohibit us from discussing certification and release dates, but you're welcome to monitor or subscribe to this blog for updates, which I'll post as soon as soon as they're available.   

Remember, also, that you can find a handy one-page summary of all of our current certifications here.  This is extracted from our CERTIFY database on My Oracle Support, which should be consulted for platform-specific certifications.

Related Articles
The following is intended to outline our general product direction.  It is intended for information purposes only, and may not be incorporated into any contract.   It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision.  The development, release, and timing of any features or functionality described for Oracle's products remains at the sole discretion of Oracle.

Tuesday Jul 21, 2009

Updated Tips for Debugging Sun JRE + Forms Focus Issues for EBS 11i and 12

Oracle Jinitiator 1.3 will be desupported for Oracle E-Business Suite Release 11i users at the end of this month, July 31, 2009.  If you haven't already begun your conversion from JInitiator to the native Sun Java Runtime Engine (JRE) plug-in, now is the time to start. 

The end of this month marks the end of the JInitiator era for Apps 11i.  After this point, we will only support the Sun JRE for Forms users connecting to the E-Business Suite.  I've summarized everything you need to know about the EBS switch from JInit to the Sun JRE in this roundup article.

Sun Java Website screenshot Screencap of Sun's Java SE website

Clusters of Common Focus-Related Issues

As more of you make the cutover, we've seen that your reported issues are clustering around some common themes.  Based on your feedback and reported issues, we've updated our internal training for all Support engineers who cover Applications Technology topics.  Our latest diagnostic and debugging techniques for EBS Forms focus-related issues have been refreshed. 

Our Support and Development teams published notes for diagnosing Forms focus-related issues with Apps 11i earlier this year.  That troubleshooting guide's scope has been broadened to include additional guidance and tips for Oracle E-Business Suite Release 12 environments, too:

The latest topics covered in this Note include:

  • What is a focus issue?
  • Why are Focus Issues Experienced?
  • Symptoms Indicating a Loss in Focus
  • Strategy for Investigating and Resolving Focus Issues
  • The Right Checks to Ensure it's a Focus Issue
  • Fixing Known Focus Issues
  • Determining the Current Forms Version and MLR Patch (Release 11i)
  • Determining the Current Forms Version and MLR Patch (Release 12)
  • Gathering the Right Information
  • Debugging Steps for Focus Issues
  • Reporting a Focus Loss to Oracle Support Services

Getting Support from Oracle for Your Conversion

I've noted this before, but it's worth repeating. We're very interested in helping you get through this conversion with a minimum of pain. If you hit any problems with your Apps conversion to the native Sun JRE plug-in, please log a formal Service Request via Metalink. Our Support engineers will work with you on this, and also track the underlying issues to see whether changes to our documentation or patches are warranted. If necessary, we'll work with Sun to get fixes prioritized for future JRE releases, too.

Given my position in Oracle Development and the visibility of this blog, I sometimes think that my perspective on customer deployments might be a little skewed.  I'd appreciate your help in getting an accurate view of how these conversions are going for you. I'd be very interested in hearing about your experiences, good or bad. What went well? What went sideways? Please feel free to sound off in the comments or drop me a private email with more details about your migration.

Related Articles

Friday Jun 26, 2009

Roundup: Oracle JInitiator 1.3 Desupported for EBS Customers in July 2009

[June 29, 2009 Update: The July 2009 desupport date for JInitiator 1.3 applies to E-Business Suite customers only. Generic Oracle Forms customers should see Note 761159.1 for generic JInitiator desupport dates.]

We've covered the impending demise of JInitiator and the certification of the native Sun Java client in many articles already.  With the sun setting on Oracle Jinitiator next month, this is a good time to summarize the essentials about running Windows-based Java clients with the E-Business Suite:

  1. Sun's Java Runtime Engine (JRE) is certified with both EBS 11i and 12
  2. JInitiator 1.3 will be desupported for E-Business Suite customers at the end of July 2009
  3. JInitiator 1.1.8 was desupported at the end of December, 2008
  4. JInitiator cannot be run on Vista Desktops

If you haven't already started migrating your E-Business Suite end-users to the native Sun JRE plug-in, I'd strongly recommend that you begin this process immediately.

Sun Java Website screenshot Screencap of Sun's Java SE website

1. Sun's Java Runtime Engine (JRE) is Certified with EBS 11i & 12

Oracle JInitiator was originally released as a licenced version of Sun's Java client back when specific features were required to support Oracle Forms. This was particularly necessary for E-Business Suite Forms-based functionality, since the E-Business Suite pushed the envelope of what Forms and Java could do collectively from a user interface perspective.

Sun has since incorporated all of the enhancements needed to support Oracle Forms into their native Sun Java Runtime Engine plug-in. This eliminates the need for Oracle to package its own Java client just for running Oracle Forms-based applications. 

To convert your E-Business Suite environment from JInitiator to the native Sun Java plug-in, see:

Benefits of Switching to the Sun Java Client

The elimination of Oracle JInitiator simplifies your desktop administration environment.  Apps DBAs who have migrated their users to the native Sun JRE no longer have to struggle with compatibility and coexistence problems between JInitiator and other Java runtime clients on the same desktop.

Minimizing Risks of Switching from JInitiator to Sun Java Clients

The majority of customers switching from Oracle JInitiator to the Sun Java Runtime Engine have experienced minimal issues with this conversion.  However, some customers have reported problems, some rather painful.  Problems typically fall into the following categories:

  1. Missing prerequisite E-Business Suite patches or configuration steps
  2. Known issues, e.g. focus-related problems
  3. Conflicts with legacy Java-based application requirements

I strongly recommend a careful review of the Notes above, to ensure that you don't miss any prerequisites or configuration steps.  We document all of the known issues in the respective Notes for Oracle E-Business Suite Release 11i and 12.  We also update our Notes regularly whenever we find new JRE-related compatibility issues with the E-Business Suite.

Some of you might have legacy Java-based applications that require earlier Java clients.  Those legacy applications might only be certified with an old Java release like 1.4.x, and will not work with later JRE releases such as 1.5 or 1.6.  Oracle doesn't have much guidance on third-party Java application compatibility, naturally, so your best option in those situations would be to lobby your legacy application vendor to upgrade their certifications to include the latest Java clients. 

Sun has changed the options for handling multiple Java plug-ins through their "Classic Java Plug-in" and "Next-generation Java Plug-in" technologies.  Handling your requirements for multiple Java plug-ins will vary based upon the JRE versions installed and your default corporate browsers.  If you have multiple Java clients installed on the same Windows desktop, I would strongly recommend that you review the "Static vs. Non-Static Versioning and Set-Up Options" appendices in either Note 290807.1 or 393931.1. 

If you're encountering issues with your EBS conversion to use the Sun Java client, you might find the following document useful:

Minimum JRE Versions Required for E-Business Suite

Apps 11i was originally certified with Oracle JInitiator to run Oracle Forms-based content.  Apps 11i is now certified with the native Sun Java Runtime Engine plug-in.  Apps 11i end-users can use JRE releases on either of the following version levels:

  • JRE 1.5.0_13 and higher
  • JRE 1.6.0_03 and higher

Apps 12 was certified only with the native Sun Java Runtime Engine.  Oracle JInitiator is not certified or supported with Apps 12.

EBS Compatibility and Support for Future JRE Releases

E-Business Suite end-users can upgrade their JRE clients whenever Sun releases a new JRE release on either the 1.5 or 1.6 versions.  EBS users do not need to wait for Oracle to certify new JRE 1.5 or 1.6 plug-in updates with the E-Business Suite.

2.  JInitiator 1.3 will be Desupported for E-Business Suite customers at the end of July 2009

JInitiator 1.3.1.30 was the final certified version for Apps 11i.

Oracle JInitiator 1.3 was built on Sun's JDK 1.3.  Sun has long-since desupported JDK 1.3, so JInitiator 1.3 must be desupported, as well.  Oracle Forms Development has no plans to port JInitiator to JDK 1.4 or higher.

Support Implications for JInitiator Users

Here's what you can expect if you log an Oracle E-Business Suite Release 11i Service Request against JInitiator after the respective dates shown above:

  1. Oracle Support will help you diagnose and isolate the root cause of any compatibility issues between JInitiator and the E-Business Suite.

  2. If there's a workaround or an existing Forms or JInitiator patch, Oracle Support will help you obtain the fix.

  3. If the issue requires a new Forms patch and can be reproduced using the native Sun JRE plug-in, a new bug will be logged against Oracle Forms.

  4. If the issue cannot be reproduced with the native Sun JRE client, no new Forms or JInitiator bugs will be logged.

3.  JInitiator 1.1.8 was desupported at the end of December, 2008

JInitiator 1.1.8.27 was the final certified version for Apps 11i.

I know that some of you continue to run JInitiator 1.1.8 with your E-Business Suite Release 11i environments for legacy compatibility reasons.  I'm afraid that the time has come for you to retire JInitiator 1.1.8.  Error Correction Support for JInitiator 1.1.8 ended on December 31, 2008.  In other words, the Oracle Forms group will no longer issue bug fixes via new versions of JInitiator 1.1.8.x as of December 31, 2008.

The "Support Implications for JInitiator Users" section, above, applies equally to JInitiator 1.1.8, also.

By the way, Oracle Forms Development has (somewhat inexplicably) published Metalink Note 789049.1 indicating that JInitiator will be generically supported until March 29, 2010.  I can't say that I understand this, myself, but the December 2008 desupport notice for JInitiator 1.1.8 for Apps 11i clients is published in Note 472154.1.

4.  JInitiator cannot be run on Vista Desktops

It's not possible to run Oracle JInitiator 1.3 on Microsoft Vista.  Here's why:

  • Oracle JInitiator 1.3 is based on Sun's JDK 1.3
  • Sun's JDK 1.3 is incompatible with Vista.
  • Sun has desupported JDK 1.3, so they have no plans to make it Vista compatible
  • Therefore, JInitiator is fundamentally incompatible with Vista due to its JDK 1.3 dependencies

On Hacking Up JInitiator

Various creative individuals have discovered that it's possible to replace a certain DLL in Oracle JInitiator 1.3 with a JVM from, say, JDK 1.6.  I can't personally testify that these hacks work.  I can say that this kind of surgery makes me intensely uncomfortable.

While it's nice to see creative initiative, I have to remind you that Oracle would regard this as a customization.  We don't recommend customizing Oracle JInitiator for production environments.

What Happens When Something Goes Wrong?

If you do choose to customize Oracle JInitiator 1.3, you should consider the support implications for your users.  If you encounter any issues specific to your customized version of JInitiator, Oracle's default recommendation will be to use the native Sun JRE plug-in.

What Does Oracle Recommend for Vista?

We recommend using the native Sun Java plug-in for Vista client desktops connecting to either Oracle E-Business Suite Release 11i or 12.  The native JRE client is the only certified and supported Java client for E-Business Suite desktops end-users running on Microsoft Windows Vista.

Getting Support from Oracle for Your Conversion

Naturally, we're very interested in helping you get through this upgrade process with a minimum of pain.  If you hit any problems with your conversion to the native Sun JRE plug-in, please log a formal Service Request via Metalink.  Our Support engineers will work with you on this, and also track the underlying issues to see whether changes to our documentation or patches are warranted.  If necessary, we'll work with Sun to get fixes prioritized for future JRE releases, too.

Given my position in Oracle Development and the visibility of this blog, I sometimes think that my perspective on customer deployments might be a little skewed.  This blog's readers tend to be seasoned and highly-skilled Apps sysadmins and Oracle DBAs.  

I'd appreciate your help in getting an accurate view of how these conversions are going for you. I'd be very interested in hearing about your experiences, good or bad.  What went well?  What went sideways?  Please feel free to sound off in the comments or drop me a private email with more details about your migration.

Related Articles

Wednesday Jun 24, 2009

Understanding J2SE 1.5 End-of-Life Implications for Oracle E-Business Suite

Java logo

As with my previous post about the desupport of Sun's Java 1.4 release, you should be aware that the equivalent end-of-life (EOL) for Sun's J2SE 1.5 is coming up in October 2009.

Implications for E-Business Suite Users

Here are the implications if your Apps 11i or 12 environments are running on servers with J2SE 1.5:

  • If you log a Service Request for your environment, Oracle will continue to perform its usual diagnosis, triage, and search through our knowledge base for existing patches and workarounds.   This assistance may be constrained by limited access to a small number of remaining environments running J2SE 1.5.  It is extremely unlikely that we will issue new Apps patches for new compatibility issues identified with the E-Business Suite and J2SE 1.5.
  • Issues isolated to J2SE 1.5 itself will be referred to your operating system vendor for more assistance.  Depending on your vendor, you may be able to purchase extended support for J2SE 1.5 directly from them.
  • Issues that can't be reproduced in E-Business Suite environments running on J2SE 1.6 (6.0) will likely result in a recommendation to upgrade to those later releases.

Upgrading to Java 1.6

Given that Java 1.4 is already desupported and Java 1.5 is soon to be desupported later this year, we strongly recommend that you upgrade your EBS environments to Java 1.6, a.k.a Java 6.  For more information, see:

References

Related Articles

Wednesday Jun 03, 2009

Red Hat Enterprise Linux 2.1 Reaches End-of-Life

In case you missed the notification from Red Hat:  Red Hat Enterprise Linux 2.1 has reached its  End of Life stage.  As of May 31, 2009, Red Hat has discontinued technical support for the the following products:

redhat_small_logo.jpg
  • Red Hat Enterprise Linux AS 2.1
  • Red Hat Enterprise Linux ES 2.1
  • Red Hat Enterprise Linux WS 2.1
  • Red Hat Linux Advanced Server 2.1
  • Red Hat Linux Advanced Workstation 2.1

For complete details, see:

Oracle E-Business Suite Release 11i and 12 are supported on later Red Hat releases, including RHEL 3, 4, and 5.  For more details about E-Business Suite certifications on specific operating system platforms, see:

Related Articles

Monday Jun 01, 2009

Extended Support Fees Waived for EBS 11.5.10 and 10gR2 DB Through 2011

I'm almost caught up on backlogged announcements.  One important piece of news from the Collaborate conference last month was the waiver of Extended Support fees for two products: 

  • Oracle E-Business Suite Release 11.5.10
  • Oracle Database 10gR2.

These are challenging economic times, and some of you have been asking for additional time to plan for major EBS upgrades.  The changes described in the following documents give you a bit more breathing space:

Updates Affecting E-Business Suite Support

Premier Support for Oracle E-Business Suite Release 11.5.10 officially ends in November, 2010.  Premier Support for E-Business Suite 11.5.9 ended in June 2008. This is documented here:

The new support announcements affect what happens after the end of Premier Support.

EBS 11.5.10 Extended Support Fees Waived through November 2011

Once an E-Business Suite version leaves Premier Support, you have the option of purchasing Extended Support for an additional fee.  The good news from this announcement is that the additional fees for the first year of Extended Support for Apps 11.5.10 from November 2010 to November 2011 have been waived.

EBS 11.5.9 Sustaining Support Extended to June 2010

In addition, the first year of Sustaining Support for Apps 11.5.9 has been extended by one year.  Sustaining Support includes fixes for Severity 1 production issues and will include one statutory update:  a US 1099 update for 2009 year-end.  The extension will be in effect through June 2010.

Updates Affecting Database Support

You may still be running your E-Business Suite database on the 10gR2 Database.  Premier Support for the 10gR2 Database officially ends in July 2010.  This is documented here:

Oracle Database 10gR2 Extended Support Fees Waived through July 2011

Like the policy for the E-Business Suite described above, you have the option of purchasing Extended Support for the Oracle Database for an additional fee.  The good news from this announcement is that the additional fees for the  first year of Extended Support for the 10gR2 Database from July 2010 to July 2011 have been waived.

Plan For Your Upgrades As Soon As Possible

These latest announcements don't mean that you can stay on these products indefinitely.  It just means that you have a little extra time to get things together.  The fees for Extended Support will still kick in after these one-year extensions!  I would strongly recommend that you use the extra time to begin planning for your Oracle E-Business Suite Release 12 and 11g Database upgrades now.

Related Articles

Thursday Apr 23, 2009

Premier Support for SSO + OID 10.1.4.2 Ending in November 2009

Oracle E-Business Suite Release 11i is certified with Oracle Single Sign-On and Oracle Internet Directory 10.1.4.  Single Sign-On and Oracle Internet Directory are part of Oracle Application Server (OracleAS) 10g 10.1.4.  We certified EBS with the Oracle Application Server 10.1.4.2 patchset in early 2008, and followed this up with EBS certifications with the Oracle Application Server 10.1.4.3 patchset in February 2009.

OracleAS10143.png

You should be aware that the OracleAS 10.1.4.2 grace period will end in November 2009.  After November 2009, you will still be able to download existing OracleAS 10.1.4.2 patches, but new patches will be issued only for the latest 10.1.4.3 release.

If you've integrated your E-Business Suite environment with Single Sign-On and Oracle Internet Directory 10.1.4.2, I would strongly recommend that you plan an upgrade to the most-current certified OracleAS release. As of today, that's OracleAS 10.1.4.3.  Future readers coming across this article should refer to this blog's one-page Certifications summary for the latest certified configurations.

Want To Know More About Support Policies?

The Server Technologies support policies have recently changed in some important ways.  I've discussed the E-Business Suite implications of those changes in these articles: 

Your Thoughts?

I don't represent the Server Technologies organization (I'm in E-Business Suite Development), but I'm happy to pass on your thoughts and feedback about Oracle's support policies to management teams in those groups.  Feel free to post a comment below or send me a private email.

Related Articles

Sunday Mar 29, 2009

Premier Support for OC4J 10.1.3.3 ends in July 2009

Java logo

Oracle E-Business Suite Release 12 includes OracleAS 10.1.3 Oracle Containers for J2EE (OC4J) for running its Java-based content.  We certified Apps 12 with OracleAS 10.1.3.3 in January 2008 and with OracleAS 10.1.3.4 in December 2008. 

You should be aware that the OracleAS 10.1.3.3 grace period will end in July 2009.  After July 2009, you will still be able to download existing OracleAS 10.1.3.3 patches, but new patches will be issued only for the latest 10.1.3.4 release.

If you're running your E-Business Suite environment on OracleAS 10.1.3.3, I would strongly recommend planning an upgrade to the most-current certified OC4J release. As of today, that's OracleAS 10.1.3.4.  Future readers coming across this article should refer to this blog's one-page Certifications summary for the latest certified configurations.

Want To Know More About Support Policies?

The Server Technologies support policies have recently changed in some important ways.  I've discussed the E-Business Suite implications of those changes in these articles: 

Your Thoughts?

I don't represent Server Technologies organization (I'm in E-Business Suite Development), but I'm happy to pass on your thoughts and feedback about Oracle's support policies to management teams in those groups.  Feel free to post a comment below or send me a private email.

Related Articles

Saturday Mar 28, 2009

Premier Support for Forms 10.1.2.2 Ends in April 2009

Oracle Fusion Middleware Forms Logo

Oracle E-Business Suite Release 12 includes OracleAS Forms & Reports 10g as part of its technology stack.  EBS 12.0.0 shipped with Forms 10.1.2.0.2.  We certified Forms 10.1.2.2 with EBS 12 in August 2007 and with Forms 10.1.2.3 in November 2008.

You should be aware that the Forms 10.1.2.2 grace period will end in April, 2009.  After April 2009, you will still be able to download existing Forms 10.1.2.2 patches, but new patches will be issued only for the latest 10.1.2.3 release.

If you're running your E-Business Suite environment on Forms 10.1.2.2, I would strongly recommend planning an upgrade to the most-current certified Forms release. As of today, that's Forms 10.1.2.3.  Future readers coming across this article should refer to this blog's one-page Certifications summary for the latest certified configurations.

Want To Know More About Support Policies?

The Server Technologies support policies have recently changed in some important ways.  I've discussed the E-Business Suite implications of those changes in these articles: 

Your Thoughts?

I don't represent Server Technologies organization (I'm in E-Business Suite Development), but I'm happy to pass on your thoughts and feedback about Oracle's support policies to management teams in those groups.  Feel free to post a comment below or send me a private email.

Related Articles

Friday Mar 27, 2009

Premier Support for 11.1.0.6 Database Ends in October 2009

The Server Technologies support policies have recently changed in some important ways.  I've discussed the E-Business Suite implications of those changes in these articles: 

O_Database11g_clr.gif

Your feedback following the publication of those articles suggests that you'd find it helpful to get more warnings about upcoming desupport dates for Database and Fusion Middleware components.  Those products' desupport dates affect EBS users, so I'll start posting more articles about upcoming (or recently passed) desupport dates here.

Upgrade EBS Environments Running on Database 11.1.0.6

The adoption curve for E-Business Suite customers on the 11gR1 database is still in its early stages.  For those of you who have made the jump, you should be aware that the 11.1.0.6 database grace period will end in October, 2009.  After October 2009, you can still download existing 11.1.0.6 database patches, but new patches will be issued only for the latest 11.1.0.7 database.

If you're running your E-Business Suite environment on the 11.1.0.6 database, I would strongly recommend planning an upgrade to the most-current certified database. As of today, that's the 11.1.0.7 database for both Apps 11i and 12.

We're working with early betas of the upcoming 11gR2 database right now.  I don't have firm schedules for either the release date of 11gR2 or our certifications with various E-Business Suite releases yet.  You're welcome to monitor or subscribe to this blog for updates.

For more details about the grace periods of different database releases, see:

Your Thoughts?

I don't represent the Server Technologies organization (I'm in E-Business Suite Development), but I'm happy to pass on your thoughts and feedback about Oracle's support policies to management teams in those groups.  Feel free to post a comment below or send me a private email.

Related Articles

The preceding is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decision. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

Friday Mar 20, 2009

Premier Support for 10.2.0.3 Database Ended in February 2009

The Server Technologies database support policies have recently changed in some important ways.  I've discussed the E-Business Suite implications of those changes in these articles: 

Your feedback to those articles has made it clear that we can improve how we communicate the generic database and Fusion Middleware desupport dates to EBS users.

Upgrade EBS Environments Running on Database 10.2.0.3

In case you missed those articles, you should be aware that the 10.2.0.3 database Premier Support grace period ended in February, 2009.  After February 2009, you can still download existing 10.2.0.3 database patches, but new patches will be issued only for the latest 10.2.0.4 database.

[Read More]

Friday Feb 20, 2009

On Database Patching and Support: A Primer for E-Business Suite Users

The Oracle Server Technologies division has issued some important updates to their support policies in the following document:

These changes affect support policies for the database, Oracle Enterprise Manager, Fusion Middleware, and Collaboration Suite.  These changes are important enough to warrant an in-depth discussion about the implications of the database-related updates for E-Business Suite customers.  This article also discusses the E-Business Suite database certification process and the safety of applying interim patches to your Apps environments.  I'll cover the Apps-specific implications for the other technology products in a future article.

[Read More]

Tuesday Dec 30, 2008

Reminder: Migrate Your JInitiator Clients to Sun JRE Now!

[June 29, 2009 Update: The July 2009 desupport date for JInitiator 1.3 applies to E-Business Suite customers only. Generic Oracle Forms customers should see Note 761159.1 for generic JInitiator desupport dates.]

The significance of many problems lessens over time, so procrastination has its place as a stress management technique.  Unfortunately, putting off your EBS end-user migration from Oracle JInitiator to the native Sun Java plug-in doesn't fall into that category.  We are down to the last grains of sand in this particular hourglass.

Oracle E-Business Suite Release 11i end-users access Forms-based content either with the native Sun Java Runtime Engine (JRE) client or Oracle JInitiator.  Oracle JInitiator comes in two flavors: 1.8 and 1.3.  The sun is setting for both JInitiator versions.

Error Correction Support (ECS) for JInitiator 1.1.8 will end on December 31, 2008.  In other words, the Oracle Forms group will no longer issue bug fixes for the JInitiator 1.1.8 codeline as of tomorrow.

Error Correction Support for JInitiator 1.3 for E-Business Suite Release 11i customers will end on July 31, 2009.

Diagram showing Forms JRE JInitiator desktop client architecture layers

[Read More]

Tuesday Aug 12, 2008

Identity Crisis: Are Patches to EBS 11.5.9 Equivalent to 11.5.10?

[Aug 14, 2008 Update: Added an observation from one of our readers who pointed out that the more of the latest patches you've applied on top of your existing 11.5.9 environment, the faster the upgrade to 11.5.10 will be.]

A frequently asked question popped up again in my inbox this morning. Its recurrence is particularly timely with the end of Premier Support for E-Business Suite Release 11.5.9 in June 2008. The question is:

If an EBS 11.5.9 environment has some or all of the EBS 11.5.10 Family Packs installed, is it considered to be an 11.5.10 environment?

[Read More]

Thursday Jul 03, 2008

Out With the Old, In With the New

[Read More]
About

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
4
5
6
7
8
9
10
11
12
13
14
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today