MSAMM
Back to course

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

Reading a readme properly

Lesson 70 of 184 · 2 min

Prerequisites, post-steps and THE PARAGRAPH THAT SAYS THIS CANNOT BE ROLLED BACK. The five minutes that prevents most patching incidents. The readme is read by almost nobody and it contains the answers to almost every question that will be asked at 2am. PREREQUISITES ARE THE FIRST SECTION AND THE COMMONEST CAUSE OF A FAILED APPLY. Another patch that must be applied first, a minimum level, a technology stack requirement. Missing one means the patch fails partway through — not before it starts — so you are now in a partially applied state during a window you have already opened. Lesson 13's first failure, and it costs the entire night. POST-STEPS ARE THE SECOND AND THEY ARE SKIPPED MORE OFTEN THAN THEY ARE MISSED. The patch completes, everybody is tired, and a step that must be run afterwards — a script, a regeneration, a configuration change — is left for the…

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