MSAMM
Back to course

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

Lab briefing · Apply, fail, abandon, apply again

Lesson 81 of 184 · 3 min

Run a full cycle, ENGINEER A FAILURE in the apply phase, ABANDON IT CLEANLY, and PROVE THE SYSTEM IS WHERE YOU THINK IT IS. The proving is the exercise. Running a cycle successfully is a demonstration; failing one, abandoning it and then establishing exactly where you are afterwards is the skill you will need on a night when you cannot choose. RUN A COMPLETE CYCLE FIRST, WITH A SMALL PATCH, AND TIME EVERY PHASE. Those five numbers are what let you plan a real window — and the point of the first pass is that everything works, so you know what normal looks like. THEN ENGINEER A FAILURE IN THE APPLY PHASE. Take a filesystem to zero free space, revoke a permission, hold a lock on an object the patch needs. Any of the environmental causes from Module 4 Lesson 7 — then watch what happens: the utility does not…

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