MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 14 · Upgrades and platform moves

Upgrade, migration, or move

Lesson 142 of 184 · 3 min

THREE DIFFERENT PROJECTS THAT GET CALLED THE SAME THING, with different risks and different rehearsals. "We are upgrading" is used for all three, and they need different plans — so establishing which one you are being asked for is the first hour of the project. AN UPGRADE CHANGES THE VERSION OF SOMETHING. A new EBS release, a new database version. The functionality changes, the schema changes, and everything built on top has to be re-verified — which is why the size is decided by the inventory in Lesson 3 rather than by the version numbers. A MIGRATION MOVES TO A DIFFERENT PLATFORM. Another operating system, another architecture. The version stays the same and the executables and possibly the data format do not, so this is not a clone — Module 6 Lesson 7 — and the character set question in Lesson 7 has to be settled before anything else. A…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Apps DBA: Keeping E-Business Suite Alive, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 14 · Upgrades and platform moves

  1. 1Upgrade, migration, or move
  2. 2Why estates fall behind
  3. 3Assessing what an upgrade will touch
  4. 4The rehearsal, and how many you need
  5. 5Timing the outage
  6. 6The go or no-go decision
  7. 7Moving to a different platform
  8. 8Moving EBS to a cloud VM
  9. 9What breaks: three upgrade failures
  10. 10Lab briefing · Plan an upgrade you will not run
Upgrade, migration, or move — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM