MSAMM
Back to course

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

Moving EBS to a cloud VM

Lesson 149 of 184 · 3 min

What GENUINELY changes about the DBA job, what DOES NOT, and THE NETWORK QUESTIONS THAT ARRIVE WITH IT. Module 1 Lesson 5 said this in outline; here is what it means for the work itself. WHAT GENUINELY CHANGES IS CAPACITY AND COST BECOMING THE SAME DECISION. Resizing is minutes rather than a purchase order, which is a real improvement — and it makes adding resource cheaper than diagnosing a problem. Two more cores is a monthly cost bought to avoid an afternoon of Module 11's work, and it works, which is what makes it a trap. SNAPSHOTS ALSO CHANGE THE SHAPE OF RISK. A snapshot before a patch is a rollback that takes minutes, which is genuinely better than what Module 7 Lesson 8 describes. It is not a backup — it lives with the instance and dies with it — and treating it as one is how an estate

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.

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
Moving EBS to a cloud VM — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM