Oracle Apps DBA: Keeping E-Business Suite Alive · Module 14 · Upgrades and platform moves
Assessing what an upgrade will touch
Lesson 144 of 184 · 3 min
Customisations, interfaces, reports and ANYTHING REACHING IN FROM OUTSIDE. The inventory THAT DECIDES THE SIZE OF THE PROJECT. The inventory is the first deliverable and it is what converts "we should upgrade" into a project with a size, a cost and a duration. Without it, every estimate is invented. CUSTOMISATIONS ARE THE OBVIOUS CATEGORY AND THE HARDEST TO COUNT. The custom top from Module 4 Lesson 8 is the starting point — and anything placed outside it, which is the failure that lesson describes, is invisible to a directory listing. So the inventory has to combine what is in the custom top with what has been RECORDED, and the gap between those two lists is itself a finding. INTERFACES ARE THE CATEGORY THAT INVOLVES OTHER ORGANISATIONS. Every file dropped for a partner, every service another system calls, every scheduled extract. Each needs a test window with somebody outside your control,…
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