Oracle Apps DBA: Keeping E-Business Suite Alive · Module 14 · Upgrades and platform moves
What breaks: three upgrade failures
Lesson 150 of 184 · 3 min
A customisation NOBODY INVENTORIED, a rehearsal on a clone THAT DID NOT MATCH PRODUCTION, and an outage that RAN PAST THE WINDOW WITH NO CHECKPOINT TO STOP AT. THE UNINVENTORIED CUSTOMISATION IS THE ONE DISCOVERED AFTER GO-LIVE, BY A USER. It was not in the custom top — Module 4 Lesson 8's failure — or it was a spreadsheet, a reporting tool, or a script on somebody's desktop. Every rehearsal passed, because none of them exercised something nobody knew existed. AND THE COST IS PAID BY THE PERSON WHO DEPENDS ON IT, AFTER THE PROJECT IS DECLARED DONE. Lesson 3's question to the business — what do you use that connects to this — is the only thing that finds these, and it is skipped because it feels like a technical inventory should be enough. THE REHEARSAL ON A MISMATCHED CLONE IS THE MOST DAMAGING BECAUSE EVERYTHING WAS DONE PROPERLY.…
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