Oracle Ebs upgrade

 Upgrading Oracle E-Business Suite from 11.5.10.2 (11i) to 12.2 is a major technical and functional upgrade. Oracle supports a direct path from 11.5.10.2 CU2 → 12.2, but you must first meet the required baseline patch and database levels.

Activity	Usually Owned By
EBS upgrade execution	Apps DBA
Database upgrade	DBA
WebLogic / Apache config	Apps DBA / Middleware
DNS updates	Infra / Network
Load balancer VIP switch	Infra / Network / F5 team
Smoke testing	Application / Functional team
User validation	Business users

Here’s a practical high-level manual upgrade sequence typically followed by DBAs and Apps DBAs.

---

1. Verify Source Environment

Confirm:

• EBS version = 11.5.10.2 CU2
• Database version minimum = 11.2.0.4
• OS version certified for 12.2
• Required disk space
• Backup strategy tested

Run:

SELECT release_name FROM fnd_product_groups;

Check DB version:

SELECT * FROM v$version;

Oracle requires DB 11.2.0.4 or higher before 12.2 upgrade.

---

2. Apply Mandatory 11i Baseline Patches

Before upgrade:

• Upgrade to 11.5.10 CU2 if not already there
• Apply:
  • ATG rollups
  • TXK patches
  • Autoconfig latest
  • minimum sustaining support patches

Key Oracle reference:

• Doc ID 883202.1 (minimum baseline)

Oracle explicitly states the source system must be at 11.5.10.2 baseline before direct upgrade.

---

3. Upgrade Database to 11.2.0.4 or 19c

Typical paths:

• 11gR2 → 11.2.0.4
• Many customers now move directly to 19c before/after EBS upgrade

Common steps:

dbua

or manual upgrade scripts:

catupgrd.sql

Then:

@utlrp.sql

---

4. Prepare New 12.2 File System

EBS 12.2 introduces:

• dual filesystem
• online patching
• WebLogic Server

You create:

• fs1
• fs2
• fs_ne

Using Rapid Install:

rapidwiz

Oracle states Rapid Install creates the new application tier filesystem during upgrade.

---

5. Run EBS Upgrade Prechecks

Run:

• ETCC (EBS Technology Codelevel Checker)
• Upgrade Readiness Checker
• Invalid object cleanup

Typical commands:

perl checkDBpatch.sh
perl checkMTpatch.sh

Also:

exec utl_recomp.recomp_serial();

---

6. Backup Entire Environment

Take:

• RMAN backup
• Apps tier filesystem backup
• Context files
• APPL_TOP
• COMMON_TOP
• ORACLE_HOME

This is mandatory before downtime.

---

7. Start Downtime Upgrade

Shutdown application services:

adstpall.sh apps/apps

Enable maintenance mode:

exec fnd_conc_clone.setup_clean;

---

8. Apply 12.2 Upgrade Driver

This is the core upgrade step.

Run:

adpatch options=nocopyportion,nogenerateportion

Apply the unified driver:

u10124646.drv

(or current upgrade driver from Oracle media)

This upgrades:

• data dictionary
• AOL
• products
• schemas
• seed data

This step can take many hours.

---

9. Configure Online Patching (ADOP)

12.2 requires Edition-Based Redefinition.

Run:

perl adopmnctl.pl

Then execute online patching enablement.

Typical scripts:

adop phase=prepare

Oracle notes that 12.2 introduces online patching architecture using adop.

---

10. Run Post-Upgrade Tasks

Tasks include:

• Compile invalid objects
• Generate forms/reports
• Gather schema statistics
• Run autoconfig
• Update profiles
• Rebuild customizations

Commands:

adautocfg.sh

exec fnd_stats.gather_schema_statistics('APPLSYS');

---

11. Apply Latest RUP and AD/TXK Delta

After reaching base 12.2:

Apply latest:

• Release Update Pack (RUP)
• AD Delta
• TXK Delta

Example:

• 12.2.13
• AD/TXK Delta 16+

Oracle strongly recommends moving beyond base 12.2 immediately.

---

12. Validate Functional Areas

Validate:

• Concurrent Managers
• Workflow Mailer
• Forms
• OAF pages
• XML Publisher
• Custom interfaces
• Payroll
• GL/AP/AR flows

Run:

select count(*) from fnd_concurrent_requests;

Check invalids:

select owner, object_name from dba_objects where status='INVALID';

---

13. Test Online Patching Cycle

Mandatory validation:

adop phase=prepare
adop phase=apply
adop phase=finalize
adop phase=cutover
adop phase=cleanup

If this fails, your 12.2 environment is not production-ready.

---

14. Production Cutover

Final activities:

• Switch load balancer
• Start services
• Verify workflows
• Smoke testing
• Enable users

Start apps:

adstrtal.sh apps/apps

---

Important Architecture Changes in 12.2

Area	11i	12.2
Web tier	Apache/JServ	WebLogic
Patching	adpatch	adop online patching
File system	Single	Dual fs1/fs2
DB requirement	9i/10g	11.2.0.4+
Online patching	No	Yes
Middleware	10g	Fusion Middleware

---

Recommended Real-World Approach

Most successful projects follow:

1. Clone PROD → Sandbox
2. Perform multiple dry runs
3. Document timings/errors
4. Tune long-running upgrade workers
5. Freeze customizations
6. Upgrade PROD only after 2–3 successful rehearsals

Reddit practitioners consistently mention that multiple rehearsal upgrades are essential for reducing downtime and stabilizing the cutover.

---

Key Oracle Documentation

• Oracle EBS 11i to 12.2 Upgrade Guide
• Oracle EBS 12.2 Upgrade Documentation Library
• Oracle EBS Technology Blog

If you want, I can also provide:

• detailed command-by-command upgrade checklist
• complete downtime sequence
• 11i → 12.2.13 + 19c reference architecture
• ADOP troubleshooting guide
• common upgrade failures and fixes
• effort estimation and downtime planning
• upgrade flow diagram
• clone-and-test strategy