MSAMM
Back to course

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

Why the database is always blamed first

Lesson 171 of 184 · 3 min

It is THE COMPONENT EVERYONE HAS HEARD OF. Understanding that makes the conversation EASIER RATHER THAN MORE ANNOYING. "It must be the database" arrives with every performance complaint, and being irritated by it is the least useful available response. THE REASON IS NOT IGNORANCE, IT IS VOCABULARY. A user knows the system is slow and needs a word for where the problem might be. The database is the only component in the stack most people can name — nobody says "it must be the managed server" or "it must be the storage latency", because those are not words they have. SO "IT MUST BE THE DATABASE" USUALLY MEANS "SOMETHING IS WRONG AND I CANNOT TELL YOU WHAT", which is a reasonable thing for somebody to say and contains no claim you need to argue with. AND TREATING IT AS AN ACCUSATION IS WHAT MAKES THESE CONVERSATIONS GO BADLY. Defending 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.

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