MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 7 · Patching

The outage plan

Lesson 78 of 184 · 2 min

Who is told, in what order, WHAT THE ABORT CRITERIA ARE, and WHO DECIDES. Written BEFORE THE NIGHT, not during it. The technical work is the smaller half of a patching night, and the plan is what prevents the failures that are not technical at all. WHO IS TOLD AND IN WHAT ORDER IS NOT ADMINISTRATION. Users need enough notice to finish what they are doing — a period close that runs into the window is a business event rather than an inconvenience. The service desk needs to know, or they spend the evening logging tickets for a system you took down on purpose. And anybody whose interfaces run overnight needs to know, because a partner expecting a file at 02:00 will not get one. THE ABORT CRITERIA ARE THE PART THAT IS ALWAYS OMITTED AND ALWAYS NEEDED. Write, in advance: the time by which the cutover must have started,…

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.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 7 · Patching

  1. 1Why you are patching at all
  2. 2Kinds of patch, and what each touches
  3. 3Reading a readme properly
  4. 4Online patching: the model
  5. 5The adop cycle, phase by phaseFree preview
  6. 6When a phase fails
  7. 7Abandoning and cleaning up
  8. 8Rollback: what is actually reversible
  9. 9Patching the database tier
  10. 10Testing a patch before production
  11. 11The outage plan
  12. 12Patching cadence, and falling behind
  13. 13What breaks: five patching failures
  14. 14Lab briefing · Apply, fail, abandon, apply again