Customer Story: Part 1 - Upgrading a heavily customised Oracle E-Business Suite to R12.2.9 with minimal downtime (Almac)

By Rishin Mitra

Elevator Pitch

Are you planning to upgrade your Oracle E-Business Suite instance, but concerned about extended downtime? Come, join us in this session and we will show you how we managed to upgrade a heavily customized and integrated Oracle E-Business Suite system from R12.1.3 to R12.2.9 with minimal downtime.

Description

Almac Clinical Services is a 24/7 drug manufacturing and distribution company delivering Clinical Supplies worldwide. A key component in their consistent delivery of exceptional customer service is their heavily customised and extended E-Business Suite instance. Implemented on a high availability architecture of multiple application nodes, stretched RAC database and a hardware load balancer to minimise planned downtime. In this presentation we will show how we prepared to upgrade a heavily customized EBS system from R12.1.3 to R12.2.9, with minimum downtime and little impact to their customer base. We will discuss the upgrade path, identification of CEMLIs and how we remediated objects that violated EBS R12.2 Coding standards for ADOP through multiple test cycles before the production upgrade.

Audience will need to have a basic understanding of E-Business Suite.

Notes

This presentation is based on our experience with Upgrading ALMAC’s heavily customised and extended E-Business Suite instance from R12.13 to R12.2. Implemented on a high availability architecture of multiple application nodes, stretched RAC database and a hardware load balancer with extensive customization and integrations with several other Oracle databases and third-party applications/extensions, the entire process was pretty much complex. We will discuss how we managed to bring down the downtime for the upgrade from 136 hours to just 24 hours, which was compliant with the time agreed with the business.

Audience will need to have a basic understanding of E-Business Suite.