Oracle Apps DBA: Keeping E-Business Suite Alive · Module 14 · Upgrades and platform moves
Why estates fall behind
Lesson 143 of 184 · 3 min
NOT LAZINESS. Customisations, integrations, a business that CANNOT TAKE THE OUTAGE, and THE COST OF THE REHEARSAL. Every estate that is years behind is described by somebody as neglected, and that diagnosis is almost always wrong and always unhelpful. CUSTOMISATIONS ARE THE FIRST REASON AND THE LARGEST. Every one has to be assessed, possibly rewritten, and tested — and an estate with two hundred of them has two hundred small projects inside the upgrade. Nobody counted them when they were written, so the size is unknown until Lesson 3's inventory exists. INTEGRATIONS ARE THE SECOND AND THEY INVOLVE OTHER PEOPLE. A bank, a partner, a warehouse system. Each has to be re-tested, and each needs somebody at the other end to agree to a test window — which is a scheduling problem across organisations rather than a technical one, and it moves in months. THE OUTAGE IS THE THIRD AND…
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.
In this module: Module 14 · Upgrades and platform moves
- 1Upgrade, migration, or move
- 2Why estates fall behind
- 3Assessing what an upgrade will touch
- 4The rehearsal, and how many you need
- 5Timing the outage
- 6The go or no-go decision
- 7Moving to a different platform
- 8Moving EBS to a cloud VM
- 9What breaks: three upgrade failures
- 10Lab briefing · Plan an upgrade you will not run