Oracle Apps DBA: Keeping E-Business Suite Alive · Module 14 · Upgrades and platform moves
The go or no-go decision
Lesson 147 of 184 · 3 min
Abort criteria agreed BEFORE THE NIGHT, and WHO IS ALLOWED TO INVOKE THEM. NOT THE PERSON WHO IS TIRED AT FOUR IN THE MORNING. Module 7 Lesson 11 established this for a patch; an upgrade is the same rule with far more invested and therefore far more pressure to continue. THE CRITERIA MUST BE CONCRETE AND TIME-BASED, WHICH MEANS THEY COME FROM LESSON 5'S CHECKPOINTS. "If the main run has not completed by 02:00, we abort." Not "if things are going badly", which is a judgement, and judgement at 04:00 is the thing this lesson exists to remove. AND THE PRESSURE AT 04:00 IS ALWAYS TOWARD CONTINUING, FOR REASONS THAT FEEL RATIONAL. Months of preparation, a business told this weekend would be the one, and a team who cannot face repeating it. Every one of those argues for one more hour, and none of them changes whether the remaining work…
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