MSAMM
Back to course

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

Ruling the database in or out quickly

Lesson 172 of 184 · 2 min

A short sequence that settles it IN MINUTES, with EVIDENCE YOU CAN SHOW SOMEBODY ELSE. The sequence is short because it eliminates rather than investigates, and the evidence matters as much as the answer — a conclusion nobody else can check is an opinion. ONE: IS THE DATABASE DOING ANYTHING UNUSUAL RIGHT NOW? Active sessions and what they are waiting on — Module 11 Lesson 3's five categories. A database with a handful of idle sessions while users report a system-wide problem is not the cause, and that takes one query. TWO: HAS ANYTHING CHANGED IN THE DATABASE'S OWN MEASUREMENTS? Compare against the baseline from Module 11 Lesson 5. Same workload, same waits, same response times as a normal period is strong evidence — and without a baseline you cannot make this step at all, which is why that lesson is not optional. THREE: TIME A QUERY YOURSELF, FROM 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
Ruling the database in or out quickly — Oracle Apps DBA: Keeping E-Business Suite Alive — MSAMM