The transition to extended support for EBS 11.5.10.2 is right around the corner - November. Some of ya'all are obviously going to stay with 11i and take advantage of the one year of free extended support. Fair enough…I've said before it would make sense for some customers to wait.
For those of you waiting to upgrade, I'd like to bring one really important point to your attention: Oracle's Extended Support policy for 11.5.10.2 requires a minimum baseline patch level. You can read about that minimum baseline in the following Metalink documents:
- 883202.1: Minimum Baseline Patch Requirements for Extended Support on Oracle E-Business 11.5.10
- 1116887.1: Critical E-Business Suite 11i (11.5.10) Extended Support Information on Minimum Baseline Patch Requirements
You will need to meet the minimum baseline patch requirements if you intend to receive Extended Support from Oracle for EBS 11.5.10.2. You may want to start reading now...
NOTE: Thanks to the OAUG Customer Support Council for bringing this issue to everyone's attention.
2 comments:
The minimum baseline patch list for EBS 11.5.10.2 is like a mini upgrade project. First of all, one has to be on ATG.RUP6 level. This will require a round of mega patching for many modules notably HR. With so much regression testing required, I think it might as well be worth to upgrade to R12!
I've recently assisted a client with analysis and testing of the 11.5.10.2 baseline patches, and I can echo Mohan's sentiments. Getting to the baseline is not trivial, though of course if you've been keeping up with family packs for your installed products, it's not as bad as it could be.
As with any My Oracle Support document, it's worth checking back on Note 883202.1 occasionally for changes. There were two significant updates to the document between April and July 2010, which caused some consternation for my client, who thought that they had testing well in hand; instead had to make adjustments to accommodate the changes to the baseline requirements. I was subsequently (jokingly) asked to avoid revisiting the document. :-)
Regards,
John P.
Post a Comment