MSAMM
Back to course

Oracle Apps DBA: Keeping E-Business Suite Alive · Module 17 · When it is not the database

Writing a finding somebody will accept

Lesson 177 of 184 · 3 min

What you measured, what it shows, what you are asking for, and WHAT YOU ARE NOT CLAIMING. THE LAST PART IS WHAT MAKES IT LAND. A correct finding delivered badly gets defended against rather than checked, which is Lesson 8's second failure and wastes the whole investigation. WHAT YOU MEASURED COMES FIRST AND IT MUST BE REPRODUCIBLE. The command, the host, the time, the conditions. Anything the other team can run themselves — because a measurement they can repeat is a fact, and one they cannot is your assertion. WHAT IT SHOWS IS THE NUMBERS AND THE COMPARISON, WITH NO INTERPRETATION YET. This value now, that value last month, this value from a different host. The comparison is the persuasive part, because it rules out the measurement being wrong in a way a single figure cannot. WHAT YOU ARE ASKING FOR IS A REQUEST TO CHECK RATHER THAN A DIAGNOSIS

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.

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 17 · When it is not the database

  1. 1Why the database is always blamed first
  2. 2Ruling the database in or out quickly
  3. 3When it is the network
  4. 4When it is storage
  5. 5When it is the client
  6. 6When it is a person
  7. 7Writing a finding somebody will accept
  8. 8What breaks: two arguments that went badly
Writing a finding somebody will accept — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM