Upgrade Oracle E-Business Suite R12.2.13 → R12.2.14

 

Step by Step Guide to Upgrade Oracle E-Business Suite R12.2.13 → R12.2.14

Hello Everyone 👋,

In this blog, I am sharing my Apps DBA approach for upgrading Oracle E-Business Suite (EBS) from R12.2.13 to R12.2.14. This guide is simplified, practical, and includes Oracle Doc IDs, patch references, ETCC steps, and timelines so that both DBAs and Management can follow easily.

---

🔹 Why Upgrade to R12.2.14?

• Latest certified release of Oracle E-Business Suite.

• Enhanced security fixes, stability improvements, and new features.

• Keeps environment aligned with Oracle Support timelines.

• Foundation for future EBS roadmap.

---

📌 Pre-Upgrade Checklist

1. Database Version: Must be 19c (minimum 19.17 or latest RU).

2. Operating System: RHEL 7 or 8 certified.

3. Backups:

   • Take AMI backups (if on AWS EC2).

   • RMAN full DB backup + Apps tier filesystem backup.

4. ETCC Check (Doc ID 1594274.1):

   • Download the latest ETCC.

   • Run on DB + App nodes.

   • Identify and apply missing patches.

---

🔹 Step 1: Apply ETCC Patches

• Download the latest ETCC (Oct 2024 release) from Oracle Support.

• Apply missing Database and Middleware Technology Patches.

• Re-run ETCC until environment is clean.

📖 Reference: Oracle Doc ID 1594274.1

---

🔹 Step 2: Apply Latest AD and TXK Delta Release Update Packs

Before applying the R12.2.14 patch, ensure AD/TXK is up-to-date.

• Apply the following patches:

  • R12.AD.C.Delta.16

  • R12.TXK.C.Delta.16

• These packs include structural changes (e.g., EBS_SYSTEM schema) and upgrade utilities.

📖 Reference: Oracle Doc ID 1617461.1

---

🔹 Step 3: Apply R12.2.14 Upgrade Patch

• Download and apply R12.2.14 Release Update Pack (Patch 35570137).

• Use adop in online mode for minimum downtime.

• Post-Upgrade Steps:

  • Run AutoConfig on all tiers.

  • Compile invalid objects.

  • Validate Concurrent Managers.

📖 Reference: Oracle Doc ID 2484000.1

---

🔹 Step 4: Post-Upgrade Validation

• DBA Validation: Invalid objects, schema compilation, DB logs review.

• Functional Testing:

  • Forms, Reports, Interfaces, and Customizations.

• Testing Cycles:

  • Unit Testing

  • SIT/UAT

  • Regression Testing

---

📊 Suggested Upgrade Timeline (POC/Test Run)

Phase	Task	Duration
Phase 1	AMI + DB Backups	0.5 Day
Phase 2	ETCC Patching	1 Day
Phase 3	Apply AD/TXK Delta 16	1.5 Days
Phase 4	Apply R12.2.14 Patch	2 Days
Phase 5	Post-Upgrade Validation & Handover	1 Day
Total	~6 Days

---

📂 Key Oracle References

• Doc ID 1594274.1 – Using ETCC for DB + Middleware Patching

• Doc ID 1617461.1 – Applying Latest AD and TXK Delta Packs

• Doc ID 2484000.1 – Oracle EBS R12.2.14 Readme

---

🔹 Flowchart – Upgrade Path

Here’s a simple visual flow you can insert into the blog for management clarity:

Start → Backup (AMI + RMAN) → ETCC Patches → AD/TXK Delta 16 → Apply R12.2.14 Patch → Post-Upgrade Validation → Handover

Start → Backup → ETCC → AD/TXK Delta 16 → R12.2.14 Patch → Validation 

---

✅ Conclusion

Upgrading to Oracle EBS R12.2.14 is not just a patching exercise — it’s a strategic move to keep your enterprise system secure, compliant, and future-ready.

My recommendation:

• Always start with a POC in TEST environment.

• Document backups, ETCC results, and validation steps.

• Share timelines with Management before Production cutover.

CHECKLIST FOR ORACLE DATABASE UPGRADE

 

CHECKLIST FOR ORACLE DATABASE UPGRADE

Check List for Oracle Database Upgrade
No	Description	Status
1.	Enable Port 6000 (Default port) XWindow to run DBUA	o Yes o No
2.	Enable Port 22 (SSH) *if it’s still not open	o Yes o No
3.	Run XClock to verify status of GUI	o Yes o No
4.	DBUA can upgrade only supported versions of direct upgrade.   Please verify version from current database 12.1.0.2 OR 12.2.0.1	o Yes o No
5.	Download and Run Oracle’ Database Pre-Upgrade Utility (Doc ID 884522.1) * Oracle Database Pre-Upgrade utility is executed on your existing database, while the database is running (no shutdown required) and provides a list of items which should be reviewed prior to the actual upgrade.	o Yes o No
6.	Create New Oracle Home for 19c *Make sure there are enough disks space in the current Oracle home path (12c) to create new Oracle home(19c)
7.	Transfer Binary Oracle 19c inside the current Oracle server
8.	Source Database            I.            Ensure that all database components/objects provided by Oracle are Valid            II.            Make sure to have a valid backup of source database prior to upgrade.            III.            Ensure backup is complete before upgrade            IV.            Empty recycle bin              V.            Disable any custom triggers that would get executed before / after DDL statements. Re-enable after the upgrade.            VI.            Check the database server upgrade/downgrade compatibility matrix before upgrading the database.            VII.            Set Archive Log ON during upgrade. Oracle recommends that you set Archive Log ON in order for DBUA to create and update the log file for the upgrade process.             VIII.            For Oracle RAC, if you upgrade a cluster database using DBUA, then you must leave the CLUSTER_DATABASE initialization parameter set to TRUE.            IX.            Ensure to run the pre-upgrade utility prior to upgrading the database. (refer item no 3)            X.            Examine and follow the recommendation given in the preupgrade log file. (refer item no 3)            XI.            Materialized views in source database should be stopped before upgrade (Doc ID 1406586.1)            XII.             Disable scheduled database custom jobs / cron jobs.	o Yes o No   o Yes o No   o Yes o No   o Yes o No   o Yes o No     o Yes o No    o Yes o No     o Yes o No      o Yes o No   o Yes o No  o Yes o No   o Yes o No
9.	Target Database            I. Verify whether Operating System/ Platform is certified for 19x release            II.  Make sure to set the ORACLE_HOME, PATH, LD_LIBRARY_PATH, LIBPATH etc. to 19.x target home.            III. Review patch status inside current database (Doc ID 2539751.1)	o Yes o No   o Yes o No    o Yes o No
10.	Make sure Latest RMAN Backup success before start upgrade	o Yes o No