Oracle Apps DBA: Keeping E-Business Suite Alive · Module 7 · Patching
Kinds of patch, and what each touches
Lesson 69 of 184 · 2 min
Database, application, technology stack and one-off fixes. Reading a patch to find out WHAT IT WILL ACTUALLY CHANGE. The four kinds have different tools, different outage profiles and different rollback stories, so knowing which you are holding decides how the night is planned. DATABASE PATCHES CHANGE THE ORACLE HOME AND SOMETIMES THE DATA DICTIONARY. Their own tooling, their own calendar, and Lesson 9 — and their outage is the database, which means the application tier is down for the duration whether or not it is being touched. APPLICATION PATCHES ARE THE ORDINARY CASE AND ARE APPLIED WITH adop. They change the file system and usually the database too — new files, new packages, altered tables. That dual nature is why patching is not reversible by restoring a file system, and it is the whole subject of Lesson 8. TECHNOLOGY STACK PATCHES CHANGE THE MIDDLEWARE UNDERNEATH THE APPLICATION. They are 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.
In this module: Module 7 · Patching
- 1Why you are patching at all
- 2Kinds of patch, and what each touches
- 3Reading a readme properly
- 4Online patching: the model
- 5The adop cycle, phase by phaseFree preview
- 6When a phase fails
- 7Abandoning and cleaning up
- 8Rollback: what is actually reversible
- 9Patching the database tier
- 10Testing a patch before production
- 11The outage plan
- 12Patching cadence, and falling behind
- 13What breaks: five patching failures
- 14Lab briefing · Apply, fail, abandon, apply again