Here's the first of a string of new platform certifications announced last week. HP-UX PA-RISC 11.31 is now certified for both E-Business Suite Release 11i and 12.

Key Prerequisites
Release 11i
- E-Business Suite 11.5.10.2
Release 12
- Rapid Install startCD 12.0.0.23 (patch 5972626) or later
- You must apply an update for the oraparam.ini files in the E-Business Suite Tools (10.1.2) and Application Server (10.1.3) ORACLE_HOMEs (Patch 6461336) if you:
- Installed E-Business Suite Release 12 on HP-UX 11.3 and upgraded your operating system HP-UX 11.3.1
- Performed a new installation of E-Business Suite Release 12 on HP-UX 11.32
- Oracle Applications Installation and Upgrade Notes, Release 11i (11.5.10.2) (Metalink Note 316806.1)
- Oracle Applications Installation and Upgrade Notes, Release 12 (12.0) for HP-UX PA-RISC (Metalink Note 402308.1)
Comments (2)
Guys,
Hoping I can get a quick yes/no kind of an answer from one of you experts.
We run 11.5.10.2 (middle tier Linux) on database 10.2.0.2 on HP-UX PA RISC (11.11).
We purchased some new HP Itanium servers and want to put our test and development instances (we have 25, yes 25 non-prod Oracle Apps envs) on these new servers. We did a quick test and the database migrate seamlessly from pa risc to Itaniums. We won't be migrating Production for some time now (I would say 6 months to a year). So we would be in a situation where we would run Production on pa risc, non production on Itanium. Do you see a major issue with this. I should add that we do plan to keep the final pre-production (last step before changes go to Production) would still be pa risc.
Do you see a major issue with this ?
Thanks.
Posted by Naveen | May 1, 2008 9:00 PM
Posted on May 1, 2008 21:00
Naveen,From a technical perspective, you can safely run your production and testbed instances on different supported operating system platforms. From a strategic standpoint, you may wish to reflect on whether such an approach meets your Quality Assurance goals, though. The traditional use of non-production testbeds is to test patches, extensions, and configuration changes prior to rolling them into production. If these environments are dissimilar, it's difficult to generalize testbed results to your production environments. Having your final preproduction environment mirror your production platform is a good idea. For maximum safety, you should ensure that all of the system tests you performed on the preceding environments are also run on this penultimate environment.Regards,Steven
Posted by Steven Chan | May 2, 2008 12:29 PM
Posted on May 2, 2008 12:29