MSAMM
Back to course

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

Patching the database tier

Lesson 76 of 184 · 2 min

A SEPARATE CALENDAR, a separate tool and a SEPARATE OUTAGE. Sequencing it against the application patches. The database has its own patch stream and its own tooling, and it is the half of the estate that gets neglected. Application patching has adop, a rhythm and an obvious owner; the database quarterly arrives on a different calendar and belongs to whoever remembers. AND IT IS THE HALF THAT CARRIES MOST OF THE PUBLISHED SECURITY EXPOSURE, which is the argument for treating it as seriously as the application stream rather than as something to do when there is time. ITS OUTAGE IS DIFFERENT IN KIND FROM AN adop CUTOVER: THE DATABASE IS DOWN, SO EVERYTHING IS DOWN, FOR AS LONG AS THE PATCH TAKES. There is no online model here — no patch edition, no short swap. So a database patch is a genuine outage of an hour or more, and it…

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