MSAMM
Back to course

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

Rollback: what is actually reversible

Lesson 75 of 184 · 2 min

Some patches roll back, some do not, and A DATA CHANGE NEVER DOES. Knowing which you are holding BEFORE THE CUTOVER. "We can roll it back" is the sentence that gets a risky patch approved, and it is frequently untrue. BEFORE THE CUTOVER, ROLLBACK IS TRIVIAL AND COMPLETE. Abandon the cycle; users were never on the patch edition. That is the strongest position you will be in all night, and it is why the cutover is the decision point rather than the start. AFTER THE CUTOVER, IT DEPENDS ENTIRELY ON WHAT THE PATCH DID. File changes can generally be reversed. Object definitions can generally be reversed. A DATA CHANGE CANNOT. AND THE DATA CHANGE IS THE PART PEOPLE FORGET IS IN THERE. Patches migrate data: they populate a new column, transform values into a new format, seed reference rows, restructure something. Once users transact on top of that, reversing 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