Oracle Apps DBA: Keeping E-Business Suite Alive · Module 18 · Capstone: a system handed over
Making it recoverable
Lesson 181 of 184 · 3 min
THE FIRST REAL CHANGE, because UNTIL A RESTORE HAS BEEN PROVEN NOTHING ELSE YOU DO IS SAFE. That is the argument in one sentence, and it is the one to make to a client who wants the performance complaint addressed first. EVERY OTHER PIECE OF WORK IN THIS CAPSTONE CARRIES RISK. Tuning changes plans, monitoring needs configuration, and any change can go wrong. Doing any of it on an estate with no proven way back is taking a risk with no floor under it — and the floor is not the backup, it is a restore somebody has performed. SO ESTABLISH ARCHIVE LOG MODE FIRST, BECAUSE IT DECIDES WHAT IS POSSIBLE. Module 3 Lesson 5 — if it is off on a production instance, that is an incident to report immediately, in writing, with the consequence stated in the client's terms. THEN RESTORE, PROPERLY, TO A SEPARATE HOST. Module 5…
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 18 · Capstone: a system handed over
- 1The brief
- 2Establishing what you have
- 3Making it recoverable
- 4Making it observable
- 5The performance complaint
- 6The handover