MSAMM
Back to course

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

Abandoning and cleaning up

Lesson 74 of 184 · 2 min

The commands, and the state the system is in afterwards — WHICH IS NOT ALWAYS THE STATE IT WAS IN BEFORE. Abandoning tells adop to discard the patch edition rather than continue with it, and cleanup then removes what the cycle left behind. Both are ordinary commands and both are safe; what is not safe is the assumption that follows them. THE ASSUMPTION IS THAT THE SYSTEM IS NOW EXACTLY AS IT WAS BEFORE THE CYCLE STARTED, AND IT IS NEARLY TRUE. Users are on the run edition, which was never touched. Nothing they can see has changed. "Nearly" is where the next incident lives. SO VERIFY THREE THINGS RATHER THAN ONE. First, the cycle status — adop will tell you what state it believes it is in, and it must say no cycle is in progress before anything else is attempted. A system that thinks a cycle is still…

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