MSAMM
Back to course

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

Online patching: the model

Lesson 71 of 184 · 2 min

Two editions, a patch edition prepared WHILE USERS WORK, and a cutover. THE CONCEPT BEFORE THE COMMANDS. Online patching exists to solve one problem: applying a large patch used to mean an outage as long as the patch took, which on a real estate is many hours. THE MECHANISM IS TWO COPIES OF EVERYTHING. Module 2 Lesson 3's two application file systems, and a corresponding split inside the database. One set is RUN — what users are on right now. The other is PATCH — where the patch is being applied. SO THE LONG PART HAPPENS WHILE THE SYSTEM IS UP. Files are copied, packages are compiled, objects are created — all in the patch edition, which nobody is using. Users work normally throughout, on code that is not being touched. THE CUTOVER IS THE ONLY OUTAGE AND IT IS SHORT. The system stops, the two editions swap — patch…

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