OracleAS 10.1.2.2 Certified with EBS 11i and 12

Screenshot%20of%20Patchset%204960210%20download%20screen.png

We wrapped up a new certification over the long weekend, but it's a bit of a strange one. We had originally not planned to do this certification at all, for reasons that might be clearer by the end of this article.

However, a suitably large number of you have requested it explicitly, so we revisited that decision.  This is an object lesson in the principle that it never hurts to ask. On to the actual certification announcement:

Oracle Application Server and Oracle Developer Suite 10g Release 2 (10.1.2) Patch Set 2 (10.1.2.2.0) (Patchset 4960210) is now certified for use with E-Business Suite Release 11i and 12 environments. This certification covers all platforms for which this OracleAS patchset is available.

Now for the odd part...

Supported External Oracle Application Server 10g integrations

As many of you know, it's possible to integrate Oracle E-Business Suite Release 11i and 12 environments with external Oracle Application Server 10g instances for the use of the following optional services:

  • Oracle Single Sign-On and Oracle Internet Directory
  • Oracle Portal
  • Discoverer
  • Web Cache
  • Web Center (for Oracle E-Business Suite Release 12 only)
  • Oracle Business Intelligence Enterprise Edition

For pointers to the documentation for these optional Release 11i and 12 integrations, see the respective "Getting Started With..." articles listed below in the Related Articles section.

Some of you use these external Oracle Application Server 10g instances to provide these services to other applications across your enterprise. The most common example of this is Oracle Single Sign-On, which can be used by both the E-Business Suite as well as your custom applications. Some of these custom applications may be built using Oracle Application Server 10g, say, Oracle Developer Suite 10g 10.1.2.0.2.

Upgrading? Decisions, decisions, decisions...

This is where things get interesting, based upon the current Fusion Middleware releases and codelines. I find it confusing, so don't feel badly if you're having trouble keeping up, too. I'll try to recap the key points here, but I've previously covered this in rather-painful detail in this older article.

There are two notable upgrade scenarios:

Scenario 1: SSO-enabled E-Business Suite

In this first scenario, you're using an external Oracle Application Server 10g 10.1.2.0.2 for Single Sign-On (SSO) or Oracle Internet Directory (OID). If you want the latest SSO or OID updates, you must upgrade your Oracle Application Server 10g environment to either 10.1.4.0.1 or 10.1.4.2 because there are no SSO or OID updates in Oracle Application Server 10g 10.1.2.2.

It's important to note that if you're only using your Oracle Application Server 10g environment for Single Sign-On purposes, there's no point in applying the 10.1.2.2 patchset. It certainly doesn't hurt to apply Oracle Application Server 10g 10.1.2.2 to your external instance, but there's no benefit to E-Business Suite users in this scenario.

Scenario 2: Oracle Application Server 10g used for something else

In this second scenario, you're using an external Oracle Application Server 10g 10.1.2.0.2 for Single Sign-On (SSO) or Oracle Internet Directory (OID) as well as for other purposes. For example, you might also be using that same Oracle Application Server 10g instance for custom application development using, say, Oracle Developer Suite 10g 10.1.2.0.2. If you want the latest fixes for Oracle Developer Suite  delivered by 10.1.2.2, then you can apply this patchset to your environment.

In this case, your E-Business Suite integration only "cares" about the Single Sign-On and Oracle Internet Directory components. There aren't any SSO or OID fixes in Oracle Application Server 10g 10.1.2.2, so your E-Business Suite integration is completely unaffected by this patchset.

Go to the Source

There are other possible reasons to apply this patchset. For example, you might be running Portal 10.1.4.0.0, or Oracle Business Inteligence Tools 10g Release 2 (10.1.2.0.2). The very best way of determining whether you need to apply Oracle Application Server 10g 10.1.2.2 is to review the patchset's official README:

References

Related Articles

Comments:

In your scenario #1, how would you apply a CPU Infrastructure patch if you didn't upgrade to 10.1.2.2? 10.1.2.0.2 doesn't seem to have any CPU's this time around? My understanding is that 10.1.2.0.2 no longer gets CPUs. I understand that SSO and OID are all that are required for eBusiness suite and they have their own CPUs but aren't there other components that are used that probably would be patched with the infrastructure CPU (such as Apache, OC4J,...) or would they all be covered by the latest IM CPU?

I don't want to apply patches that aren't required but I also don't want to be exposed with an unpatched component.

Posted by Mike Charchuk on September 02, 2008 at 10:19 AM PDT #

Steven,

A very complex but all too common situation in the field. Good description of what the issues are and what people can do. We can only hope that this all will get easier with Fusion Applications...:-)

Good job.

thx,
John

Posted by John Stouffer on September 02, 2008 at 09:09 PM PDT #

I would like to expand on Mike's comments. Based upon CPU availability, 10.1.2.2 is, at the moment, the only supported 10.1.2.x version of the application server (including SSO) available for use with E-Business Suite. If you stay at 10.1.2.0.2/10.1.2.1, you do not have CPU coverage, hence you are increasing your risk of a compromise. Likewise, you cannot upgrade to 10.1.2.3, as this is not certified.

I understand the problems with supporting/certifying many versions of a system, but if Oracle is going to use critical patch updates to left-handedly desupport software versions, certifications need to keep up with that.

Posted by Tim Guido on September 02, 2008 at 10:11 PM PDT #

Mike and Tim,

Your observations are 100% correct.

CPUs are no longer produced for Oracle Application Server 10g 10.1.2.0.2. If an E-Business Suite customer wishes to ensure that an Oracle Application Server 10g environment has the latest CPUs, then that Oracle Application Server 10g environment needs to be upgraded to 10.1.2.2 (which is the latest certified patchset).

Our OracleAS Global Support CPU Tech Lead confirmed that in a private email to me:

[For example,] a 10.1.4.0.1 or 10.1.4.2 environment will need 10.1.2.2 (or 10.1.2.3) applied in order to get CPU patches on the 10.1.4.0.1 or 10.1.4.2 home. There are extra 10.1.4.0.1 or 10.1.4.2 patches, but both 10.1.2.x and 10.1.4.x CPUs need to be applied together.

Indeed, there are other Oracle Application Server 10g components used as part of the overall SSO/OID dependencies needed in E-Business Suite-integrated configurations.

Likewise, our OracleAS Global Support CPU Tech Lead noted the following:

[For example,] SSO uses both OC4J_SECURITY and OHS (Apache), both needing a patch to at least 10.1.2.2, and both get directly patched with the CPU for 10.1.2.2 (even on the 10.1.4.x home). The CPU ofr 10.1.4.0.1 or 10.1.4.2 only affects OID.

If there are security-related fixes for those components in a recent CPU, then you will need to upgrade to 10.1.2.2 as a prerequisite before applying that CPU.

By the way, we're working on certifying Oracle Application Server 10g 10.1.2.3 right now for externally-integrated instances.

Tim's observation about certifications needing to keep pace with CPU prerequisites is well-taken. I agree that our timing of the 10.1.2.2 certification was less-than-ideal. Failing to take the CPU dependencies into account in our earlier decision to skip the 10.1.2.2 certification for the E-Business Suite was an oversight on our part. I'm grateful to the customers and their teams who brought this to our attention, and I apologize for the last-minute scramble that it may have triggered. This type of error will not occur again on my watch.

Aside from these points, I'm a little nervous about turning this comment thread into a CPU support forum. If there are additional CPU-related questions about OracleAS 10.1.2.2, feel free to email me your Service Request numbers; I'll be sure to engage our CPU specialists to help.

Regards,
Steven

Posted by Steven Chan on September 04, 2008 at 08:41 AM PDT #

i have installed 10.1.2.2 developer suite and i tried to set the patch 10.1.2.3.but the set up stops with a message like 'createFile error 32 when trying set file time'.

Posted by edhok on September 21, 2008 at 12:08 PM PDT #

Hello Edhok,

Metalink Note 560272.1 "Rapidwiz R12 error: Createfile Error 32 When Trying Set File Time" is the only similar error I can see from a quick look round our knowledge base, so unless this note is the same as your situation it would be best to raise a Service Request with Oracle Support for your problem to be investigated in detail

regards

Mike

Posted by Mike Shaw on September 21, 2008 at 03:36 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
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