MSAMM
Back to course

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

When it is a person

Lesson 176 of 184 · 3 min

A job somebody submitted, a change somebody made, or a process nobody documented. ASKING WITHOUT ACCUSING. A large share of incidents are caused by a person doing something entirely reasonable, and the difficulty is asking about it in a way that gets an honest answer. THE JOB SOMEBODY SUBMITTED IS THE COMMONEST. A report with no date range at month end — Module 11 Lesson 10 — consuming the concurrent managers and the database at once. Nobody did anything wrong; a screen let them ask for something enormous. THE CHANGE SOMEBODY MADE IS THE ONE THAT EXPLAINS "SINCE TUESDAY". A configuration change, a new interface enabled, a profile option adjusted. It was legitimate, it was in somebody's remit, and it was not mentioned to you — because the person making it had no reason to think it would affect performance. AND THE PROCESS NOBODY DOCUMENTED IS THE ONE THAT TAKES

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