Tuesday May 10, 2011

Database 10.2.0.5 Certified with EBS on Nine Additional Platforms

As a follow-on to the original certification announcement, Oracle Database 10gR2 Patch Set 10.2.0.5.0 is now certified with Oracle E-Business Suite Release 11i and Release 12 (12.0, 12.1) on the following additional platforms:

Release 11.5.10.2 + ATG RUP 6 and higher

  • HP-UX PA-RISC (64-bit) (11.11, 11.23, 11.31)
  • HP-UX Itanium (11.23, 11.31)1
  • IBM: Linux on System z (RHEL 4 and 5, SLES 9 and 10)1
Release 12 (12.0)
  • HP-UX PA-RISC (64-bit) (11.11, 11.23, 11.31)
  • IBM: Linux on System z (RHEL 4 and 5, SLES 9 and 10)1
Release 12 (12.1)
  • HP-UX PA-RISC (64-bit) (11.23, 11.31)
  • IBM: Linux on System z (RHEL 5, SLES 9 and 10)
1: This is a database tier only (or split tier) configuration where the application tier must reside on a different fully certified E-Business Suite platform

This announcement includes:
  • Oracle Database Vault
  • Transparent Data Encryption (Column Encryption)
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO)
  • Export/Import Process for Oracle E-Business Suite Release 11i and Release 12 Database Instances
EBS 12 References
EBS 11i References

Related Articles

Monday May 09, 2011

Oracle Database 11gR2 11.2.0.2 Certified with EBS on Microsoft Windows

As a follow-on to our 11.2.0.2 certification announcement late last year, Oracle Database 11g Release 2 (11.2.0.2) is now certified with Oracle E-Business Suite Release 12 and 11i on the following Microsoft Windows platforms:

Release 12.1.1 and higher
  • Microsoft Windows Server (32-bit) (2003, 2008)
  • Microsoft Windows x64 (64-bit) (20031, 20081, 2008 R22)
Release 12.0.4 and higher
  • Microsoft Windows Server (32-bit) (2003)
  • Microsoft Windows x64 (64-bit) (2003, 2008, 2008 R2)1
Release 11.5.10.2 + ATG PF.H RUP 6 and higher
  • Microsoft Windows Server (32-bit) (2003)
  • Microsoft Windows x64 (64-bit) (2003, 2008)1
1: This OS is a 'database tier only' or 'split tier configuration' platform where the application tier must be on a fully certified E-Business Suite platform.
2: This OS is a 'database tier only' platform for Release 12.0. For 12.1.1 or higher, it is also supported on the application tier via the migration process outlined in My Oracle Support Document 1188535.1.

This announcement for Oracle E-Business Suite R12 and 11i includes:
  • Oracle Database Vault
  • Transparent Data Encryption (Column Encryption)
  • Advanced Security Option (ASO)/Advanced Networking Option (ANO)
  • Export/Import Process for Oracle E-Business Suite Release 11i and Release 12 Database Instances
EBS 11i References
EBS 12 References
Related Articles

Wednesday Feb 23, 2011

Windows 7 Service Pack 1 Certified with E-Business Suite

windos7_logo2.png
There are three possible configurations for Windows 7 desktop clients:
  1. 32-bit Windows 7, 32-bit browsers, 32-bit JRE
  2. 64-bit Windows 7, 32-bit browsers, 32-bit JRE
  3. 64-bit Windows 7, 64-bit browsers, 64-bit JRE
We certified the first configuration in December 2009:  E-Business Suite with 32-bit Windows 7 desktop clients running 32-bit versions of Internet Explorer (IE) and Firefox with the 32-bit JRE.

We certified the second configuration in September 2010: E-Business Suite with 64-bit Windows 7 desktop clients running 32-bit versions of IE and Firefox with the 32-bit JRE.

I'm pleased to announce that Microsoft Windows 7 Service Pack 1 (SP1) is now certified with both of those configurations for Oracle E-Business Suite 11i and Oracle E-Business Suite R12 with the following minimum requirements:

Internet Explorer 8 (32-bit)
ie8_logo_125.png
Oracle E-Business Suite 11i Prerequisites
  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or higher
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6) (patch 5903765) or higher.
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) (note 125767.1).
  • MLR Patch 8888184
  • Java client plug-in JRE 1.6.0_03 (32-bit) or higher.
Oracle E-Business Suite R12.0.x Prerequisites
  • Oracle Applications Technology R12.ATG_PF.A.DELTA.6 (patch 7237006) or higher.
  • Oracle Forms Version 10.1.2.3 or higher.
  • Java client plug-in JRE 1.6.0_03 (32-bit) or higher.
Oracle E-Business Suite R12.1.x Prerequisites
  • Oracle E-Business Suite 12.1.1 or higher.
  • Java client plug-in JRE 1.6.0_03 (32-bit) or higher.
Firefox 3.6.x (32-bit)
firefox_logo4.jpg
Oracle E-Business Suite 11i Prerequisites
  • Oracle Applications patch 10 (11.5.10) plus Maintenance Pack 11.5.10 CU2 or higher
  • Oracle Developer 6i patchset 19 (6.0.8.28.x) or higher (note 125767.1)
  • Oracle Applications Technology 11i.ATG_PF.H Rollup 6 (RUP 6)(patch 5903765) or higher
  • Applications Framework Patch 7651759
  • Java client plug-in JRE 1.6.0_10 (32-bit) or higher.
  • It is also strongly recommended that 11i.ATG_PF.H Rollup 6 (RUP 6) users apply patch 7567782 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. This is particularly important for running client side next-generation JRE plugin (JRE 1.6.0_10 or higher).
Oracle E-Business Suite R12.0 Prerequisites
  • Oracle Applications Technology R12.ATG_PF.A.delta.6 (patch 7237006) or higher.
  • Applications Framework Patch 7602616
  • Java client plug-in JRE 1.6.0_10 (32-bit) or higher.
  • It is also strongly recommended to apply patch 7567840 which removes the use of the jpi-version parameter and switches Firefox to a non-static versioning model. This is particularly important for running client side next-generation JRE plugin (JRE 1.6.0_10 or higher).
Oracle E-Business Suite R12.1 Prerequisites
  • Oracle E-Business Suite 12.1.1 or higher.
  • Java client plug-in JRE 1.6.0_10 (32-bit) or higher.
  • Exceptions
Oracle JInitiator Not Supported

Premier Support for Oracle JInitiator has expired for E-Business Suite customers.

Premier Support for Oracle JInitiator 1.1.8 ended in December 2008, and Premier Support for Oracle JInitiator 1.3 ended for EBS customers in July 2009.  For more information about JInitiator desupport and switching your EBS end-users from JInitiator to the Sun JRE, see:
Windows 7 desktop clients are certified only with the native Sun Java Runtime Engine (JRE) with Windows 7.  Oracle JInitiator was built on top of Java 1.3.  Java 1.3 is desupported by Sun Microsystems and and not compatible with either Windows Vista or Windows 7.  We have no plans to certify Oracle JInitiator with Windows 7.

On Hacking Up JInitiator -- Please Don't

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 About Earlier Versions of IE?

Microsoft only supports IE 8 on Windows 7 desktops.  Microsoft does not support earlier versions of IE on Win7, so Oracle is only able to support IE8 on Windows 7 clients for the E-Business Suite.

Exceptions to this certification

Oracle JDeveloper 10g is not certified on Windows 7 desktop clients.  Our Fusion Middleware group has not publicly announced any plans for this certification.  If you are interested in this combination, I strongly recommend your logging a formal Service Request via My Oracle Support against the JDeveloper product to request it.

For information on other client based products that are not certified on Windows 7 please see:
Why are you interested in the third configuration?

As I mentioned in my previous update on this topic, we've certified the first two configurations and we're working on the third.  You've asked for it, so we'll deliver.

That said, I am curious about your business need for the final certification (Win7 64-bit + 64-bit browsers and JREs).  Firefox 64-bit releases seem to lag in functionality and in the general release cycle.  Some reports suggest that 64-bit browsers do not necessarily provide improved performance across the board, and may have compatibility issues -- most notably with Flash, since Adobe is still working on their 64-bit Flash Player.

Even more telling, in fresh installs of Windows 7 64-bit, Microsoft configures the default browser to be IE 32-bit, not IE 64-bit.  In other words, end-users need to take an extra step to run the 64-bit version of IE. 

If you're planning to reconfigure your users' desktops to invoke a 64-bit browser by default, I'd be very interested in understanding your reasons.  Feel free to post a comment here or drop me an email.

References
Related Articles

Monday Feb 21, 2011

Choosing the Right JDeveloper Release for Your EBS Environment

115914.gif
Oracle E-Business Suite developers use a special build of Oracle JDeveloper. This build contains the correct Oracle Application Framework (OA Framework or OAF) libraries corresponding to a specific version of Oracle E-Business Suite (specifically, to an ATG patch level). For customers and developers who are building OA Framework components and extensions to Oracle E-Business Suite, one of the first questions is "How do I find the right version of JDeveloper?"

Oracle makes these OA Framework/JDeveloper builds available in separate patches when a new ATG patch level is released.   A handy My Oracle Support Document shows the ATG patch levels and the corresponding patch containing the correct version of JDeveloper with the right versions of OA Framework libraries:

The document covers the OA Framework and JDeveloper patches for both Release 11i and Release 12.

Happy coding!

Related Articles

Friday Feb 18, 2011

Discoverer 11.1.1.4 Certified with E-Business Suite


[Read More]

Oracle Internet Directory 11.1.1.4 Certified with E-Business Suite

Oracle E-Business Suite comes with native user authentication and management capabilities out-of-the-box. If you need more-advanced features, it's also possible to integrate it with Oracle Internet Directory and Oracle Single Sign-On or Oracle Access Manager, which allows you to link the E-Business Suite with third-party tools like Microsoft Active Directory, Windows Kerberos, and CA Netegrity SiteMinder. 
3rd_party_architecture.png
For details about third-party integration architectures, see either of these article for EBS 11i and 12:
Oracle Internet Directory 11.1.1.4 is now certified with Oracle E-Business Suite Release 11i, 12.0 and 12.1.  OID 11.1.1.4 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.4.0, also known as FMW 11g Patchset 3.  Certified E-Business Suite releases are:
  • EBS Release 11i 11.5.10.2 + ATG RUP 7 and higher
  • EBS Release 12.0.6 and higher
  • EBS Release 12.1.1 and higher
Oracle Internet Directory 11.1.1.3.0 can be integrated with two single sign-on solutions for EBS environments:
  • With Oracle Single Sign-On Server 10g (10.1.4.3.0) with an existing Oracle E-Business Suite system (Release 11i, 12.0.x or 12.1.1)
  • With Oracle Access Manager 10g (10.1.4.3) with an existing Oracle E-Business Suite system (Release 11i or 12.1.x)
Platforms certified for R12
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (Red Hat Enterprise Linux 4, 5)
  • Linux x86 (SLES 10)
  • Linux x86-64 (Oracle Linux 4, 5)
  • Linux x86-64 (Red Hat Enterprise Linux 4, 5)
  • Linux x86-64 (SLES 10)
  • Oracle Solaris on SPARC (64-bit) (9,10)
Platforms certified for Release 11i
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (Red Hat Enterprise Linux 4, 5)
  • Linux x86 (SLES 10)
  • Oracle Solaris on SPARC (64-bit) (9,10)
Other platform certifications still underway

Certifications for other operating system platforms are still underway.  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.   

References
Related Articles

Portal 11.1.1.4 Certified with E-Business Suite

Oracle Portal 11g allows you to build, deploy, and manage enterprise portals running on Oracle WebLogic Server.  Oracle Portal 11g includes integration with Oracle WebCenter Services 11g and BPEL, support for open portlet standards JSR 168, WSRP 2.0, and JSR 301.

Portal 11g (11.1.1.4) is now certified with Oracle E-Business Suite Release.  Portal 11.1.1.4 is part of Oracle Fusion Middleware 11g Release 1 Version 11.1.1.4.0, also known as FMW 11g Patchset 3.  Certified E-Business Suite releases are:
  • EBS Release 11i 11.5.10.2 + ATG RUP 7 and higher
  • EBS Release 12.0.6 and higher
  • EBS Release 12.1.1 and higher
If you're running a previous version of Portal, there are a number of certified and supported upgrade paths to Portal 11g (11.1.1.4):
upgrade_1111_paths.png
Platforms certified for R12
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (Red Hat Enterprise Linux 4, 5)
  • Linux x86 (SLES 10)
  • Linux x86-64 (Oracle Linux 4, 5)
  • Linux x86-64 (Red Hat Enterprise Linux 4, 5)
  • Linux x86-64 (SLES 10)
  • Oracle Solaris on SPARC (64-bit) (9,10)
Platforms certified for Release 11i
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (Red Hat Enterprise Linux 4, 5)
  • Linux x86 (SLES 10)
  • Oracle Solaris on SPARC (64-bit) (9,10)
Other platform certifications still underway

Certifications for other operating system platforms are still underway.  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.   

References
Related Articles


Thursday Feb 17, 2011

Identifying Data Model Changes Between EBS 12.1.3 and Prior EBS Releases

[Update June 21, 2011: A complementary tool that compares seed data between different EBS releases is now available.]

The EBS 12.1.3 Release Content Document (RCD, Note 561580.1) summarizes the latest functional and technology stack-related updates in a specific release.  The E-Business Suite Electronic Technical Reference Manual (eTRM) summarizes the database objects in a specific EBS release. 

Those are useful references, but sometimes you need to find out which database objects have changed between one EBS release and another.  This kind of information about the differences or deltas between two releases is useful if you have customized or extended your EBS instance and plan to upgrade to EBS 12.1.3. Where can you find that information?

Answering that question has just gotten a lot easier.  You can now use a new EBS Data Model Comparison Report tool:

This new tool lists the database object definition changes between the following source and target EBS releases:
  1. EBS 11.5.10.2 and EBS 12.1.3
  2. EBS 12.0.4 and EBS 12.1.3
  3. EBS 12.1.1 and EBS 12.1.3
  4. EBS 12.1.2 and EBS 12.1.3
For example, here's part of the report comparing Bill of Materials changes between 11.5.10.2 and 12.1.3:
Screenshot of EBS data model comparison report for Bill of Materials 12 1 3 and EBS 11 5 10 2 bom_1213_diffs.png

What types of database objects does this tool cover?

This tool includes reports of the differences in:
  • Regular tables
  • Partitioned tables
  • Index organized tables
  • Global temporary tables
  • Queued tables
  • Views
  • Indexes
  • Sequences
  • Materialized views
  • Materialized view logs
  • Advanced queues
  • Packages
  • Triggers
  • Types
Your feedback is welcome

This new tool was produced by our hard-working EBS Release Management team, and they're actively seeking your feedback.  Please feel free to share your experiences with it by posting a comment here.  You can also request enhancements to this tool via the distribution list address included in Note 1290886.1.

Related Articles

Tuesday Feb 15, 2011

Sun JRE 1.6.0_24 Certified with Oracle E-Business Suite

jceecolorlogo2.gif
The mismanaged session cookie issue (now fixed) may have made you a little nervous about automatically applying new JRE updates.  To reassure you on that front:
  • Sun Java Runtime Environment 1.6.0_24 (a.k.a. JRE 6u24, 1.6.0_24-b07) is certified with E-Business Suite Release 11i and 12.
  • JRE 1.6.0_24 contains the fixes for the mismanaged session cookie issue that were originally released as part of JRE 1.6.0_23.
All JRE releases are certified with EBS upon release

Our standard policy is that all E-Business Suite customers can apply all JRE updates to end-user desktops from JRE 1.6.0_03 and higher.  We test all new JRE releases in parallel with the JRE development process, so all JRE releases are considered certified with the E-Business Suite on the same day that they're released by our Java team. 

In other words, you do not need to wait for a certification announcement before applying new JRE releases to your EBS users' desktops.  If you wish, your desktop administrators can enable the Java "Automatic updates" option on your end-users' desktops.

What's new in Java 1.6.0_24?

See the 1.6.0_24 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Wednesday Feb 09, 2011

New Whitepaper: Upgrading EBS 11i Forms + OA Framework Personalizations to EBS 12

Personalizations are -- and have always been -- one of the safest and most upgradable ways to "customize" your Oracle E-Business Suite screens, both for Oracle Forms-based screens and for Oracle Application Framework-based pages. However, the upgrade from Release 11i to Release 12.1 spans many years of EBS evolution, during which time Oracle has actively been building many new features and modules. A lot has changed in Oracle E-Business Suite that may affect upgrading your personalizations from 11i to 12.1. 

We have published a new note on My Oracle Support that discusses ways to evaluate your existing personalizations:

Two distinct types of personalizations

There are two distinct types of personalizations:

  1. Form Personalization
  2. OA Framework Personalization.

Both types of personalization are completely metadata-based. The personalizations are stored as data in database tables. However, because the underlying technologies (Oracle Forms and OA Framework) are very different, Forms personalizations and OA Framework personalizations are not equivalent and cannot be converted or migrated from one to the other.

Diagram showing how personalizations can be transported for like-to-like functionality from EBS 11i to 12 Like-to-Like.gif

Critical factors when affecting upgradeability

Upgradability of personalizations is based on the premise that you are upgrading "from like to like." That is, a personalization based on a certain form, affecting certain fields, will be upgradable to the next version of the same form assuming that the underlying structure of the form is the same (that is, the blocks and fields touched by the personalization are still in the form and have the same names). In other words:

  • For an upgrade from one minor release to another minor release, personalizations are generally likely to be upgradable.
  • For an upgrade from one major release (11i) to another major release (12.1), personalizations are much less likely to be upgradable.

Personalizations that need to be reimplemented manually

A personalization is not upgradable if you are not upgrading "from like to like." This can happen for a number of reasons:

  1. A screen or page has been sufficiently modified in the new version of the product such that the old objects that were personalized no longer exist in the new version. For the 11i to 12 upgrade, however, forms are more likely to have been rebuilt in OA Framework than to have been modified using Oracle Forms.
  2. An Oracle Forms-based screen has been replaced by an OA Framework-based page. This is very common across the 11i to 12.1 upgrade, because many products have rebuilt a lot of their Oracle Forms-based functionality into OA Framework while adding or redesigning other features. For example, the user interface for item instance functionality in Oracle Install Base has been rewritten in OA Framework.
  3. A screen or page has been moved into a different product, so the personalization metadata no longer applies (because each product has its own namespace). For example, between 11i and 12.1, some payments forms were removed from Oracle Payables (AP) and their functionality was consolidated with other payments functionality into a new Oracle Payments (IBY) module. Personalizations made to those original AP payments forms would no longer apply.

Comparing EBS 11i screens to EBS 12 equivalents

For the most part, when you upgrade an OA Framework-based page from Release 11i to 12.1.3, that OA Framework page will still exist in 12.1.3 unless the specific Oracle E-Business Suite product has been heavily redesigned. So in general, OA Framework personalizations are likely to upgrade smoothly ("like to like") to 12.1.3, though of course it depends on the specific products you have.

There are various ways to tell if a particular form or page no longer exists in 12.0 or 12.1. Generally, you should start with the upgrade manuals for your installed products and determine if there has been a major redesign of any of the modules you have. In those cases, most of your form personalizations will no longer apply, and in fact, you will probably no longer need them anyhow. For example, as mentioned above, payments functionality has been moved into a separate Oracle Payments module (IBY). Many customizations you might have had for that functionality can be retired instead of re-implemented because the new product offers significant configurability, and features were added as standard that previously may have required customization to achieve.

For further information, see Note 1292611.1.  Happy reading and upgrading!

References

Related Articles


Tuesday Jan 25, 2011

Database 10gR2 10.2.0.5 Certified with EBS on 14 Additional Platforms

Somehow this certification that was completed last year missed out as a blog article (though it was updated at the time in our official Certifications matrix on My Oracle Support). 

As a follow-on to our original certification announcement, Oracle Database 10gR2 Patch Set 10.2.0.5.0 is certified with Oracle E-Business Suite Release 11i and R12 on the following additional platforms:

Platforms certified for 11i (11.5.10 CU2+ATG_PF.H.delta.6 (RUP 6) and higher)

  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • Oracle Solaris on SPARC (64-bit) (8, 9, 10)
  • Oracle Solaris on x86-64 (64-bit) (10) (See Note 1)

Platforms certified for R12 (12.0.4 and higher) and 12.1 (12.1.1 and higher):

  • HP-UX Itanium (11.23, 11.31)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • Oracle Solaris on SPARC (64-bit) (8, 9, 10)
  • Oracle Solaris on x86-64 (64-bit) (10) (See Note 1)

Screencap of download screen for 10 2 0 5 database patchset page 10205-download.png


Notes

  1. This is a split configuration certification where the application tier must be on a fully certified E-Business Suite platform.

Certified Database Options

This database patchset certification also includes the following 10gR2 10.2.0.5 database options:

  • Real Application Clusters
  • Oracle Database Vault
  • TDE Column Encryption
  • Advanced Security Option/Advanced Networking Option (ANO/ASO) 
Should You Upgrade to This Release?

There are two important considerations if you're deciding whether to upgrade to this release.  The first:  Premier Support for 10gR2 ended in July 2010.  The second: Error Correction Support for 10.2.0.4 ends in April 2011 -- in three months.  For more details about what this means for E-Business Suite environments, and recommendations, see this article:
EBS 12 References
EBS 11i References
Related Articles

Monday Jan 24, 2011

In-Depth: Thoughts on Testing from a Battle-Scarred Support Engineer

[Editor's Note: Weighing in at over 3,100 words, Nick Quarmby's treatise below is more of a whitepaper-in-disguise than our traditionally-short blog articles.  This article is worth your time, though.  In my experience, shortchanging testing simply translates to longer upgrade times downstream.  With EBS 11i now in Extended Support, everyone still on that release should already have their R12 planning underway.  Nick's insights and tips are worth careful consideration by everyone, but particularly so for if you're planning your R12 upgrade.]



"The more I practice, the luckier I seem to get."

"If you think safety is expensive, just try having an accident."

The two quotes above I think pretty accurately sum up the importance of preparation and planning. The first has been attributed to various professional golfers over the years and suggests luck is never accidental. If things work, they work for a reason and that reason is usually because of good preparation, not good luck.

The second quote has been attributed to various airline industry executives. Here the message is that however much time, and inevitably money, that you spend making sure your planes do not crash, it will cost you considerably more if one of them does.

The real message is of course that planning and preparation pay off in the long term and, in the context of your Oracle Applications upgrade, you can conclude that successful upgrades are the result of good testing, not good fortune.

This article is just a few thoughts from a battle-scarred Support Engineer on why good testing is crucial to the success of your system and why it is important for you to thoroughly test any patches, upgrades or migrations before carrying out the work on your production environment. The great majority of the work that you do in any project will be testing. Underestimate it at your peril. Testing is not simply a necessary evil which has to be endured before the inevitable, white-knuckle ride of the production upgrade. Testing is not where you should be cutting corners. Testing is where you should be going into every conceivable corner you can find and looking for something that might, without warning, jump out of the shadows and derail your production upgrade.

There are links at the end of the document to various tools you have access to which may help your testing but this article is not intended to go into the specifics of testing but simply to discuss how testing should be approached and hopefully raise awareness of the consequences of not doing enough testing.

Preparation

A significant Oracle Applications upgrade is a project that will be measured in months, not weeks. The most important part of that long process will be the work that is done before the production upgrade.

A requirement to upgrade a system or perform maintenance is usually triggered via a business or technical requirement. Once a need to upgrade is identified, the work always seems to be considered urgent - these days everything is urgent. Early on in the project you need to clearly identify what is needed to achieve a successful upgrade and present this to the people driving the project. You may sometimes feel you are presented with unreasonable timescales to complete a project and commercial pressures beyond your control have placed you in this position. This is sometimes an inevitability but it is for these reasons that, as early as possible in a project, you emphasise to the people driving your business that systems do not change over the course of one frenetic weekend. Well, actually, they do, but what happens during that weekend is simply the tip of the iceberg.

Behind the scenes you must do a lot of work to prepare for that tiny weekend window at the end of your long project plan. It's sometimes inevitable that tasks tend to concertina towards the end of a project and, whilst some people work better under pressure with a visible and looming deadline, many others do not. Use your time wisely unless you look forward to sleepless nights.

Testing should be performed on a complete cloned copy of your production environment, and, where possible, on an identical hardware environment. If migrating to new hardware, your upgrade testing should include the new hardware so you are confident you can configure the software on the new hardware and that it performs correctly in the new environment.

You should never consider applying untested patches on your production environment.  However urgent a patch may be, it is never so urgent you should risk the stability of the whole production environment by applying it untested. Oracle Applications patches (patches applied using adpatch) are not reversible without using database rollback/flashback features and it would also require a detailed analysis of the patch and its log files in conjunction with your specific system. You should never assume you can manually reverse even the simplest of Oracle Applications patches. Oracle Support cannot provide this service for you remotely via a Service Request (SR).

Do not rely on the assurances of your suppliers and assume everything will work on the day. You need to prove to yourself that your suppliers will deliver what you need and when you need it. Contact them early in the project - they will be grateful for the opportunity to be part of your plans. If things go wrong, having a supplier to blame for things not working may absolve you of some responsibility but you will still have to present this failure within your organisation and that will reflect on you, no matter how much you consider that you were not responsible for that failure.

Always follow the documentation.   Context sensitive documents exist for upgrading all components of Oracle Applications and should be followed. If you cannot find an appropriate document for a process in your upgrade, contact Oracle Support who should be able to advise you of the right Note or manual to follow. Do not assume generic documentation will be applicable to your Oracle Applications environment.

Our published documentation is designed to achieve a successful upgrade. It is not tested by trying to perform the upgrade steps in a different order or by deliberately omitting steps to see how the upgrade will turn out. You should perform all steps in the upgrade documentation unless you have a clear reason not to, or clear guidance from Oracle Support that a step can be omitted.

Consider phasing your upgrade.  If a major upgrade involves both a database and Applications upgrade you may be able to perform this in separate, shorter downtimes. 10gR2 and 11gR2 are certified on both 11i and R12 so you could perform a database upgrade during your first downtime, return the system to your users and perform the Applications upgrade in the second downtime at a later date. This will increase the testing you have to do and will also require additional user acceptance testing but you may find this method works for you.

Testing is not just to establish that the technical upgrade is a success. Testing should also include ensuring that the system you build performs acceptably under load and remains stable. The links at the end of this article refer to products you can use to measure performance and load on your environment. 

The truth is the hardest work you will do in your whole upgrade project will be the testing and preparation. It is during testing that you will find where you have to reduce what takes two weeks into something that you'll be lucky to get 48 hours to perform. It is during testing that you will have to find imaginative ways to solve the issues you encounter.


Issues Encountered During Testing

Some people see testing as something that is only for the overly cautious - those people who are too scared to confront real-time events when they arise. We may live in an increasingly risk-averse society but the truth is that smart people are always testing. Only fools rush in. A macho or cavalier attitude to testing rarely produces a reliable or stable environment.

Your testing will reveal issues that have to be solved.  These truly are opportunities and not problems. This is why you are testing in the first place - so that you do not see these errors when you come to the production upgrade. If you encounter issues during testing then you must find a solution to these issues or find a workaround that does not compromise the rest of the upgrade. Skipping a documented step because you don't think it's significant can easily cause problems further down the line. 

Perform at least one test upgrade before you make a commitment to how soon you can perform your production upgrade. A well run project should allow the key people involved time to scope out their work before committing to any deadlines. If you do not know the scale of the job, you cannot accurately plan for the production upgrade. As part of the whole project, you should plan to perform a minimum of three successful test upgrades.

During testing you will see software acting inconsistently under apparent laboratory conditions. Some people seem to accept software is a somewhat capricious product that can behave unpredictably and that it's acceptable to see it acting differently from one day to the next so long as it doesn't actually do the wrong thing. This is not how commercial business software is designed or expected to behave. You should be able to find a reason for that inconsistent behaviour. If you cannot, then you have to make a call on how significant you believe that inconsistency is, but be assured, there is a reason for this apparently erratic behaviour. Software - even fiendishly complicated software - does not have a mind of its own.

Use Service Requests (SR) with Oracle Support to validate your upgrade plans and to help you if you encounter any technical issues during your testing. An upgrade where the first we hear from you is when you raise a Severity one SR during the production upgrade is already a failing upgrade. We want to know about any issues you encounter during testing when these can be handled as Severity two and three type SRs where you can work closely with a single engineer, usually in your own time zone, for the duration of the SR.

Be flexible in your testing. Oracle may release a new maintenance pack or updates to patches or the technology stack in the middle of your testing. Consider whether you should now integrate these later releases into your planned upgrade. This will require additional testing but you may not get another downtime window for some time so it's important you upgrade to the latest software whenever possible.


The Production Upgrade

Some DBAs approach a production upgrade with about as much relish as they approach invasive dental work. They know it will be painful, there may be some sleepless nights, and it will cost much more than expected. This is a worrying but increasingly common scenario and it's a real concern to think that some customers feel that the production phase of an upgrade is not only the most stressful part of their project but also the stage most likely to produce an unpredictable outcome.

It would be wrong to dismiss the above concerns as groundless but it's important to realise that with good planning and testing, the production upgrade should not exactly be a formality, but it should certainly be something for which you are fully prepared for every scenario you can think of, and probably a few you have not thought of.

If you approach your production upgrade with dread, unsure of what might go wrong, and wondering if it will succeed then this is almost certainly due to a lack of effective preparation and testing. You may feel under pressure to deliver a system but this is nothing compared to the pressure you will feel if you deliver nothing at all. If you really go into your production upgrade being unsure of its success then you should not be contemplating performing it. Production downtime is not something you will be offered regularly and it should not be lost on speculative or poorly tested work.

The Apollo astronauts on their way to the Moon, had a "go/no go" decision at each critical point in their mission. Your production upgrade should run on similar lines. At each significant stage in the production upgrade you should decide whether you are on course to reach your objective. You should not be afraid to abandon a production upgrade which has gone wrong and instead focus on returning the old system to your users as quickly as possible. This should be the worst scenario you can contemplate but your project plan should include a contingency for it. Your users may not thank you for this but having the old system available on Monday morning is always more acceptable than having no system at all to offer them. You can always come back to fight another day. At no time should you be in a position that you have nothing to offer your users but a broken, part-upgraded environment.

Your production upgrade is not the place where you should be trying any of the following:-

  • Fixing errors that you have not seen during testing
  • Trying out a different upgrade path that you did not think of during testing
  • Applying patches that you did not require during testing

The common message in the above is that you should not be trying anything in your production upgrade that you have not done during testing. This should be pretty much a golden rule of your production upgrade. One day you may have to break that rule but that day will be an exceptional one.

Using standby database functionality from Data Guard is very useful when upgrading. You can configure up to nine standby databases off your production database. If, for example, you have a standby database, you can decouple this at the start of the upgrade. This is then immediately available as a pre-upgrade backup should your production upgrade fail. If the production upgrade succeeds then you just bring this standby database back online after the upgrade and it will automatically resynchronise with the new production database through Data Guard. This may be a little more complicated if your upgrade includes a database upgrade but standby databases can still have an important part to play in any maintenance exercise.

It's important to approach a production upgrade with a positive mental attitude. A belief that what you are going to do will succeed means you will approach any problems with a belief that you can solve them. If you expect your upgrade to fail then problems come like body blows and you struggle to pick yourself up and fight back. You will only have that positive mental attitude if the weeks and months you have spent prior to the production upgrade have been used constructively giving you the confidence you need to make your production upgrade a success.


When Things Go Wrong

Fans of The Hitchhiker's Guide to the Galaxy will know that printed on the cover of this book is the phrase "DON'T PANIC" (always in upper case). This is always good advice in difficult circumstances. A calm head is always best when things don't seem to be going to plan.

Always have a contingency plan.  Expect things to go wrong and congratulate yourself when they don't, but do not assume that the most fastidious of testing will guarantee a success. Having a contingency or backup plan will support you. You'll be reassured that you were smart enough to plan for every eventuality.

Do not expect to rely on others in a crisis.  This is your upgrade and your responsibility. Your colleague at the next desk may be sympathetic to your predicament but that does not mean they do not have their own issues to deal with. Nobody knows your upgrade as intimately as you do. If your production upgrade fails and you need help, consider how much time you may have to spend familiairising a third party with your upgrade and your environment before they can offer constructive help as to how you might overcome your current problem. They may be able to help you but if they cannot, then the onus is back on you to find a solution to your problem. Good preparation before you started your upgrade will be invaluable here.

Do not assume that if a component of the upgrade fails then you can resort to the supplier and they will be responsible for the failure. That may give you a solution in the long term but it may not fix your immediate short term problem. Having a new solution after the event may deflect some of the recriminations as to why the upgrade failed but that will not make the failure go away.


Conclusion

We want your upgrade to succeed.  Oracle Support is available to help during testing and also during your production upgrade. Make sure you use us to ensure everything we offer is available to you throughout your project. Engage your Service Delivery Manager (SDM) and ensure they know about your upgrade. They can make Oracle Support aware of your plans.

The media is full of stories about IT upgrades that have failed. Outside of promotional literature, you rarely read a headline that says "IT Project Goes Exactly to Plan." That does not mean that successes do not exist -- it just means that they do not make the news.

There is rarely much glory in doing your work quietly, efficiently and delivering what is promised, on time and within budget. But if you look around your organisation you will notice that some of the most successful people in the business are the ones who do exactly that. They're not lucky. They planned it that way.


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

Tuesday Jan 18, 2011

Critical Patch Update for January 2011 Now Available

The Critical Patch Update (CPU) for January 2011 was released on January 18, 2011. Oracle strongly recommends applying the patches as soon as possible.

The Critical Patch Update Advisory is the starting point for relevant information. It includes a list of products affected, pointers to obtain the patches, a summary of the security vulnerabilities, and links to other important documents.

Supported Products that are not listed in the "Supported Products and Components Affected" Section of the advisory do not require new patches to be applied.

Also, it is essential to review the Critical Patch Update supporting documentation referenced in the Advisory before applying patches, as this is where you can find important pertinent information.

The Critical Patch Update Advisory is available at the following location:

The next four Critical Patch Update release dates are:

  • April 19, 2011
  • July 19, 2011
  • October 18, 2011
  • January 17, 2012

Wednesday Jan 12, 2011

Latest DSTv15 Timezone Patches Available for E-Business Suite

Wooden_hourglass_small2.jpg
If your E-Business Suite Release 11i or 12 environment is configured to support Daylight Saving Time (DST) or international time zones, it's important to keep your timezone definition files up-to-date. They were last changed in July 2010 and released as DSTv14. DSTv15 is now available and certified with Oracle E-Business Suite Release 11i and 12.

Is Your Apps Environment Affected?

When a country or region changes DST rules or their time zone definitions, your Oracle E-Business Suite environment will require patching if:
  • Your Oracle E-Business Suite environment is located in the affected country or region OR
  • Your Oracle E-Business Suite environment is located outside the affected country or region but you conduct business or have customers or suppliers in the affected country or region
We last discussed the DSTv14 patches on this blog. The latest "DSTv15" timezone definition file is cumulative and includes all DST changes released in earlier time zone definition files. DSTv15 includes changes to the following timezones since the DSTv14 release:
  • Africa/Cairo 2010 2010
  • Egypt 2010 2010
  • America/Bahia_Banderas 2010 2010
  • Asia/Amman 2002
  • Asia/Gaza 2010 2010
  • Europe/Helsinki 1981 1982
  • Pacific/Fiji 2011
  • Pacific/Apia 2011
  • Hongkong 1977 1977
  • Asia/Hong_Kong 1977 1977
  • Europe/Mariehamn 1981 1982
What Patches Are Required?

In case you haven't been following our previous time zone or Daylight Saving Time (DST)-related articles, international timezone definitions for E-Business Suite environments are captured in a series of patches for the database and application tier servers in your environment. The actual scope and number of patches that need to be applied depend on whether you've applied previous DST or timezone-related patches. Some sysadmins have remarked to me that it generally takes more time to read the various timezone documents than it takes to apply these patches, but your mileage may vary.

We've published the following Notes which identify the various components in your E-Business Suite environment that may need DST patches:
Related Articles

Customized Database Listener Names Now Supported for EBS

The database listener name can now be configured using AutoConfig with newly introduced context variable s_db_listener. Prior to this certification it was not possible to use AutoConfig generated listener.ora files for managing listeners from SRVCTL when there were multiple RAC instances on the same server.

To use this feature E-Business Suite customers need to apply the following patch:
  • 11.5.10CU2 - Roll Up Patch 9535311 (RUP-U) or higher
  • 12.0.x - R12.TXK.A.delta.7 or higher
  • 12.1.x - R12.TXK.B.delta 3 or higher
There is a small difference between Oracle Database 10gR2/11gR1 and 11gR2 Listener names. In Oracle Database 10g Release 2 and 11g Release 1 NETCA creates the listener with the given name suffix nodename.

For example : If the given listener name is ebs then NETCA creates listener with ebs_<nodename>.

But in Oracle Database 11g Release 2 NETCA creates the listener with the given name.

To configure the listener with a customized name:
  • Create listener using NETCA
  • Update s_db_listener context variable with listener name.
  • Run Autoconfig.
References
E-Business Suite 11i
E-Business Suite 12
Related Articles

Wednesday Dec 29, 2010

The Eight Most-Important EBS Techstack Stories of 2010

I've never really understood the custom of stuffing a summary of one's family's activities for the year in a Christmas/Hanukkah/Kwanzaa card.  I'd rather my friends kept authentically in touch throughout the year, but perhaps that's just me.

Nonetheless, I see the value of a year-end summary in the IT industry.  I spend a lot of time helping our customers understand the latest new developments... and straightening out confusion over changes to the old and familiar.  It can be hard to keep up with the latest news in this space.

Here are the eight most-important news items for 2010, with suggested actions for Apps DBAs:
  1. Premier Support for EBS 11.5.10 ended on November 30, 2010

    You need to be on a minimum baseline of 11.5.10 patches to be eligible for Extended Support.  New patches for EBS 11i released during the Extended Support period will be produced only for the minimum baseline configuration.

    Action: Ensure that your EBS 11i environments meet the minimum baseline requirements.

  2. Minimum Baselines are Emerging for EBS 12.0 Extended Support

    Extended Support for EBS 12.0 begins on February 1, 2012.  That's only 13 months away.  Minimum baselines haven't been finalized yet, but the 12.0.6 Release Update Pack and the Financials CPC July 2009 are currently slated.

    Action: Ensure that your EBS 12.0 environments meet the currently-specified baseline requirements.

  3. Sun, Windows, and Linux users should have upgraded to JDK 6 by now

    JDK 5's End of Service Life was October 30, 2009 for those three platforms.  If you're running the E-Business Suite on Sun, Windows, or Linux, you should upgrade your EBS servers to JDK 6.  Alternatively, you can purchase Java for Business support (the equivalent of Extended Support for Java).

    Action: Upgrade your Sun, Windows, or Linux EBS servers to JDK 6.

  4. Premier Support for Database 10gR2 ended on July 31, 2010

    The 10gR2 Database is now in Extended Support.  If you're still on 10gR2, you should start planning your upgrade to a higher certified database version such as 11gR2 11.2.0.2.

    Action: Upgrade to 10gR2 databases to 11gR2 11.2.0.2.

  1. EBS 12.1.3 was released

    EBS 12.1.3 was released in August, 2010 and represents the latest EBS 12 update with new EBS 12 features and fixes to improve security, stability, and performance.  EBS 12.1 users can apply this update directly.  EBS 12.0 users must first apply EBS 12.1.1 before applying EBS 12.1.3.

    Action: Upgrade EBS 12 environments to 12.1.3

  2. First-generation Fusion Middleware products are going into sunset mode

    Fusion Middleware 11g was released, putting some older Fusion Middleware products into sunset mode.  Existing Oracle Single Sign-On 10g users should consider their plans for upgrading to Oracle Access Manager.  Existing Discoverer users should consider their plans for upgrading to Oracle Business Intelligence Enterprise Edition (OBIEE) or Oracle Business Intelligence Applications (OBIA).  Existing Oracle Portal users should consider their plans for upgrading to Oracle WebCenter.

    Action: Review upgrade plans for Single Sign-On, Discoverer, and Portal.

  3. Microsoft Windows 7 was certifed; doesn't run JInitiator

    Windows 7 was certified with the E-Business Suite for both 32-bit as well as 64-bit clients.  JInitiator is incompatible with Windows 7, so Forms end-users with Win7 desktops must switch to the native Sun JRE 1.6 plug-in -- preferably at the 1.6.0_23 level or higher.

    Action: Upgrade to Windows 7 if desired; upgrade all Windows clients to JRE 1.6.0_23 or higher.

  4. Microsoft Office 2010 was certified

    Office 2010 was certified with the E-Business Suite in November, 2010 for all currently-supported Microsoft operating systems.  You can even build your own integrators between EBS products and Microsoft Office components via the WebADI Desktop Integration Framework.

    Action: Upgrade to Office 2010 if desired.
Another good year

Software -- and this blog -- is written by people, not machines.  Your support and enthusiasm continues to inspire us and shape our products.  I can't stress how important your feedback is to us in the Applications Technology Group.

We published 148 articles on this blog in 2010 -- roughly three articles a week.  Not bad for a little blog written by volunteer contributors in their free time.  Please let my fellow bloggers know that you appreciate their work, either with private emails or by posting a comment here.

The eight areas that I highlighted above are just the tip of the iceberg.  I highly recommend browsing our archives if you aren't a regular visitor.  If you're looking for a quick snapshot, here's a one-page summary of all important E-Business Suite technology stack components and technologies.

Above all, if you haven't already done so, I strongly recommend subscribing to this blog via email updates or our newsfeed.  We have some exciting news lined up for 2011.  I'd hate for you to miss anything.

Happy New Year.

Steven Chan,
Chief Editor

New Whitepaper: Oracle E-Business Suite on Exadata

[Dec. 30, 2010 Update: Added link to Note 1133355.1]

Our Maximum Availability Architecture (MAA) team has quietly been amassing a formidable set of whitepapers about the Oracle Exadata Database Machine.  They're available here:
If you're one of the lucky ones with access to this hardware platform, you'll be pleased to hear that the MAA team has just published a new whitepaper with best practices for EBS environments:
exadata_v2_feature_main.png
This whitepaper covers the following topics:
  • Getting to Exadata -- a high level overview of fresh installation on, and migration to, Exadata Database Machine with pointers to more detailed documentation
  • High Availability and Disaster Recovery -- an overview of our MAA best practices with pointers to our detailed MAA Best Practices documentation
  • Performance and Scalability -- best practices for running Oracle E-Business Suite on Exadata Database Machine based on our internal testing
As an added bonus, the whitepaper has details about the internal testbeds where this configuration was evaluated with Oracle's own 18 TB Global Single Instance.  The whitepaper's Appendix discusses Exada Smart Flash Cache results, Smart Scan, RAC, and RMAN backup performance.

Need an Overview of Migration Options?

Also useful:  A summary of the different technologies and techniques that you can use to migrate your E-Business Suite database to Exadata can be found here:
That overview Note provides a short but precise analysis of physical migration techniques (e.g. Data Guard Physical Standby, Transportable Database, Transportable Tablespaces, Rapid Clone) vs. logical migration techniques (e.g. Oracle Data Pump).

Related Articles


Friday Dec 17, 2010

Is RAC One Node Certified for E-Business Suite?

Oracle Real Application Clusters (RAC) is a cluster database with a shared cache architecture that supports the transparent deployment of a single database across a pool of servers.  RAC is certified with both Oracle E-Business Suite Release 11i and 12.  We publish best-practices documentation for specific combinations of EBS + RAC versions.  For example, if you were planning on implementing RAC for EBS 12, you would use this documentation:
Many of the largest E-Business Suite users in the world run RAC today, including Oracle; see this Oracle R12 case study for details.

A number of customers have recently asked whether RAC One Node can be used with the E-Business Suite.  From the RAC website:
Oracle RAC One Node is a new option available with Oracle Database 11g Release 2. Oracle RAC One Node is a single instance of an Oracle RAC-enabled database running on one node in a cluster.

Diagram of RAC One Node database migration between nodes rac_one_node.png

RAC ONE Node is supported as a cold failover solution for E-Business Suite environments.  We don't support live node migration; the E-Business Suite does not have code-level support for Fast Application Notification (FAN) events at present. 

Is there RAC One Node documentation for EBS environments?


No, we do not explicitly certify or document E-Business Suite configurations.  You can follow the generic RAC One Node documentation to implement this in E-Business Suite environments.  If you're interested in using this technology with the E-Business Suite, you're advised to run proof-of-concept tests prior to a production deployment to ensure that it meets your operational requirements.

Related Articles


Friday Dec 10, 2010

E-Business Suite Certified with DB 11.2.0.2 on HP-UX Itanium and IBM AIX on Power

As a follow-on to our previous certification announcement, Oracle Database 11g Release 2 (11.2.0.2) s now certified with Oracle E-Business Suite Release 12 (12.0.x and 12.1.x) and 11i (11.5.10.2 + ATG PF.H RUP 6 and higher) on the following additional platforms:

Oracle E-Business Suite Release 12
  • HP-UX Itanium (11.31)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
Oracle E-Business Suite Release 11i
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)

db_11202_screenshot.png

This announcement for Oracle E-Business Suite R12 and 11i includes:
Pending Certifications
  • Transparent Data Encryption (TDE) Tablespace Encryption
  • Other platform certifications are pending and awaiting the availability of this patchset on the platform, including:
    • HP-UX PA-RISC (64-bit)
    • Microsoft Windows Server (32-bit)
    • IBM: Linux on System z 
  • 'Split tier' or 'database tier only' certifications on:
    • AIX 7 (R12)
    • HP-UX Itanium 11.31 (11i)
    • Microsoft Windows x64 (64-bit) (R12)
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.   

EBS 11i References
EBS 12 References
Related Articles

Thursday Dec 09, 2010

Understanding EBS Support Windows, Redux

Last month we discussed the two interlocking support policies that affect E-Business Suite users:
  1. Oracle's Lifetime Support Policy
    Specifies support dates for major EBS release codelines (e.g. EBS 11.5.10.2, 12.0, 12.1) -- and by implication, the latest EBS patchset for a given codeline. The Lifetime Support Policy presents support definitions and dates for three different levels of support:  Premier, Extended, and Sustaining. 

  2. E-Business Suite Error Correction Support Policy (Note 1195034.1)
    Specifies support principles for EBS release update packs for a given EBS releases codeline covered by Premier Support.  Examples of EBS release update packs (RUPs) include EBS 12.0.2, 12.0.3, 12.0.4, 12.0.5, 12.0.6, 12.1.2, 12.1.3. 
The first version of the Error Correction Support Policy introduced the concept of grace periods to allow you time to upgrade to the latest E-Business Suite Release Update Pack.  Generally speaking, this window was eighteen months.

Your feedback led us to review this policy.  In response to your comments, we've made a number of important changes to relax these support policies.  These changes are published in Version 2 of the E-Business Suite Error Correction Support Policy released earlier this month. 

The central theme of these changes is to simplify your maintenance planning by providing you with more detailed information about the dates by which specific Release Update Packs will become minimum baselines for new patches.  In most cases, the new policy allows for more than 18 months to apply the latest Release Update Pack. 

These changes have important operational implications for all E-Business Suite 12 users.  We strongly recommend that you review them carefully.

What's Changed in Version 2 of this policy?
1. Clarified the relationship between one-off patches and Release Update Packs

In particular, we've given more information about the conditions under which one-off patches are created, as well as the minimum release requirements for one-off patches.

2. Replaced the "18 month grace period for N-1 RUPs" concept for general EBS 12 products with simpler baselines
  • E-Business Suite Release Update Pack 12.0.4 for EBS 12.0 after January 2011.
  • E-Business Suite Release Update Pack 12.1.3 for EBS 12.1 after January 2013.
3. Clarified specific exceptions for minimum baselines for two EBS areas
  • EBS modules that are subject to annual legislative updates
  • Applications Technology Group Release Update Packs:
  • ATG Release Update Pack 12.0.6 will be the minimum baseline for EBS 12.0 on February 1, 2011
  • ATG Release Update Pack 12.1.2 will be the minimum baseline for EBS 12.1 on July 1, 2011
  • ATG Release Update Pack 12.1.3 will be the minimum baseline for EBS 12.1 on February 1, 2012
4. Described the process of transitioning from Premier Support to Extended Support

A minimum level of suite‐wide Release Update Packs, product family Release Update Packs, Critical Patch Updates, and applicable technology stack certifications will be set for each E‐Business Suite release prior to its transition from Premier Support to Extended Support.
Although the minimum requirements have not been finalized yet, we've listed some preliminary baselines for both E-Business Suite 12.0 and 12.1 to help you with your maintenance and upgrade planning.
What about E-Business Suite technology stack components?

It's important to remember that Fusion Middleware and database components in EBS instances are separate from the the ATG Release Update Packs and are governed by their own support policies and dates.  This applies to the technology stack components installed by the E-Business Suite Rapid Install (e.g. Oracle Forms, OC4J, database).  This also applies to external standalone components (e.g. Oracle Single Sign-On, Discoverer, SOA Suite) that you may have integrated with your E-Business Suite environment.

You must also plan to update those technology stack components on an ongoing basis.  If you're interested in learning more about the implications of Fusion Middleware and database support windows for E-Business Suite users, see these two articles:
Related Articles

Tuesday Dec 07, 2010

Mismanaged Session Cookie Issue Fixed for EBS in JRE 1.6.0_23

jceecolorlogo2.gif
At last:  some good news for those of you affected by the mismanaged session cookie issue in E-Business Suite environments.  This issue is resolved by the latest Sun Java Runtime Environment 1.6.0_23 (a.k.a. JRE 6u23, internal version 1.6.0_23-b05).

See the 1.6.0_23 Update Release Notes for details about what has changed in this release.  This release is available for download from the usual Sun channels and through the 'Java Automatic Update' mechanism.

This JRE release has been certified with both Oracle E-Business Suite Release 11i and 12.  We recommend this release for all E-Business Suite users.

References
Related Articles

Thursday Dec 02, 2010

Maintaining Your EBS Environment for Maximum Performance

I think that all E-Business Suite DBAs know that they need to apply a number of interoperability patches when upgrading from one database release to another.  These are documented in our Interoperability Upgrade Notes for a given EBS + database combination.  For example, if you're upgrading Oracle E-Business Suite Release 12 to the latest 11gR2 11.2.0.2 database, you'd apply the patches listed here:
However, I don't think it's as widely-known that there are two other classes of patches that you might need to apply.  These are documented in the following two Notes:
  1. Oracle E-Business Suite Recommended Performance Patches (Note 244040.1)
  2. Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (Note 1147107.1)

Performance benchmark graph for EBS 12 1 2 cpu_load.png


What are E-Business Suite "recommended performance patches"?

Oracle E-Business Suite Recommended Performance Patches (Note 244040.1) is written and maintained by our Applications Performance team.  I've covered this team's responsibilities previously, but to recap: this team is dedicated to optimizing the performance of the E-Business Suite.  They perform all of our E-Business Suite benchmarks and high-volume scalability testing, and they work intensively with our largest E-Business Suite customers in fine-tuning E-Business Suite configurations. 

They've summarized all of their hard-won expertise about performance-related patches in a single document.  A major part of this document covers database patches, but that's not all.  It also covers performance-related patches for:
  • Client tools
  • Applications Technology products and components
  • Financials products
  • Manufacturing and Supply Chain products
  • Human Resources products
  • Sales & Marketing products
This should be your first stop after upgrading your database or if you're trying to nail down a troublesome database performance-related issue.  I consider this mandatory reading for all E-Business Suite DBAs.

Do you want to apply database Patch Set Updates?

Our Server Technologies division began releasing quarterly database Patch Set Updates (PSU) in July 2009.   Patch Set Updates include:
  • Field-tested fixes for critical technical issues that may affect a large number of customers
  • Critical Patch Update fixes
Database Patch Set Updates are optional for E-Business Suite users.  If you choose to use them, database Patch Set Updates may safely be applied to Oracle E-Business Suite Release 11i and 12 environments.  Patch Set Updates are fully compatible and supported for use with the E-Business Suite.  Depending upon the database version and Oracle E-Business Suite release, one or more overlay patches may be required to address conflicts with a specific Oracle Database Patch Set Update.

Database Patch Set Update Overlay Patches Required for Use with PSUs and Oracle E-Business Suite (Note 1147107.1) summarizes the latest overlay patches required when applying Database Patch Set Updates to Oracle E-Business Suite environments running on the 10gR2, 11gR1, and 11gR2 databases.  If you use PSUs with your EBS database, you should review this Note on a regular basis.

Related Articles

Tuesday Nov 30, 2010

EBS 11i Extended Support Starts December 2010 with Minimum Patching Baselines

[Editor: This article was originally published in January 2010, and again in August 2010.  Reposting this article in its entirety with small modifications to emphasize the date.]

Premier Support for Oracle E-Business Suite Release 11i ends today, November 30, 2010. Extended Support for EBS 11i begins tomorrow, December 1st, 2010.

Extended Support comes at an additional cost, but these are waived for Oracle E-Business Suite Release 11i through November 2011. I'm in EBS Development and not sales, so you should contact your Oracle account manager with questions about Extended Support costs. 

Here is a comparison of the different support levels:

A new set of minimum technical requirements for Apps 11i goes into effect when Extended Support begins in December 2010.  These new minimum baseline patch requirements are listed in:
What are the impacts of this new baseline?

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.

Minimum Baseline Patch Requirements
  • Oracle E-Business Suite Release 11.5.10 Consolidated Update 2 plus additional patches listed in Note 883202.1
  • ATG Rollup Patchset 6 (11i.ATG_PF.H.delta.6, Patch 5903765)
  • 10.2.0.4 Database or 11.1.0.7 Database
  • Forms6i Patchset 19 (version 6.0.8.28, Patch 6194129)
  • Oracle HTTP Server MLR Patchset 4393827
  • Sun Java Runtime Engine (JRE) 1.6.0_03 or higher
The baseline versions listed here (and in the Note) are current as of the document's release date but may change in the future.  Any changes will be communicated via Note 883202.1.  If you've found this article as the result of a web search, I would strongly encourage you to check the latest version of the Note for the current information.

What EBS 11i products are affected by this new baseline?

In addition to the major technology stack components shown above, Note 883202.1 contains additional minimum baseline requirements for:
  • Applications Technology
    • Common Applications Calendar
  • Contracts
    • Core Contracts
    • Procurement Contracts
    • Project Contracts
    • Sales Contracts
    • Service Contracts
  • Customer Data Management
    • Customers Online
    • Trading Community
  • Financials
    • Assets
    • iAssets
    • Advanced Collections
    • Bill Presentment Architecture
    • Cash Management
    • E-Business Tax
    • Financials for the Americas
    • Financials for Asia/Pacific
    • Financials Common Country
    • Financials for EMEA
    • Financials for India
    • Internet Expenses
    • Lease Management
    • Loans
    • Payables
    • Payments
    • Property Manager
    • Public Sector Budgeting
    • Public Sector Financials
    • Public Sector Financials (International)
    • Receivables
    • iReceivables
    • Treasury
    • U.S. Federal Financials
  • Human Resources
    • Advanced Benefits
    • Approvals Management
    • HR Intelligence
    • Human Resources
    • Labor Distribution
    • Learning Management
    • Payroll (All Localizations)
    • Payroll (International/Custom)
    • iRecruitment
    • Self-Service Human Resources
    • Time and Labor
    • US Federal Human Resources
  • Intelligence
    • Balanced Scorecard
    • E-Business Intelligence
  • Interaction Center
    • Customer Interaction History
  • Logistics
    • Inventory Management
    • Warehouse Management
  • Manufacturing
    • Cost Management
    • Quality
    • Supply Chain Globalization
    • Work in Process
  • Marketing and Sales
    • Incentive Compensation
    • Marketing
    • Partner Management
    • Quoting
    • Sales
    • Sales for Handheld
    • Sales Offline
    • Territory Management
    • Trade Management
  • Order Management
    • Advanced Pricing
    • Configurator
    • Order Capture
    • Order Management
  • Procurement
    • iProcurement
    • Purchasing
    • Sourcing
    • iSupplier Portal
    • Supplier Scheduling
  • Product Lifecycle Management
    • Advanced Product Catalog
    • Bills of Material
    • Document Management and Collaboration
    • Engineering
    • Item Master
  • Projects
    • Grants Accounting
    • Project Billing
    • Project Collaboration
    • Project Costing
    • Project Portfolio Analysis
    • Project Foundation
    • Project Resource Management
    • Projects
  • Service
    • Advanced Scheduler
    • Complex Maintenance, Repair & Overhaul
    • Customer Care
    • Depot Repair
    • Field Service
    • iSupport
    • Teleservice
  • Supply Chain Planning
    • Demand Planning
    • Production Scheduling
    • Strategic Network Optimization
Related Articles

Sunday Nov 28, 2010

Using Two New Oracle Database 11gR2 Features With EBS

ORACLE_DB11G_CLR.GIF

With the recent announcement of Oracle Database 11gR2 (11.2.0.2) certification with Oracle E-Business Suite, we've also certified two new features with the E-Business Suite to make your life a little easier.

These two new features are:

  1. The Single Client Access Name (SCAN) feature that was introduced with the Oracle Database 11g Release 2 Grid Infrastructure to simplify client access to database services.

  2. No need to disable Fast Validation before performing Applications maintenance or upgrade operations.

Single Client Access Name support for EBS environments

Single Client Access Name (SCAN) is an Oracle Real Application Clusters (RAC) 11gR2 feature that provides a single name for clients to access Oracle databases running in a cluster. This means that the client's connect information can remain the same if cluster nodes are added or removed.

The SCAN feature is now certified for use with the EBS AutoConfig configuration management tool, and can be deployed with EBS by following the steps below.

  1. Meet the configuration prerequisites for using the SCAN listener, as per My Oracle Support Knowledge Document Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID  823587.1).

  2. Set the following AutoConfig parameters as shown below:
    • s_scan_name = <SCAN Name>
    • s_scan_port = <SCAN Port>
    • s_update_scan = <TRUE>
  3. Run AutoConfig on the EBS database tier to create SCAN configuration files on that tier.

  4. Run AutoConfig on the application tier to create SCAN configuration files on that tier.

No Need to Disable Fast Validation

With database versions prior to Oracle 11gR2 (11.2.0.2), you needed to disable Fast Validation in the database when performing Applications upgrades or maintenance operations.

To disable Fast Validation, you needed to add the following parameter to the database initialization parameter file:

_disable_fast_validate=TRUE

Failing to set this in Oracle Database 11gR1 (11.1.0.7) or 11gR2 (11.2.0.1) could lead to invalid objects and forms or reports compilation failures, potentially causing problems with product functional flows.

Starting with 11gR2 (11.2.0.2), this parameter no longer needs to be set for upgrade or maintenance operations (and then unset again for normal operations).  This is one less thing for you to have to remember.

References

Related Articles

Monday Nov 22, 2010

Microsoft Office 2010 (32-Bit) Certified with E-Business Suite

ms_office_logo.png

[Editor Jan. 17, 2013 update: Removed outdated references to Open Office.  We have no plans to certify the E-Business Suite with Open Office.]

Microsoft Office 2010 (32-Bit) is certified for integration with Oracle E-Business Suite 11i and Release 12 with the following desktop client operating systems:

  • Windows XP
  • Windows Vista
  • Windows 7 32-bit
  • Windows 7 64-bit
The Oracle E-Business Suite is comprised of several product families such as Financials, Supply Chain Management, Human Resources, and so on.  These product families group together collections of individual products.  Some of these products may be optionally integrated with one or more Microsoft Office components such as Excel, Word, and Projects.

Individual E-Business Suite product teams have the option of building integrations between their products and one or more Microsoft Office components.  This is not mandatory.  Over forty E-Business Suite teams offer these kinds of Office integrations today.

Examples of available integrations include:
  • HRMS Payroll integrations with Microsoft Excel
  • Supply Chain Management Contracts Core integration with Microsoft Word
  • Financials General Ledger (GL) integration with Microsoft Excel
  • Customer Relationship Management (CRM) Proposals integration with Microsoft Word
Which Office versions are certified?

We explicitly tested Microsoft Office 2010 Professional Edition with Oracle E-Business Suite.  We expect that our certification tests also apply to:
  • Home and Student Edition
  • Home and Business Edition
  • Standard Edition
  • Professional Academic Edition
  • Professional Plus Edition
We have no plans to certify the following editions with Oracle E-Business Suite:
  • Office Web Apps
  • Starter Edition
  • Mac Edition
  • Office Mobile
I would not expect the results of our certification with Office 2010 Professional Edition to apply to the above four editions.

How are these integrations supported?

You can log Service Requests against the E-Business Suite product that you're trying to integrate with Microsoft Office. 

For example, you might be trying to take advantage of CRM Marketing (AMS) 12.1.2's integration with Excel 2010.  To get support, you can log an SR against CRM Marketing directly. 

The Support team for that product will help you diagnose and resolve the problem.  If the issue is isolated to a Microsoft product, then it may be necessary to log a corresponding support ticket with Microsoft, as well.

What about 64-bit Office?

Microsoft Office 2010 is available in both 32-bit and 64-bit editions. The 64-bit version is available for a subset of Microsoft's supported operating systems. 

Due to a number of technology issues Oracle E-Business Suite is currently certified against the Microsoft Office 2010 32-bit edition only.  We intend to certify Office 64-bit components with the E-Business Suite; stay tuned for more details on this front.

Thursday Nov 18, 2010

Access to Automated Release Update System Has Changed

The access protocol for the Automated Release Update (ARU) system has changed.  Older versions of the Oracle E-Business Suite Patch Wizard and Patch Manager (part of the Application Change Management Pack for Oracle E-Business Suite) will generate errors when attempting to access E-Business Suite patches.

If you use these tools as part of your E-Business Suite patching procedures, you will need to obtain new versions to ensure continued access to ARU.  You can find links to the updated tools here:
Obtaining Support

If you encounter any issues with these new tools, please log a Service Request via My Oracle Support (formerly Metalink) to get one of our specialists engaged. 

Related Articles

Monday Nov 15, 2010

Two New Options for Signing E-Business Suite JAR Files Now Available

We use Java Archive (JAR) files to deliver certain types of E-Business Suite content to end-user desktop clients.  JAR files can be digitally signed for increased security. 

Oracle E-Business Suite uses a self-signed certificate to sign the JAR files that are downloaded to the client PC when launching forms and other applets (such as Workflow Status Diagram or Account Hierarchy Manager).  By default, E-Business Suite JAR files are signed with 1024-bit self-signed digital certificates.  Self-signed digital certificates can trigger Windows security warnings like this:

Windows Warning dialog box triggered with self-signed Java content - the application's digital certificate cannot be verified - dig_sig_warning.png
Some E-Business Suite users have advanced requirements for signing JAR files, including the ability to:
  1. Sign E-Business Suite JAR files with 3072-bit certificates
  2. Sign E-Business Suite JAR files with digital certificates from third-party Certificate Authorities (CA) (e.g.Verisign, Comodo, etc.)
I'm pleased to announce that both of these advanced JAR file signing options are now certified for Oracle E-Business Suite Release 11i and 12.

What are the benefits of these new signing options?

The first of these two new signing options meets the latest recommendations of the US National Institute of Standards and Technology (NIST):
The second option allows you to prevent the potentially-alarming warning from being triggered when your users access certain E-Business Suite functions for the first time.

Oracle E-Business Suite Release 12 Certified Platforms
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (RHEL 3, 4, 5)
  • Linux x86 (SLES 9, 10)
  • Linux x86-64 (Oracle Linux 4, 5)
  • Linux x86-64 (RHEL 4, 5)
  • Linux x86-64 (SLES 9, 10) 
  • Oracle Solaris on SPARC (64-bit) (8, 9, 10)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • IBM Linux on System z** (RHEL 5, SLES 9, SLES 10)
  • HP-UX Itanium (11.23, 11.31)
  • HP-UX PA-RISC (64-bit) (11.11, 11.23, 11.31)
  • Microsoft Windows Server (32-bit) (2003, 2008 for EBS 12.1 only)
Oracle E-Business Suite Release 11i Certified Platforms
  • Linux x86 (Oracle Enterprise Linux 4, 5)
  • Linux x86 (RHEL 3, 4, 5)
  • Linux x86 (SLES 8, 9, 10)
  • Linux x86 (Asianux 1.0)
  • Oracle Solaris on SPARC (64-bit) (8, 9, 10)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • HP-UX PA-RISC (64-bit) (11.11, 11.23, 11.31)
  • HP Tru64 (5.1b)
  • Microsoft Windows Server (32-bit) (2000, 2003)
References
Related Articles

11gR2 11.2.0.2 Database Certified with E-Business Suite

[Jan 20, 2011 Update: Removed erroneous Linux x86-64 SLES 9 database tier reference]

[Nov 18, 2010 Update: Added HP-UX Itanium to the EBS 11i list of pending certifications]


We certified the 11gR2 11.2.0.1 Database with E-Business Suite 11i and EBS 12 late in 2009.  It's taken a little longer than we had hoped to certify 11.2.0.2, the first patchset for the 11gR2 Database.  The reasons: the release cycle for 11.2.0.2 overlapped with our EBS 12.1.3 release cycle, and some of the ports for this patchset weren't released until just before Halloween.  Our Server Technologies team is as-yet working on other ports, too.

I know that some of you have been eager to apply this latest patchset to your E-Business Suite databases, so I'm very pleased to announce that Oracle Database 11gR2 Patchset 1 Version 11.2.0.2 is now certified with the E-Business Suite. 

Screenshot of 11-2-0-2 11gR2 database patchset 1 Patchset 10098816 download page db_11202_screenshot.png

Oracle E-Business Suite Release 11i
Prerequisites
  • Oracle E-Business Suite Release 11.5.10.2
Certified Platforms
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (RHEL 4, 5)
  • Linux x86 (SLES 10)
  • Linux x86-64 (Oracle Linux 4, 5) -- Database-tier only
  • Linux x86-64 (RHEL 4, 5) -- Database-tier only
  • Linux x86-64 (SLES 10--Database-tier only)
  • Oracle Solaris on SPARC (64-bit) (10)
  • Oracle Solaris on x86-64 (64-bit) (10) -- Database-tier only
Pending Platform Certifications
  • Microsoft Windows Server (32-bit)
  • Microsoft Windows Server (64-bit)
  • HP-UX PA-RISC (64-bit)
  • HP-UX Itanium
  • IBM: Linux on System z 
  • IBM AIX on Power Systems
Oracle E-Business Suite Release 12
Prerequisites
  • Oracle E-Business Suite Release 12.0.4 or later; or,
    Oracle E-Business Suite Release 12.1.1 or later
Certified Platforms
  • Linux x86 (Oracle Linux 4, 5)
  • Linux x86 (RHEL 4, 5)
  • Linux x86 (SLES 10)
  • Linux x86-64 (Oracle Linux 4, 5)
  • Linux x86-64 (RHEL 4, 5)
  • Linux x86-64 (SLES 10)
  • Oracle Solaris on SPARC (64-bit) (10)
  • Oracle Solaris on x86-64 (64-bit) (10)  -- Database-tier only
Pending Platform Certifications
  • Microsoft Windows Server (32-bit)
  • Microsoft Windows Server (64-bit)
  • HP-UX PA-RISC (64-bit)
  • IBM: Linux on System z
  • IBM AIX on Power Systems
  • HP-UX Itanium
Database Feature and Option Certifications
The following 11gR2 11.2.0.2 database options and features are supported for use:
Certification of the following database options and features is still underway:
  • Transparent Data Encryption (TDE) Tablespace Encryption 11gR2 version 11.2.0.2
About the pending certifications

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.    

EBS 11i References
EBS 12 References
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.

Wednesday Nov 03, 2010

Portal 11g (11.1.1.3) Certified with EBS on 17 Additional Platforms

Oracle Portal 11g allows you to build, deploy, and manage enterprise portals running on Oracle WebLogic Server.  Oracle Portal 11g includes integration with Oracle WebCenter Services 11g and BPEL, support for open portlet standards JSR 168, WSRP 2.0, and JSR 301.

We certified Oracle Portal 11g (11.1.1.3) with Oracle E-Business Suite Release 11i (11.5.10.2 + ATG PF.H RUP 7 and higher), 12.0 and 12.1 on five platforms earlier this month. Our hard-working Applications Platform Engineering team has just added 17 new platforms to the list of certified platforms for this configuration. 

Oracle E-Business Suite Release 12
  • Linux x86-64 (Oracle Linux 4, 5)
  • Linux x86-64 (Red Hat Enterprise Linux 4, 5)
  • Linux x86-64 (SLES 10)
  • Oracle Solaris on SPARC (64-bit) (9, 10)
  • HP-UX Itanium (11.23, 11.31)
  • HP-UX PA-RISC (11.23, 11.31)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • Microsoft Windows Server (32-bit) (2003; 2008 for 12.1.1 or higher only)
Oracle E-Business Suite Release 11i
  • Oracle Solaris on SPARC (64-bit) (9, 10)
  • HP-UX PA-RISC (11.23, 11.31)
  • IBM AIX on Power Systems (64-bit) (5.3, 6.1)
  • Microsoft Windows Server (32-bit) (2003)
References
Related Articles

About

Search

Categories
Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today