Oracle Apps DBA: Keeping E-Business Suite Alive · Module 1 · What an Apps DBA does, and what Fusion took away
What breaks: the estate nobody owned
Lesson 11 of 184 · 3 min
Two shapes — a system with THREE PART-TIME ADMINISTRATORS AND NO ONE ACCOUNTABLE, and one with A SINGLE ADMINISTRATOR AND NO SUCCESSOR. THE FIRST FAILS BY DIFFUSION AND IT LOOKS LIKE RESILIENCE. Three people each spend a day a week on it, so it is always covered and nobody is a single point of failure. What actually happens is that nothing with a long horizon gets done — backups are taken and never restore-tested, patches are deferred because nobody owns the window, and the documentation is three partial sets in three places. THE MECHANISM IS THAT EVERY ONE OF THEM IS DOING THE URGENT PART CORRECTLY. Nobody is negligent. Availability gets attended to because it announces itself; recoverability does not, so it is always next week's problem for whoever is on it. The failure surfaces the day a restore is needed and nobody can say when one was last proven.…
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.