Oracle Apps DBA: Keeping E-Business Suite Alive · Module 17 · When it is not the database
What breaks: two arguments that went badly
Lesson 178 of 184 · 3 min
A finding WITH NO EVIDENCE BEHIND IT, and a CORRECT finding delivered in a way that made the other team DEFEND THEIR SYSTEM INSTEAD OF CHECKING IT. THE FINDING WITH NO EVIDENCE IS THE ONE THAT COSTS CREDIBILITY RATHER THAN TIME. "It looks like a network problem" handed over with nothing behind it — and the network team checks their monitoring, reports everything within specification, and hands it back. Both are right, and nothing has moved. AND THE COST COMPOUNDS, WHICH IS THE PART TO NOTICE. The next time you bring them something — with measurements, correctly — they have learned that findings from your team are suspicions. Credibility is spent by the first unevidenced hand-off and it is spent for months. THE CORRECT FINDING DELIVERED BADLY IS THE MORE PAINFUL OF THE TWO, BECAUSE THE WORK WAS DONE PROPERLY. The measurements were right, the diagnosis was right, and 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.
In this module: Module 17 · When it is not the database
- 1Why the database is always blamed first
- 2Ruling the database in or out quickly
- 3When it is the network
- 4When it is storage
- 5When it is the client
- 6When it is a person
- 7Writing a finding somebody will accept
- 8What breaks: two arguments that went badly