Industry: Hospitality
Key Technologies and Platforms: Oracle E-Business Suite, Oracle Database, Oracle Access Manager (OAM), Oracle Internet Directory (OID), MarkView, iCaps, Oracle Enterprise Manager (OEM), Hyperion, OBIA
About the Client
A global hospitality enterprise operates luxury and business properties across multiple regions. Its core enterprise systems run on Oracle E-Business Suite, supported by Oracle databases and integrated middleware components.
The IT landscape includes Oracle EBS, Oracle Databases, service-oriented architecture, OBIA (BI Apps, ODI & OAS), Hyperion, iCaps, MarkView, OAM, and OID. These systems support business-critical financial and operational workflows.
As multiple components approached the end of support, the organization initiated an Oracle EBS upgrade program to stabilize its technology foundation and ensure long-term support continuity.
Business Requirements
To address these challenges, the enterprise required:
- Upgrade of the EBS application to the latest stable version
- In-place database upgrade
- Upgrade of middleware components, including OAM, OID, MarkView, and iCaps
- Structured DEV → SIT → UAT execution with one mock production run
- OEM enablement
- Post-upgrade stabilization
- 24×7 AMS support
- Monitoring, tuning, and timely issue resolution
- Reduced TCO through automation and standardization
Business Challenge
Several components of the environment had moved into sustaining support, increasing operational risk.
- End of Premium Support:- E-Business Suite R12.1.3 was on Sustaining Support. Oracle Database 12.1.0.2 Extended Support has ended. Existing middleware versions were nearing the end of error correction support.
- Unsupported Applications:- MarkView 11g and iCaps 12.2.1.3 had reached end-of-support, increasing vulnerability exposure
- Complex Landscape:- A 4-node EBS architecture and a large 16 TB RAC database increased the effort required for upgrade planning and execution.
- Minimal Downtime Tolerance:- The business required minimal disruption during the upgrade due to critical operations.
The Solution
The objective was straightforward. Bring the Oracle environment back into support without interrupting ongoing business operations. Instead of attempting everything at once, the Oracle EBS upgrade was broken into manageable stages. Each step was completed, validated, and stabilized before moving forward. This kept the environment steady while changes were introduced.
Structured Upgrade Execution
The team worked through the DEV, SIT, and UAT environments one at a time rather than overlapping activities. Each phase was completed and reviewed before moving forward. Prior to production, a mock run was carried out to walk through the entire sequence end-to-end. That dry run helped identify small gaps and timing dependencies that could have caused delays later.
Jade relied on its EASE framework and a collection of scripts refined over earlier engagements. The Oracle EBS upgrade methodology was used as a working reference during execution, helping the team stay aligned while avoiding unnecessary back-and-forth or last-minute adjustments
Business Benefits Achieved
- Extended Support Timeline
- EBS is supported till 2036
- Database 19c supported till 2029
- OAM/OID & iCaps supported till 2030
- MarkView 14c supported till 2031
- Downtime Reduction: 35% reduction through online patching.
- Incident Reduction: 19% fewer incidents post upgrade.
- SLA Compliance: 99.5% adherence.
- DB Cloning Efficiency: 30% reduction in time taken for DB cloning and reduced dependency on the storage team.
- Improved Monitoring & Governance: Automated monitoring and proactive issue detection.