Oracle Apps DBA: Keeping E-Business Suite Alive · Module 7 · Patching
What breaks: five patching failures
Lesson 80 of 184 · 3 min
A prerequisite nobody read, a cutover with no rollback, a cleanup skipped for a month, a customisation overwritten, and A PATCH TESTED ON A CLONE THAT DID NOT MATCH PRODUCTION. THE PREREQUISITE NOBODY READ FAILS THE APPLY PARTWAY THROUGH. Not at the start — partway — so the window is already open and the estate is in a cycle. The prerequisite cannot be satisfied at 01:00 because it is another patch, so the only option is abandoning the night. Lesson 3, and it is five minutes of reading days earlier. THE CUTOVER WITH NO ROLLBACK IS THE ONE WHERE A PLAN EXISTED AND WAS FALSE. Somebody wrote "roll back if there are problems" without reading the paragraph saying this patch cannot be. The real fallback was a database restore nobody had scheduled time for, discovered after the cutover with users already on the system. Lesson 8. THE CLEANUP SKIPPED FOR…
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 7 · Patching
- 1Why you are patching at all
- 2Kinds of patch, and what each touches
- 3Reading a readme properly
- 4Online patching: the model
- 5The adop cycle, phase by phaseFree preview
- 6When a phase fails
- 7Abandoning and cleaning up
- 8Rollback: what is actually reversible
- 9Patching the database tier
- 10Testing a patch before production
- 11The outage plan
- 12Patching cadence, and falling behind
- 13What breaks: five patching failures
- 14Lab briefing · Apply, fail, abandon, apply again